senza-knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENZA_KB_MODEL | Yes | Model ID (e.g., 'deepseek-v4-flash', 'claude-sonnet-4-5'). | |
| SENZA_KB_API_KEY | Yes | Provider API key. | |
| SENZA_KB_DOMAINS | No | Comma-separated domain tags. | |
| SENZA_KB_RAW_DIR | No | Raw layer directory (defaults to '.'). | . |
| SENZA_KB_BASE_URL | Yes | Provider endpoint URL. | |
| SENZA_KB_PROVIDER | Yes | Provider name: 'openai' (OpenAI-compatible) or 'anthropic'. |
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 |
|---|---|
| kb_askA | Answer a question grounded in the domain knowledge base (uses an internal agent to search and synthesize; may take ~10s). |
| kb_searchA | Search the knowledge base (semantic, via internal agent); returns matching source identification + snippets. Use kb_get to fetch full text. |
| kb_getB | Fetch the full markdown of a knowledge document by source_id or file name (fast, no LLM involved). |
| kb_listA | List all documents in the knowledge base (source_id, name, size, dates). |
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
kb_list, kb_search, kb_get, and kb_ask each target a distinct user intent: catalog browsing, source retrieval, full-text fetching, and synthesized answering. The only close pair, kb_ask vs kb_search, is clearly disambiguated by their outputs: an answer versus source snippets.
All tools follow a uniform kb_<verb> pattern with simple, clear verbs. There are no mixed conventions or vague names.
Four tools is appropriate for a focused read-only knowledge base server. Each tool covers one core operation and none feel redundant or missing.
The read-side lifecycle is complete: list, search, get, and ask cover discovery through consumption. Write/management operations are absent, but they appear outside the server's intended purpose.