recall-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECALL_DOCS_DIR | No | Path to the directory containing .md and .txt documents to index | /absolute/path/to/recall-mcp/data/documents |
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 |
|---|---|
| search_documentsA | Search the knowledge base for passages relevant to a query. Args: query: What to look for, in natural language or keywords. limit: Maximum number of passages to return (1-50, default 5). mode: "auto" (semantic if available, else keyword), "semantic", or "keyword". Use "keyword" to force exact-word matching. Returns: The most relevant passages, each labelled with its source and score. |
| list_sourcesB | List the documents in the knowledge base and the active search mode. |
| get_documentA | Return the full text of one document by its source name. Use list_sources first to see valid names. The caller can then read or summarise the returned text. |
| add_noteA | Save a new note to the knowledge base and index it immediately. Args: title: A short title; also used to name the file. content: The note body (plain text or Markdown). Returns: A confirmation with the created document's source name. |
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: adding notes, retrieving a specific document, listing sources, and searching. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case: add_note, get_document, list_sources, search_documents. The pattern is uniform and predictable.
4 tools is slightly below average but still reasonable for a focused knowledge base server. It covers core operations without being too sparse or excessive.
The tool set provides create, read, and search capabilities but lacks update and delete operations. This is a significant gap for managing a knowledge base, as agents cannot modify or remove notes.