Skip to main content
Glama
mcpc-tech

Docsmith MCP

by mcpc-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Docsmith MCP

No user-submitted related servers found.

    Related Servers

    • Nutrient Document Engine MCP

      PSPDFKit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and users to process documents through natural language, supporting PDF operations like text extraction, redaction, splitting, form filling, annotations, and content search.
      43 npm
      62
      MIT

    • docx-editor-mcp

      merzano369
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to create, edit, and extract data from Microsoft Word documents programmatically, supporting document creation, content editing, table manipulation, parameter extraction, and template generation.
      1
      MIT

    • Office Word MCP Server

      franlealp1
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to create, read, and manipulate Microsoft Word documents with comprehensive formatting, table creation, content management, and document protection capabilities. Supports advanced operations like merging documents, PDF conversion, and rich text formatting through a standardized interface.
      32
      MIT

    • office-worker-mcp

      CaFra-House
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create and process office documents locally, including generating branded PDF, Word, Excel, and editable PowerPoint files from templates and themes, plus reading, OCR, form-filling, manipulation, and conversion of PDFs.
      1
      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

    B3.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct in purpose: get_document_info for metadata, read_document for reading content, write_document for writing content, and run_python for custom operations. However, run_python could overlap with read_document and write_document for file operations, potentially causing confusion about when to use it versus the specialized tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: get_document_info, read_document, run_python, write_document. This makes them predictable and easy to understand, with no deviations in style.

    Tool Count4/5

    With 4 tools, the count is reasonable for a document processing server, covering core operations like reading, writing, and metadata retrieval. However, it feels slightly thin as it lacks tools for operations like document conversion, editing, or deletion, which might be expected in a comprehensive document toolset.

    Completeness3/5

    The toolset covers basic read, write, and metadata operations, but has notable gaps for a document processing domain. Missing operations include document conversion (e.g., to different formats), editing (e.g., modifying content without full rewrite), and deletion, which could limit agent workflows and cause dead ends in complex tasks.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources