iLovePDF MCP for AI. Handle the entire life cycle of any PDF document.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
iLovePDF connects PDF document manipulation—merging, splitting, compressing, and converting files—to your AI agent. You can initiate complex file tasks through natural conversation; it tracks progress in real time, allowing you to retrieve finalized documents without manual web steps.
What AI agents can do with iLovePDF Automation
Get pdf download link
Retrieves a usable download URL for a PDF that has finished processing.
Get task status
Checks the current status of any ongoing or completed PDF task using its unique ID.
List pdf tasks
Retrieves a list of all recent PDF processing jobs that have run through the system.
Initiate a full suite of document actions—including merging multiple files or splitting one large file—and get an ID for tracking.
Query the current state of any processing job, telling you if it's pending, running, or complete.
Start a task using a file link instead of having to upload the actual file data.
Get a direct, temporary download link for any processed PDF output.
Ask an AI about this
Waiting for input…
What AI agents can do with iLovePDF with 6 Tools
These tools allow your agent to handle every step of the document lifecycle: uploading files from URLs, starting tasks, checking status, and retrieving final downloads.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using iLovePDF on VinkiusGet Pdf Download Link
Retrieves a usable download URL for a PDF that has finished processing.
Get Task Status
Checks the current status of any ongoing or completed PDF task using its unique ID.
List Pdf Tasks
Retrieves a list of all recent PDF processing jobs that have run through the system.
Process Pdf Task
Executes specific, configured PDF manipulations on files already uploaded to the...
Start Pdf Task
Starts a new PDF processing job; it requires parameters and returns a task ID you...
Upload Pdf By Url
Downloads a PDF file directly from an external web address for use in a task.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with iLovePDF, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by iLovePDF. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Dealing with PDFs means dealing with endless clicks, copy-pasting, and waiting., Solved with Vinkius AI Gateway
Right now, if you need to combine five reports into a single document, the process is manual pain. You download Report A, open it in a PDF editor; then download Report B, repeat the merge steps for all five files. If one file fails or the server times out, you're back at square one—you have to restart the whole tedious sequence.
With this MCP, your agent handles the entire chain of commands. You simply tell it what needs doing: 'Merge these five reports and compress them.' The tool manages the queue, tracks progress, and gives you a single, finished file ready for use.
iLovePDF MCP lets you manage document workflows using `start_pdf_task`.
The biggest time sink that disappears is the manual state management. You don't have to remember if you need to check status, or what ID belongs to which job, or if the process finished successfully before downloading. The agent handles all of it.
Now, complex file manipulation becomes a single conversation turn. It’s about defining the desired end state, not managing the 10 steps required to get there.
What your AI can actually do with this
You need to run a batch of PDFs through several stages—say, merging three reports, then running them through compression, and finally converting the whole thing to DOCX. Manually doing that is painful. This MCP lets your AI agent handle the entire workflow conversationally. You can upload files using just a URL or give it local documents; the system handles the task queuing and progress tracking.
It's built for developers who need reliable file processing pipelines, so you don't have to write boilerplate code for every step. When connected through Vinkius, your agent gets access to this whole toolkit right alongside everything else in the catalog.
019dd108-d5f8-7343-a32f-3fc470ce5f74 Here's how it actually works
The bottom line is: you feed it a job and a URL, it runs the whole thing in the background, and then you retrieve the result via a link.
Tell your agent to start the job. You can begin by uploading files via URL or giving it local documents, which returns a unique task ID.
Use that task ID with the status check tool (get_task_status) until the process is marked 'Complete'.
Finally, use get_pdf_download_link to pull the finished file into your workflow.
Who is this actually for?
This MCP is built for developers and operations engineers who deal with document lifecycles. If your job involves transforming files—getting data from PDFs, combining reports, or converting formats—you need this. It cuts out the manual steps of status checking and downloading.
Needs to combine multiple quarterly PDF reports into one master document before passing it to a compliance team.
Runs nightly batch jobs that compress and archive thousands of generated PDFs from different sources.
Needs to integrate PDF processing into a backend API, using the agent to handle task state management without complex external queue workers.
What Changes When You Connect
You don't have to manually monitor job status. Instead, use get_task_status to keep your agent informed until a task is ready.
Merge complex reports in one go. Use start_pdf_task to combine multiple documents and run compression or conversion on the result immediately.
Process files from anywhere. The upload_pdf_by_url tool means you can start a job just by providing an address, no file upload needed.
Keep track of everything. Run list_pdf_tasks to see a history of all jobs completed today or last week—it's great for debugging workflows.
Get the final product right away. Once processing is done, get_pdf_download_link gives you the direct URL, so your agent can pass it off immediately.
See it in action
Compliance Audit File Collection
A compliance officer needs to gather reports from five different departments. Instead of manually downloading and merging them, they ask their agent to use upload_pdf_by_url for all five links, then call start_pdf_task to merge them into a single audit package.
Converting Legacy Documentation
You receive 50 old PDFs that need to be converted to Word format. You instruct your agent to run the full batch through the conversion process, then use get_task_status repeatedly until all are ready for final retrieval.
Creating a Master Presentation
Your marketing team has three separate pitch decks (PDF). You tell your agent to merge them using start_pdf_task, then compress the resulting large file, ensuring the output is small enough for email.
The honest tradeoffs
Assuming instant results
The developer thinks that once they call start_pdf_task, the data is ready to be downloaded. They immediately try calling get_pdf_download_link and fail.
Wait for confirmation. You must first use get_task_status with the ID returned by start_pdf_task. Only when that status reports 'Complete' should you attempt to get the download link.
Ignoring input source
Trying to process a PDF file that is only available via a temporary web link, forcing an actual local upload.
Use upload_pdf_by_url first. This lets you pull the document directly from the internet and feed it into your workflow without needing physical access.
Losing track of jobs
Running multiple tasks (e.g., merge, then compress) in a session and forgetting which task ID belongs to which job.
Always use list_pdf_tasks before starting new jobs. This gives you a clear history log, so you can reference the correct task IDs later when checking status.
When It Fits, When It Doesn't
Use this MCP if your workflow requires managing asynchronous file states: Input -> Process -> Wait -> Output. You need it when you must reliably merge multiple documents, convert formats (PDF to DOCX), or compress large batches of files; in short, any time the PDF processing is not instantaneous. Don't use this if you just need to read data content from a single PDF—you'd be better off using an OCR/extraction tool that reads text directly. Use it only for file manipulation and state management.
Questions you might have
How do I start merging PDFs with iLovePDF MCP? +
You initiate a merge by calling start_pdf_task. You pass the IDs of all the source files, and the tool returns a task ID that you must use for tracking.
Can I process PDFs using iLovePDF MCP if they are only online? +
Yes. Use upload_pdf_by_url to pull the document from an external web address, making it available to your task without needing a direct upload.
What do I use if my PDF job is finished? iLovePDF MCP? +
You need get_pdf_download_link. This tool takes the successful task ID and gives you the final, working URL for the document.
How can I check on a long-running job with iLovePDF MCP? +
Use get_task_status and provide it with the unique task ID. This lets your agent know if the process is still running or if it finished successfully.
What credentials do I need to connect iLovePDF MCP and start tasks? +
You need your iLovePDF Public Key and Secret Key. You get these from the developer portal. Providing these keys allows your agent to run all processing tools, like starting a new task or listing existing ones.
How do I specify advanced parameters when using start_pdf_task? +
You pass specific instructions in the JSON payload for start_pdf_task. This lets you define exact output formats, like converting to DOCX, or specifying page ranges for splitting.
What happens if I use upload_pdf_by_url and the URL is inaccessible? +
The tool will return an error code indicating failure. You must check the URL validity first. If it's a temporary network issue, retrying with start_pdf_task usually solves it.
If I need to process multiple different types of tasks, which tools should I use? +
Use list_pdf_tasks first to see your history. Then, you can start new jobs using process_pdf_task or start_pdf_task. Don't forget to check the status with get_task_status afterward.
Can I merge multiple PDF files into one? +
Yes. Use start_pdf_task with task type 'merge', then upload each PDF with upload_pdf_by_url, and finally call process_pdf_task to execute. Use get_pdf_download_link to retrieve the merged result.
Does iLovePDF require two credentials? +
Yes. iLovePDF uses a Public Key and Secret Key pair. The server exchanges these for a JWT token automatically via api.ilovepdf.com/v1. No manual token management required.
Can I track the status of a PDF processing task? +
Yes. Use get_task_status with the task ID to check progress. Use list_pdf_tasks to see all tasks with their current status (pending, processing, completed, failed).
We've already built the connector for iLovePDF. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.