Carbone MCP
OfficialRelated Servers
Alternatives to Carbone MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA universal MCP server for document processing, conversion, and automation. Handle PDF, DOCX, HTML, Markdown, and more through a unified API and toolset.137 npm140MIT
- AlicenseCqualityDmaintenanceA unified MCP server for document processing that enables creating, editing, and converting Word documents (DOCX), PDFs, Markdown, and images, with support for templates, formatting, and batch operations.100MIT
- FlicenseAqualityCmaintenanceMCP server for rendering, parsing, converting, and editing Office documents (Excel, PowerPoint, Word) from a structured JSON spec, using LibreOffice WASM for conversion and preview.51-
- AlicenseAqualityDmaintenanceMCP server for Word document (.docx) creation and manipulation — the production-grade document automation tool for AI agents.932 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to compile markdown into DOCX, PDF, or HTML with customizable templates, analyze documents for ATS optimization, and retrieve template skeletons via MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables document conversion and processing through MCP, including Office/PDF/Markdown conversions, OCR, and PDF operations like split, rotate, encrypt, and extract.MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: template CRUD, rendering, conversion, and API introspection are well separated. The only potential ambiguity is between convert_document and render_document, but their descriptions strongly differentiate template-preserving conversion from data-injection rendering.
All tools follow a consistent verb_noun snake_case pattern: list_templates, upload_template, render_document, get_api_status, etc. This makes the tool surface predictable and easy to navigate.
11 tools is well-scoped for a document templating and rendering service: template CRUD, listing/management, conversion, rendering, and discovery/status each have a place. No redundancy or bloat.
The surface covers template CRUD (upload, list, download, delete, update metadata), rendering, conversion, category/tag discovery, and API health. This is comprehensive for Carbone's core workflows; no obvious dead ends.