rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| index_documentA | Index a document into the knowledge base so it can be searched. Reads the file at Args: file_path: Absolute path to the file to index. Supported types: .pdf .md .txt .py .js .ts .json .yaml .yml Returns: A summary string describing what was indexed. |
| search_docsA | Semantically search the knowledge base for content related to The query is embedded using the same model used during indexing. ChromaDB finds the N most similar chunks using cosine similarity. Lower distance = more relevant. Args: query: Natural-language question or keyword phrase. n_results: How many results to return (default 5, max 20). source_filter: If non-empty, restrict search to chunks from this specific document (exact filename, e.g. "notes.md"). Returns: Formatted string with matching chunks, their sources, and distances. Returns a helpful message if the knowledge base is empty. |
| list_indexed_docsA | List all documents currently indexed in the knowledge base. Returns one entry per document with its filename, file type, number of chunks, and when it was last indexed. Returns: Formatted string listing all documents, or a message if empty. |
| delete_documentA | Remove a document and all its chunks from the knowledge base. This is useful when a document has been updated (you'll delete then re-index it) or when you no longer need it to be searchable. Args: source: The filename of the document to remove, e.g. "design_doc.pdf". Use list_indexed_docs to see valid filenames. Returns: Confirmation message with the number of chunks deleted. |
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 clearly distinct purpose: index, delete, list, and search. No overlap or ambiguity in their functionality.
All tools follow a consistent verb_noun pattern (delete_document, index_document, search_docs, list_indexed_docs). The slight variation in list_indexed_docs is still predictable.
4 tools is well-scoped for a RAG knowledge base server. It covers the essential operations without unnecessary bloat or missing core functionality.
The tool surface covers the complete lifecycle: indexing (create), listing (read), searching (query), and deleting. Update is handled via delete+re-index, which is acceptable for this domain.