A
licenseB
qualityC
maintenanceEnables MCP clients to render Markdown to HTML, estimate page counts, verify document delivery constraints, and atomically ship documents through a zero-dependency JSON-RPC stdio server.
4
MIT
carve-mcp
Officialby markup-carve
Related Servers
Alternatives to carve-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to parse markdown documents into structured AST nodes—including headings, lists, tables, callouts, and code blocks—and serialize modified AST back into clean canonical markdown via MCP tools.7MIT
- AlicenseBqualityBmaintenanceEnables an MCP-compatible assistant to read and edit live LaTeX source, upload and download project files, inspect history and review comments, and compile PDFs remotely or locally.208 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and export OpenPencil .fig and .pen files directly from disk, supporting operations like info, tree traversal, XPath queries, linting, and conversion to various formats without the desktop app or CLI.MIT
- AlicenseNot gradedqualityCmaintenanceEnables creating, reading, editing, and verifying PDF, Word, Excel, and PowerPoint documents through MCP tools that return structured results. It preserves source files by default for edits and supports local stdio operation without network requests.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to split Markdown into heading-based chunks with heading paths and line numbers, list outlines, retrieve sections by heading or anchor, and save chunks as JSONL for search, embeddings, or documentation bots.4MIT
TDQS
A3.5/5.0
Scored across 15 tools
Disambiguation2/5
The patch/edit cluster has unclear boundaries: carve_plan_ast_edit, carve_create_ast_patch, and carve_create_reversible_ast_patch all produce patches, while carve_apply_ast_patch and carve_apply_reversible_ast_patch both apply them, and carve_replace_source provides yet another source-editing path. An agent must reason carefully about reversible vs. non-reversible and AST-level vs. source-level before selecting, and carve_diagnose_and_fix partially overlaps with lint/format plus plan-and-apply flows.
Naming Consistency4/5
All names use the carve_ prefix with snake_case and a dominant verb_noun convention (create_ast_patch, apply_ast_patch, select_ast_nodes, get_block, replace_source). The only minor deviation is that several tools are verb-only (format, lint, render, parse, migrate), but the pattern remains predictable and readable.
Tool Count4/5
Fifteen tools is at the upper edge of a reasonable scope for a markup-language toolchain spanning parsing, formatting, linting, rendering, migration, and editing. However, the count is inflated by the redundant reversible/non-reversible patch pairs, so not every tool clearly earns an independent place.
Completeness4/5
The surface covers the full lifecycle well: parse, format, lint, render across multiple targets, migrate, diagnose/fix, inspect blocks, and create/apply patches with undo. Minor gaps exist around direct document persistence (tools explicitly avoid writing files) and general insertion/append operations outside the patch model, but agents can work around these.
Maintenance
ActivityActive
ResponsivenessUsually handled