ragmap
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AGENT_NAME | No | Optional agent name header. | |
| SERVICE_VERSION | No | Optional version override. | |
| RAGMAP_API_BASE_URL | No | Optional API base URL override. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rag_find_serversC | Search/filter RAG-related MCP servers from the RAGMap subregistry. |
| rag_top_serversC | Get top recommended retriever MCP servers with smart defaults. |
| rag_get_serverA | Fetch a server record by registry name (latest version). Use the exact name from the registry, e.g. io.github.khalidsaidi/ragmap for RAGMap. |
| rag_list_categoriesA | List all RAG categories known to RAGMap. |
| rag_explain_scoreB | Explain RAGMap scoring for a server. Use the registry server name, e.g. io.github.khalidsaidi/ragmap for RAGMap. |
| rag_get_install_configC | Get copy-ready Claude Desktop and generic MCP host config for a server. |
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 6 tools
Each tool has a clearly distinct purpose: explaining scoring, searching servers, getting config, fetching server details, listing categories, and retrieving top servers. No overlap despite similar domains.
All tools follow a consistent 'rag_<verb>_<noun>' pattern, making it easy to predict functionality. The naming is uniform and intuitive.
6 tools is a well-scoped set for a registry service, covering essential operations without being excessive or insufficient.
The tool surface covers all typical registry use cases: search, browse, get details, get config, and top recommendations. No obvious gaps for a read-only consumer-facing registry.