ragd-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAGD_URL | No | The URL of the ragd server. Overrides the default http://localhost:20250. | http://localhost:20250 |
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 |
|---|---|
| query_codebaseA | Fuzzy/semantic RAG search over a codebase indexed by ragd. Prefer this over Grep/Glob when the question is conceptual rather than an exact string/symbol match -- e.g. "where do we handle retry logic" or "how is auth configured" -- where you don't know the exact symbol/filename to search for. Returns a synthesized answer plus the source file excerpts it was drawn from. Args: query: Natural-language question about the codebase. resource: Name of the ragd resource to search. If omitted, the resource whose indexed directory contains the current working directory is used automatically. top_k: Number of source chunks to retrieve and ground the answer in (default 5, max 20). |
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 1 tool
With only one tool, there is no possibility of overlapping or confusable operations. query_codebase is clearly scoped to fuzzy/semantic codebase search rather than exact-match grep/glob.
query_codebase uses a clear verb_noun pattern and accurately describes the action and target. With a single tool, there is no naming inconsistency to create confusion.
One tool is the absolute minimum surface, making the server feel thin as a standalone integration. The narrow query-focused scope is defensible, but it is a borderline rather than fully developed toolset.
The server covers the core semantic search query flow, but it offers no way to list, inspect, or manage ragd resources. An agent can query successfully using auto-selection, yet resource discovery and index status information are notable gaps.