Skip to main content
Glama
markup-carve

carve-mcp

Official
by markup-carve

Related Servers

Alternatives to carve-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      F
      maintenance
      IntentText 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.
      20 npm
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      An 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.
      18
      14,742 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables document conversion and processing through MCP, including Office/PDF/Markdown conversions, OCR, and PDF operations like split, rotate, encrypt, and extract.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    TDQS

    A3.8/5.0

    Scored across 13 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive