carve-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| carve_lintA | Check Carve source for author-facing problems and silent degradation. |
| carve_diagnose_and_fixB | Diagnose Carve source, propose bounded fixes, and optionally apply selected safe fix IDs with forward and undo patches. Writer-review fixes are never applied automatically. |
| carve_formatA | Format Carve source canonically and report any lossy raw-format nodes. |
| carve_renderA | Render Carve to HTML, Markdown, plain text, or ANSI terminal text, with loss reporting. |
| carve_check_targetsA | Compare one Carve document across HTML, Markdown, plain text, ANSI, GitHub, WordPress, and PDF-stage profiles, returning target-specific warnings, losses, and fallbacks. |
| carve_parseA | Parse and resolve Carve into its position-aware interchange AST. |
| carve_create_ast_patchA | Compare two PART 12 Carve ASTs and return position-independent add, replace, and remove operations. |
| carve_apply_ast_patchA | Validate and apply structured operations to a PART 12 Carve AST, returning the patched AST and canonical Carve source. |
| carve_select_ast_nodesA | Resolve a heading ID, footnote label, node type, or current AST path to reviewable PART 12 AST paths without silently choosing among multiple matches. |
| carve_plan_ast_editA | Plan one or more atomic semantic AST edits and return a human-readable, reversible, stale-guarded source patch without writing the document. |
| carve_create_reversible_ast_patchA | Compare two PART 12 ASTs and return forward and inverse operations with semantic stale-edit fingerprints. |
| carve_apply_reversible_ast_patchA | Verify a reversible AST patch against source, apply or undo it, and return a minimal stale-guarded UTF-8 source edit without writing files. |
| carve_migrateA | Migrate HTML, Markdown, Djot, or BBCode source to Carve with version 2 fidelity diagnostics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review-document | Review a Carve document for clear, correct, human-focused writing. |
| convert-markdown | Convert Markdown to Carve while explaining fidelity warnings. |
| prepare-for-github | Check a Carve document for GitHub-specific publishing surprises. |
| explain-warnings | Turn Carve diagnostics into concise, actionable writing guidance. |
| preview-document | Render and assess a document without changing its source. |
| review-workspace | Review an authorized documentation workspace as a bounded project. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| carve-authoring-guide | Concise, human-facing guidance for common Carve writing tasks. |
| carve-rule-index | Versioned map of the normative rule categories and lookup resource. |
TDQS
Scored across 13 tools
Most tools target distinct operations, but the create_ast_patch/create_reversible_ast_patch and apply_ast_patch/apply_reversible_ast_patch pairs have heavily overlapping purposes and could cause misselection. Similarly, plan_ast_edit and diagnose_and_fix both surface proposed changes, though their intended workflows differ. Overall, descriptions help, but boundaries between the patch-related tools are not crisp.
All tools follow a consistent carve_ prefix with snake_case verb_noun naming, e.g. carve_parse, carve_render, carve_migrate, carve_create_ast_patch. The pattern is predictable and makes the purpose of each tool clear from its name alone.
With 13 tools, the server is well within the ideal 3-15 range for a domain-specific toolset. Each tool covers a distinct phase of the Carve document workflow: parsing, rendering, formatting, linting, migrating, patching, and cross-target checking. The count feels proportional to the complexity of the domain.
The toolset covers a comprehensive document lifecycle: parse, edit via AST patches, render, format, lint, migrate, check target compatibility, and diagnose/fix. Minor gaps include a lack of direct high-level document creation or deletion operations, though these can be handled through migration and AST patch operations. Overall, agents should be able to complete most Carve authoring and conversion workflows without dead ends.