knowledge-base-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_documentB | Add a new document to the knowledge base. |
| searchA | Search the knowledge base by free-text terms and/or labels. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_document | Generate a prompt asking the model to summarize a document. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
add_document and search have completely distinct purposes: adding vs. finding documents. There is no overlap in functionality.
Both tool names are verbs, but add_document uses verb_noun while search uses a bare verb. The pattern is mostly consistent with a minor deviation.
Only 2 tools for a knowledge base server is too few. Typical operations like get, update, and delete are missing, making the surface feel incomplete.
The tools cover only 'add' and 'search', lacking retrieval by ID, update, and delete. This severely limits agent workflows for managing a knowledge base.