AI Knowledge Base MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_KB_MCP_PRIVATE | No | Set to '1' to enable private mutation tools (add_channel, sync_now). Default is empty (public read-only profile). |
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 |
|---|---|
| searchB | Search the AI knowledge base for relevant content. Uses the shared retrieval spine (hybrid → fusion → optional CE). Public results cite source_id / source_url — never absolute filepath. |
| discoverB | Discover AI content without a specific query (honest browse/digest/heuristics). Modes: random, digest, concepts, channels — not a ranking product. |
| get_contextC | Get comprehensive context via shared retrieval (+ optional recent digest). |
| get_statusA | Get current status of the AI knowledge base. Does not require embedding / Ollama for index stats (Ollama health is reported). |
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 distinct purpose: discover for exploration, search for query-based retrieval, get_context for comprehensive context, and get_status for system health. However, get_context and search may cause slight confusion as both involve retrieval.
Tool names are verbs but mix single-word (discover, search) and verb_noun patterns (get_context, get_status). This inconsistency could be improved by normalizing to a single pattern.
Four tools is a minimal but reasonable set for a knowledge base query interface. It covers core functions without bloat, though it could be expanded slightly for more granularity.
The toolset focuses on reading and exploration but lacks write operations (e.g., add, update, delete content). This may hinder agents needing to modify the knowledge base.