Skip to main content
Glama
carboneio

Carbone MCP

Official
by carboneio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Carbone MCP

No user-submitted related servers found.

    Related Servers

    • MCP Documents

      rofiqcp
      A
      license
      C
      quality
      D
      maintenance
      A unified MCP server for document processing that enables creating, editing, and converting Word documents (DOCX), PDFs, Markdown, and images, with support for templates, formatting, and batch operations.
      100
      MIT

    • markforge

      rafliiar17
      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

    • AnyDoc

      xianhong1208
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct actions on templates (upload, render, convert, inspect, delete, download). The main risk is convert_document vs render_document, which both take a file and produce a document, but the descriptions sharply differentiate them (no data vs data injection, keepTags). list_categories vs list_tags are also adjacent but serve distinct organizational concepts.

    Naming Consistency5/5

    All 12 tools follow a consistent snake_case verb_noun pattern (list_categories, list_templates, render_document, upload_template, delete_template, etc.). No mixing of conventions or vague verbs.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each tool maps to a real distinct capability (discovery, generation, lifecycle, metadata). No redundancy or padding.

    Completeness4/5

    Full template lifecycle is covered: create (upload), read (list/download), update (metadata), delete, plus render, convert, inspect, and discovery (capabilities, status, categories, tags). Minor gap: no dedicated get_template-by-id and versioning is managed indirectly via metadata rather than explicit version commands, but agents can work around this.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources