Skip to main content
Glama
SamamaSaleem

mcp-document-assistant

by SamamaSaleem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-document-assistant

No user-submitted related servers found.

    Related Servers

    • Docalyze

      LunarPerovskite
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that lets AI assistants read and visually analyze local documents — PDFs, Excel spreadsheets, CSV files, Word documents, PowerPoint presentations, and images.
      4
      42 npm
      72 PyPI
      MIT

    • KnowledgeMCP

      maxzrff
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to perform semantic searches over local document collections using multi-context organization and automatic OCR. It supports various file formats including PDF, DOCX, and images, ensuring all data processing remains local and private.
      8
      MIT

    • Google Documents MCP

      0PValencia
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to manage Google Docs through natural language, including listing, reading, creating documents, and appending text. It features a simple browser-based OAuth login and persistent sessions.
      MIT

    • gdocs-mcp

      apurwa
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Google Docs and Sheets that enables AI assistants to read, create, edit, style, export, and collaborate on documents using local OAuth authentication.
      26 npm
      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

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing document IDs, reading a document's contents, and editing an existing document. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_documents, read_document, edit_document. The naming is predictable and easy to infer.

    Tool Count5/5

    With only 3 tools, the server is tightly focused on core document operations. Each tool serves a distinct need, and the count is well within the ideal range.

    Completeness2/5

    The tool surface covers listing, reading, and editing documents but lacks create and delete operations, which are fundamental to document lifecycle management. This is a significant gap that will likely force agents to rely on external processes for these actions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources