Skip to main content
Glama
metaneutrons

doc-tools-mcp

by metaneutrons
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to doc-tools-mcp

No user-submitted related servers found.

    Related Servers

    • cite-rag-mcp

      xiaofei03
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server for evidence-safe academic citation workflows, including verified-reference retrieval, Zotero duplicate detection and import, and Word export via Pandoc with zotero.lua.
      1
      -

    • zotero-mcp

      Robernetes
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects to a local Zotero library, enabling search, citation generation with CSL styles, and automatic bibliography updates in Markdown documents.
      109 npm
      MIT

    • OokCite MCP Server

      TurtleTech-ehf
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that validates DOIs, formats citations, manages bibliography collections, and catches fabricated references, returning citation metadata only. It works with MCP clients over stdio and supports both basic and API-key-based usage.
      2
      MIT

    • zotero-grounded-mcp

      msantelli
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives any MCP-compatible assistant access to your Zotero reference library, enabling search, citation, bibliography generation, and .docx processing while keeping Zotero as the ground truth for references.
      9
      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.9/5.0

    Scored across 14 tools

    Disambiguation5/5

    The bib:* and ctverify:* namespaces cleanly separate bibliography management from citation verification. Within each group, tools like get, search, exists, list, and stats have clearly distinct purposes, so an agent is unlikely to select the wrong one.

    Naming Consistency4/5

    The namespace:action pattern is consistent and readable, with snake_case action names like bib:list and ctverify:bulk-update. The only minor deviations are noun-style actions such as bib:stats and ctverify:status, plus the hyphenated bulk-update.

    Tool Count5/5

    Fourteen tools is well-scoped for a server covering bibliography management and citation verification. Each tool represents a distinct operation, and the split of 9 bibliography tools and 5 verification tools feels balanced without unnecessary bloat.

    Completeness4/5

    The bibliography side covers CRUD, search, validation, existence checks, and statistics, while the verification side covers extraction, status tracking, and batch updates. Minor gaps exist, such as no way to list all bibliography entries without specifying a CSL type and no delete operation for verification registry entries, but these are workable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources