knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSPORT | No | Transport protocol: stdio, http, or sse. Defaults to stdio. | stdio |
| KNOWLEDGE_ROOT | No | Path to knowledge sources. | |
| LEXICAL_PROVIDER | No | Lexical search provider: sqlite_fts (default) or disabled. | sqlite_fts |
| SEMANTIC_PROVIDER | No | Semantic search provider: disabled (default) or qdrant. | disabled |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| knowledge_searchA | Search for knowledge documents matching a query. Returns relevant documents ranked by relevance. |
| knowledge_getA | Get the full content of a specific knowledge document by its document ID. Can retrieve specific sections. |
| knowledge_listB | List knowledge documents with optional filtering by scope and prefix. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| System Status | Current status of the Knowledge MCP server including provider health and configuration |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: knowledge_search for query-based relevance, knowledge_get for retrieving by ID, and knowledge_list for enumerating with filters. No overlap in functionality.
All tool names follow a consistent pattern: knowledge_ + verb (search, get, list). The naming is uniform and predictable, with no mixed conventions.
Three tools is a well-scoped count for a read-focused knowledge server. Each tool covers a distinct core operation (search, retrieve, list) without unnecessary bloat.
The server is entirely read-only, offering no operations to create, update, or delete knowledge documents. For a domain implied as 'knowledge management', this is a significant gap that would prevent agents from writing to the knowledge base.