Carbone MCP Server

If you already use Carbone MCP, the carbone mcp mcp server is the piece that lets your assistant work with it directly. Official MCP for Carbone — Document Generation, Document Conversion, and Universal Templating. Generate PDF, DOCX, XLSX, PPTX, ODT, ODS, CSV, HTML and XML documents from templates and JSON data. Convert Office documents (DOCX, XLSX, PPTX).

What the server does

Give Claude, ChatGPT, and other AI assistants the power to: - 🔄 Document Conversion — 100+ format combinations (PDF, DOCX, XLSX, PNG, HTML, CSV…) - 📄 Template Engine — Generate documents from JSON data with {d.field} tags - 📚 Template Library — Upload, version, categorize, and manage reusable templates - 🎨 PDF Customization — Fill PDF forms, add watermarks, passwords, encryption, multiple converter engines - 🌍 Localization — Multi-language support, currency conversion, timezone handling - ⚡ Batch Generation — Create hundreds of documents in one request (async via webhook)

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Discovery — 📖 Full API Reference → — Detailed parameters, schemas, and examples

Credentials and setup notes

Configuration is passed through the environment: CARBONE_API_KEY, CARBONE_BASE_URL, CARBONE_TEST_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Carbone MCP's toolset — Discovery — is a fair guide to whether it matches your workflow. It is maintained by carboneio; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.