MCP Knowledge Base Server
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledge_baseA | Search the company knowledge base with natural language or keywords. Use this FIRST whenever a question might be answered by internal documentation (processes, runbooks, policies, architecture, onboarding…). |
| get_documentA | Fetch the full Markdown content of one knowledge-base article. |
| list_documentsA | List every article in the knowledge base, optionally filtered. |
| list_tagsA | List all tags used across the knowledge base, with document counts. |
| reload_knowledge_baseA | Re-scan the knowledge-base directory to pick up new or edited articles. Returns: Number of documents now indexed. |
| statsB | Basic knowledge-base statistics (document count, tags, index age). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| answer_from_knowledge_base | Ground an answer in the knowledge base: searches first, then answers with citations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| kb_index_resource | Human-readable index of the whole knowledge base. |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: searching, fetching full documents, listing documents, listing tags, reloading the index, and showing stats. There is no overlap that would cause an agent to select the wrong tool.
All tool names follow a consistent verb_noun pattern (search_, get_, list_, reload_, etc.). The pattern is predictable and easy to infer for additional tools.
Six tools is well within the ideal range for a knowledge base server. Each tool serves a distinct function, and the count feels neither too sparse nor bloated.
The tool set covers all core operations: search, read, list, and maintenance. Minor gaps exist (e.g., no tool to add or delete documents via the API, but that may be intentionally managed filesystem-side). Reload and stats provide necessary lifecycle support.