Carve MCP server

Give MCP-compatible assistants the same Carve parser, linter, formatter, and renderers used by the JavaScript implementation. Filesystem access is absent by default and can be enabled for explicitly configured document roots.

Tools

• carve_lint checks a document and returns precise, structured warnings.
• carve_format produces canonical Carve and reports rendering losses.
• carve_render renders HTML, Markdown, plain text, or ANSI.
• carve_parse returns the resolved, position-aware interchange AST.
• carve_create_ast_patch compares two interchange ASTs and returns a position-independent patch.
• carve_apply_ast_patch validates and previews a patch as both an AST and canonical Carve source without changing files.
• carve_migrate converts HTML, Markdown, or Djot and reports migration fidelity.

Tools return concise text for readers alongside schema-validated structured results for clients. Six optional prompts guide common review, conversion, and publishing workflows without replacing the writer's judgment.

Raw HTML passthrough is disabled by default because MCP inputs are untrusted. The server has no filesystem access unless you explicitly give it a workspace root.

Resources

• carve://guide is a concise authoring quick start.
• carve://rules explains the normative rule categories.
• carve://rules/{ruleId} looks up a stable normative CARVE-* rule ID, such as carve://rules/CARVE-P0-001.
• carve://lint-rules/{ruleName} explains a stable diagnostic name returned by carve_lint.

The resources identify the Carve version and link to the complete documentation when a reader needs normative detail. Lint diagnostic names are a separate namespace and are returned with their explanations directly by carve_lint.

Get started

Node.js 20 or newer is required.

npx -y @markup-carve/carve-mcp

See Connect Carve to your writing tool for copy-ready setup in Claude, VS Code, Cursor, Zed, and Codex, plus prompts to confirm it works. The compatibility page explains what CI verifies and provides the short host smoke test used for releases.

The writer workflows show practical review, conversion, preview, GitHub publishing, and documentation-folder tasks.

For local builds, workspace access, native binaries, HTTP and container deployment, and contributor checks, see Development and deployment.

This project is licensed under the MIT License.