Skip to main content
Glama
jgravelle

jdocmunch-mcp

by jgravelle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jdocmunch-mcp

No user-submitted related servers found.

    Related Servers

    • PureContext MCP

      goranocokoljic
      A
      license
      Not graded
      quality
      B
      maintenance
      Indexes codebases and lets AI agents retrieve precise code snippets (functions, classes, routes) instead of reading entire files, reducing token usage and improving accuracy.
      169 npm
      7
      MIT

    • gus

      SUD747
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI coding agents to retrieve only the specific code sections that answer their questions, drastically reducing context usage while running fully locally.
      MIT

    • mcp-code-indexer

      fluffypony
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to intelligently navigate and understand codebases by providing instant file descriptions, semantic search, and context-aware recommendations, eliminating the need to repeatedly scan files.
      20
      MIT

    • search-docs

      otolab
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search local Markdown documents using natural language, with automatic indexing and section-level retrieval.
      10
      5 npm
      1
      MIT

    • shuck-file

      Shan-Zhu
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with document conversion to Markdown, intelligently routing small and large files, and enabling targeted extraction via sections, search, and token budgets.
      6
      MIT

    • doctree-mcp

      joesaby
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agentic document retrieval over markdown, CSV, and JSONL using BM25 and tree navigation, without vector databases or embeddings, allowing AI agents to search, browse, and retrieve structured document sections.
      22 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 64 tools

    Disambiguation3/5

    Many tools are carefully differentiated, but the set contains numerous overlapping section-navigation and health-inspection tools (get_section_context vs describe_section, get_doc_health vs doc_health_radar vs get_wiki_stats, get_related_sections vs section_neighbors). The detailed descriptions help, but the boundaries are subtle enough that an agent could easily misroute a query.

    Naming Consistency2/5

    Names are all snake_case, but conventions are mixed: get_* verbs dominate, yet doc_list_repos, doc_index_repo, and doc_resolve_repo lead with a noun, while section_neighbors is noun-first. Similar operations are inconsistently prefixed (doc_health_radar vs get_doc_health, doc_list_repos vs list_docs), making predictable lookup hard.

    Tool Count1/5

    64 tools is far beyond the 25+ threshold, and many are micro-wrappers or batch variants (get_section_excerpt vs get_section_excerpts, get_section_summary vs get_section_summaries) that could be consolidated. This overwhelms the tool-selection surface for what is essentially a docs-indexing/query domain.

    Completeness4/5

    The surface is impressively complete for a documentation indexer: indexing, search, TOC, section retrieval, health/drift, link analysis, wiki stats, OpenAPI, glossary, and code-symbol bridging are all covered. Minor gaps such as a single consolidated re-index/refresh tool or cross-repo search without groups are workable, but the domain is thoroughly addressed.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources