carve-mcp
OfficialRelated Servers
Alternatives to carve-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.4MIT
- 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

intenttextofficialprivate
AlicenseNot gradedqualityFmaintenanceIntentText MCP server lets AI agents parse, validate, query, diff, and render IntentText (.it) documents. It exposes 9 tools for safe parsing, workflow validation, HTML/print rendering, template merging, and round-trip source generation.27 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to research game mods by searching documentation and definitions, inspecting dependencies and playsets, validating saved files with structural and Tiger checks, and preparing or editing mod content with preview and write controls. It also supports starting or previewing the game through a local stdio connection.22 npmGPL 3.0
- AlicenseAqualityFmaintenanceAn MCP server that exposes documents.js's document conversion, .odb, metadata, and font tooling as MCP tools, enabling agents to convert, inspect, and edit a wide range of document formats over stdio.18324 npmMIT
TDQS
Scored across 15 tools
The editing surface contains overlapping clusters: carve_create_ast_patch vs carve_create_reversible_ast_patch both diff two ASTs, and carve_apply_ast_patch vs carve_apply_reversible_ast_patch both apply ops. carve_plan_ast_edit, carve_replace_source, and the reversible-patch tools all perform source edits, so boundaries rely on descriptions (fingerprints, inverse ops, stale-guards) rather than being self-evident.
Every tool uses the uniform carve_<verb>_<noun> snake_case pattern, with a stable carve_ prefix across all 15 tools. Verb choices (parse, render, lint, format, apply, create, migrate) map predictably to their actions.
15 tools is at the upper edge for this domain but each has a defensible role (parse, render, lint, format, migrate, target-check, and AST/source editing). The redundant reversible vs non-reversible patch pairs suggest a couple of tools could be consolidated.
The surface covers the full markup lifecycle: parse, render across targets, lint, format, migrate, plus segmented AST selection, source splicing, and reversible patches. Minor gaps remain around higher-level document validation/round-trip verification, but core workflows are present.