Skip to main content
Glama
muhammadismailkhan0009

docs-navigation-mcp

by muhammadismailkhan0009
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to docs-navigation-mcp

No user-submitted related servers found.

    Related Servers

    • ragmark

      cdcoonce
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server for retrieval over markdown wikilink vaults, offering hybrid vector+lexical search, note reading, neighbor expansion, and recent activity tracking with fully local embeddings and no network egress.
      MIT

    • litecontext-cli

      Aries-0331
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP server that indexes Markdown/Obsidian folders and lets AI clients retrieve cited local context through MCP.
      MIT

    • pdf-context

      mematcha
      A
      license
      A
      quality
      D
      maintenance
      A local-first MCP server that ingests PDFs, extracts structure, and provides semantic search and sequential navigation tools for AI clients to query and learn from documents.
      10
      MIT
    • Chilon Recall by ctrlcakepro

      Chilon Recallofficial

      ctrlcakepro
      A
      license
      A
      quality
      A
      maintenance
      Local-first knowledge retrieval MCP server that turns private text documents into a source-backed knowledge base, enabling retrieval, comparison, summaries, and review outlines for any local MCP client while keeping source paths and index operations visible.
      13
      437 npm
      2
      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.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource (sources vs nodes) with a clear action (list, fetch, create, add, update, remove). No overlapping purposes; an agent can reliably select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_sources, add_nodes, remove_source, etc.). The convention is uniform and predictable.

    Tool Count5/5

    8 tools is well within the ideal range for a docs navigation server. Each tool serves a distinct purpose and the set is neither sparse nor bloated.

    Completeness4/5

    The surface covers source and node lifecycle (create, list, fetch, add, update, remove). Minor gap: no explicit source metadata update, but remove_source covers deletion and list_sources provides enumeration. Overall, core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources