mcp-convertica
OfficialThis server connects your AI assistant to Convertica's file conversion platform, enabling 35+ document and image conversions directly from your AI workflow.
Core Tools:
list_converters– Discover all available conversion tools with their slugs, input fields, and optionsconvert_file– Run any supported conversion on local files, saving results to disk
Supported Conversions:
PDF ↔ Office formats: Convert PDF to/from Word, Excel, and PowerPoint
PDF ↔ Other formats: PDF to/from JPG, HTML, Markdown, Text, and EPUB
PDF → PDF/A: Convert PDFs to archival PDF/A format
Web to PDF: Render HTML files or live URLs as PDFs
PDF manipulation: Merge, split, compress, rotate, crop, watermark, sign, protect, and unlock PDFs
Image conversion: Convert between image formats, optimize images, and convert HEIC photos to JPG, PNG, or PDF
Key Behaviors:
Files are read from and written to your local disk
Results are saved next to the input file by default, or to a custom
output_dirSupports multi-file tools (e.g., merging multiple PDFs) with order-sensitive file input
Supports tool-specific options (e.g., rotation angle, page ranges)
Requires a Convertica API key via the
CONVERTICA_API_KEYenvironment variable
Convertica MCP Server
Convert files without leaving your AI assistant. Connect Claude, Cursor, Windsurf or any MCP client to Convertica and its 35+ document and image conversion tools.
"Convert ~/Downloads/report.pdf to Word"
"Merge these three PDFs and compress the result"
"Turn this HEIC photo into a JPG"
"Render https://example.com as a PDF"MCP tools
The server exposes two tools.
list_converters
Lists all 35+ Convertica converters with their file fields and options. Call this first to find the right tool slug for convert_file. Takes no input.
{ "type": "object", "properties": {} }convert_file
Runs one of convertica.net's 35+ conversion tools on local file(s) and saves the result next to the input (or into output_dir). Requires authentication via the CONVERTICA_API_KEY env var.
{
"type": "object",
"required": ["tool"],
"properties": {
"tool": { "type": "string", "description": "Converter slug from list_converters, e.g. pdf-to-word or pdf-organize/merge" },
"files": { "type": "array", "items": { "type": "string" }, "description": "Absolute paths of input file(s); order matters for multi-file tools" },
"options": { "type": "object", "description": "Tool-specific options as listed by list_converters, e.g. {angle: 90}" },
"output_dir": { "type": "string", "description": "Directory to save the result (default: alongside the first input file)" }
}
}Supported conversions include: PDF ⇄ Word / Excel / PowerPoint / JPG / HTML / Markdown / Text / EPUB, PDF → PDF/A, HTML / URL → PDF, merge / split / compress / rotate / crop / watermark / sign / protect / unlock PDF, image convert / optimize / HEIC → JPG·PNG·PDF, and more. Full list via list_converters or at convertica.net.
Related MCP server: Document Reading and Converter Tool
Setup and API key
You need a Convertica API key: subscribe at convertica.net/pricing, then create a key at convertica.net/users/api-keys. API docs: convertica.net/api/docs.
Claude Code
claude mcp add convertica -e CONVERTICA_API_KEY=cvk_live_... -- npx -y convertica-mcpClaude Desktop / Cursor / Windsurf
{
"mcpServers": {
"convertica": {
"command": "npx",
"args": ["-y", "convertica-mcp"],
"env": { "CONVERTICA_API_KEY": "cvk_live_..." }
}
}
}Usage notes
Files are read from and written to your local disk; results are saved next to the input file unless you pass
output_dir.Conversions run synchronously over HTTPS; processed files are deleted from Convertica's servers right after the response (details).
API calls are metered against your plan's monthly quota; failed calls are not counted.
Local development
npm install
npm run smoke # protocol check, no key needed
CONVERTICA_API_KEY=... npm run smoke # + one real conversionLicense and credits
MIT. Not affiliated with Anthropic; "Convertica" is the service behind convertica.net.
Available Tools
1 toolconvert_fileConvert a file with ConverticaA
Run one of convertica.net's conversion tools on local file(s) and save the result next to the input (or into output_dir). Use list_converters to see tool slugs and per-tool options. Examples: {tool: 'pdf-to-word', files: ['/docs/report.pdf']}; {tool: 'pdf-organize/merge', files: ['/a.pdf', '/b.pdf']}; {tool: 'url-to-pdf', options: {url: 'https://example.com'}}.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | Tool slug from list_converters, e.g. 'pdf-to-word' or 'pdf-organize/merge' | |
| files | No | Absolute paths of input file(s). Order matters for multi-file tools. | |
| options | No | Tool-specific options as listed by list_converters (e.g. {angle: 90, pages: 'all'}) | |
| output_dir | No | Directory to save the result (default: alongside the first input file) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description carries full burden. It does not disclose if input files are modified, whether operations are reversible, or any side effects. Basic conversion intent is clear but lacks behavioral details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two sentences plus compact examples. No redundant words, and purpose is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate but missing key details: no mention of return value, success indication, or sync/async behavior. Given no output schema, these would be helpful for agent confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all parameters (100% coverage), but description adds valuable usage context: 'order matters' for multi-file tools, and examples show how to use options and output_dir. Enhances schema meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool runs conversion tools on local files and saves results, with examples showing usage patterns. It explicitly ties to list_converters for tool slugs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context on when to use (conversion via convertica.net) and direction to list_converters for options. No explicit when-not-to or alternatives, but siblings are absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.0- First observed
convert_file
TDQS
Scored across 1 tool
Only one tool exists, so no ambiguity in selecting among tools.
With a single tool, naming consistency is inherently perfect; the name 'convert_file' follows a clear verb_noun pattern.
One tool is too few for a conversion service; it lacks a necessary discovery tool like list_converters that is referenced in the description.
The server references list_converters but does not provide it, forcing agents to guess available converters; the single tool does not cover the full conversion lifecycle.
Maintenance
Related MCP Connectors
Convert files between 110+ document, image, audio, video, archive and ebook formats from AI agents.
Convert files between formats without quality loss. Speed up your workflow with fast, reliable con…
Convert between 200+ format pairs: JSON, CSV, XML, YAML, PDF, Excel, DOCX and more.
Convert, merge, compress, OCR, redact, and sign PDFs inside your AI assistant. From pdfAssistant.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that converts Excel and Apple Numbers files to PDF format, enabling AI assistants like Claude to perform file conversion directly through conversation.218 npm6MIT
- FlicenseAqualityDmaintenanceEnables document conversion between PDF, DOCX, and Markdown formats to facilitate reading and editing complex files in AI tools like Claude Desktop or Cursor. It utilizes marker-pdf and pandoc to provide structured text versions of documents, helping to manage context and support unsupported file types.11-
- FlicenseNot gradedqualityDmaintenanceConverts files (PDF, Word, images, etc.) to Markdown within Claude Desktop to reduce token usage.-

gurupdf-mcpofficial
AlicenseAqualityCmaintenanceConvert, compress, merge, split and OCR PDFs plus 100+ file formats (Word, Excel, images, ebooks, video) right inside your AI agent. Exposes 126 GuruPDF tools over MCP — works with Claude, Cursor, VS Code, Windsurf, or any MCP client.455 npm2MIT