Skip to main content
Glama
xyyyang97

doc-agent-mcp

by xyyyang97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to doc-agent-mcp

No user-submitted related servers found.

    Related Servers

    • doc-version-mcp

      hjamet
      A
      license
      A
      quality
      B
      maintenance
      Enables local-first document versioning with content-addressable storage, word-level AST diffs, and AI-compliance auditing for LLM agents.
      6
      MIT

    • DPR MCP Server

      Janani879
      A
      license
      B
      quality
      C
      maintenance
      Enables safe, human-in-the-loop AI document collaboration by letting agents create isolated workspaces, edit tracked files, open reviewable Change Requests, and get human approval before merging, with Git-backed conflict detection and resolution.
      35
      MIT

    • docx-mcp-server

      OkamiFeng
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read, edit, and create Microsoft Word documents (.docx) with support for rich text, tables, and images, deployable locally or via SSE.
      3
      MIT

    • TeXFlow

      aaronsb
      A
      license
      A
      quality
      C
      maintenance
      Enables collaborative document authoring and composition with project-based organization, transforming Markdown and LaTeX content into professional PDFs with conflict-free multi-agent editing capabilities.
      6
      20
      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.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct operation: reading (read_document), outlining (get_outline), searching (find_text), comments (get_comments/propose_add_comment), editing via staging (propose_replace_text/insert/delete), change management (get/discard/apply_changes), and export/list backends. No two tools overlap in purpose, and the propose_* set is clearly separated from apply_changes.

    Naming Consistency5/5

    All 13 tools follow a consistent snake_case verb_noun pattern (e.g., read_document, propose_insert_block, discard_changes). Verbs are descriptive and uniformly applied, making the naming predictable and easy to infer.

    Tool Count5/5

    13 tools is well-scoped for a document editing server. Each tool covers a distinct lifecycle stage—read, inspect, search, comment, edit (staging), apply, export—without redundancy or excessive granularity.

    Completeness4/5

    The surface covers the core document workflow: reading, outlining, text search, editing (replace/insert/delete), comment creation, change staging/commit, and export. Minor gaps include no comment deletion/editing and no document creation, but these are outside the stated purpose of working with existing documents.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources