ilovepdf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_OUTPUT_DIR | No | Default output directory for processed files | ./output |
| ILOVEPDF_PUBLIC_KEY | Yes | Your iLovePDF public API key | |
| ILOVEPDF_SECRET_KEY | Yes | Your iLovePDF secret API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| merge-pdfsA | Merge multiple PDF files into a single PDF document |
| split-pdfB | Split a PDF file into multiple documents based on page ranges or fixed intervals |
| compress-pdfB | Reduce the file size of a PDF document while maintaining quality |
| rotate-pdfB | Rotate all pages in a PDF document by a specified angle |
| protect-pdfB | Add password protection to a PDF document |
| unlock-pdfB | Remove password protection from a PDF document |
| repair-pdfB | Attempt to repair a damaged or corrupted PDF document |
| add-watermarkB | Add a text or image watermark to a PDF document |
| add-page-numbersB | Add page numbers to a PDF document |
| pdf-to-jpgB | Convert PDF pages to JPG images |
| images-to-pdfB | Convert images (JPG, PNG, etc.) to a PDF document |
| html-to-pdfB | Convert a webpage URL to a PDF document |
| office-to-pdfB | Convert Microsoft Office documents (Word, Excel, PowerPoint) to PDF |
| convert-to-pdfaA | Convert a PDF to PDF/A format for long-term archiving |
| validate-pdfaB | Validate if a PDF conforms to PDF/A standards |
| extract-textC | Extract text content from a PDF document |
| ocr-pdfA | Perform OCR (Optical Character Recognition) on a scanned PDF to make it searchable |
| edit-pdfC | Add text or images to specific positions in a PDF document |
| sign-pdfA | Create a digital signature request for a PDF document (sends signature requests via email) |
| get-signature-statusB | Get the status of a signature request |
| void-signatureB | Void/cancel a pending signature request |
| get-remaining-filesA | Check how many API file operations remain in your iLovePDF quota |
| list-tasksB | List recent PDF processing tasks from your iLovePDF account |
| chain-operationsB | Chain multiple PDF operations together (e.g., compress then merge, or split then protect) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Each tool targets a distinct PDF operation or resource, from rotation and conversion to security and e-signatures. There is minimal overlap; even similar functions like extract-text and ocr-pdf address different input types.
Tool names follow a consistent lowercase-hyphenated verb-first pattern (e.g., rotate-pdf, compress-pdf, add-watermark). Minor inconsistencies include pluralization (merge-pdfs vs. rotate-pdf) and the use of 'to-pdf' for conversions, but overall the pattern is predictable.
With 24 tools, the set is on the heavier side, which falls into the borderline category. However, each tool addresses a specific PDF workflow need, so the count is arguably justified for a comprehensive PDF service.
The server covers an extensive range of PDF operations: conversion, page manipulation, security, compression, repair, OCR, text extraction, editing, e-signatures, PDF/A handling, and task management. There are no obvious dead ends, and the surface appears complete for typical PDF workflows.