reed-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REED_MCP_URL | No | Where reed listens | http://localhost:8000 |
| REED_MCP_API_KEY | No | Sent as X-API-Key; set it when reed runs with REED_API_KEY | |
| REED_MCP_TIMEOUT_SECONDS | No | Per-request timeout | 120 |
| REED_MCP_MAX_EXCERPT_CHARS | No | Longer excerpts are truncated and marked excerpt_truncated | 2000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reed_searchA | Retrieve ranked evidence from the local reed index — no generation. Use this when you (the calling model) will write the answer: cite the
returned sources by filename and page/section. Each source carries The response also reports |
| reed_askA | Have reed's own local model answer, with audited citations. Runs reed's full pipeline: retrieval, evidence threshold, generation with
|
| reed_list_documentsA | List what the reed index knows about: one row per document. Returns |
| reed_get_documentA | Fetch the indexing status and metadata of one document by id. Returns the same shape as one reed_list_documents row. Useful to check
whether a just-uploaded document is |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.