Skip to main content
Glama
Ulzuhan

reed-mcp

by Ulzuhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to reed-mcp

No user-submitted related servers found.

    Related Servers

    • rag-mcp

      Swabhimanc
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only MCP tools for hybrid semantic and keyword search over locally indexed PDF documentation, with citations and context retrieval for LLM agents.
      -

    • rag-retriever-mcp

      code-lawyer
      F
      license
      A
      quality
      D
      maintenance
      A local-first document retrieval engine that mounts as an MCP tool for agents to index files, search for relevant passages, and let the agent's own LLM answer.
      4
      -
    • dryad-rag-mcp by DryadAI

      dryad-rag-mcpofficial

      DryadAI
      A
      license
      A
      quality
      C
      maintenance
      Exposes a RAG document-search API as MCP tools (rag_health, rag_ingest, rag_query), enabling agents to index and search markdown documents with cited results through natural language.
      3
      MIT

    • mcp-docs-ask

      alyiox
      A
      license
      Not graded
      quality
      B
      maintenance
      Local RAG MCP server for documentation that indexes markdown repos (local paths or git URLs) and provides retrieval-only tools (ask_docs, list_docs, reindex) returning grounded passages and citations for the MCP host to synthesize answers.
      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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinctly different purpose: reed_search returns raw evidence without generation, reed_ask generates a cited answer, reed_list_documents enumerates the index, and reed_get_document fetches a single document's metadata. The descriptions explicitly separate search from ask and list from get, eliminating any ambiguity.

    Naming Consistency4/5

    All tool names consistently use the reed_ prefix and snake_case, but the pattern is slightly inconsistent: reed_search and reed_ask are verb-only, while reed_list_documents and reed_get_document are verb_noun. This is still readable and predictable, just a minor deviation from a uniform verb_noun convention.

    Tool Count5/5

    Four tools is a well-scoped set for a document retrieval and Q&A server. Each tool covers a distinct core function—search, ask, list, and get—without any unnecessary bloat, landing comfortably within the ideal 3-15 tool range.

    Completeness4/5

    The set covers the read/query side well: searching, asking, listing documents, and inspecting document status. However, it lacks write operations (add/remove/update documents) and cannot retrieve full document content beyond search excerpts, which are minor gaps if the server is intended to manage the index end-to-end. For its apparent read-focused purpose, the core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources