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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledgeB | Search the knowledge base for relevant information. Use this when you need to find specific facts or documentation. |
| list_categoriesB | List all available knowledge base categories |
| get_by_categoryC | Get all knowledge base entries for a specific category |
| get_by_idC | Get a specific knowledge base entry by its ID |
| advanced_searchC | Search with additional filters like category and result limit |
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 5 tools
There is some overlap between 'advanced_search' and 'search_knowledge', as both are for searching, though 'advanced_search' adds filters. 'get_by_category' and 'list_categories' are distinct but related. The descriptions help differentiate, but an agent might initially confuse the two search tools.
Most tools follow a clear verb_noun pattern (e.g., 'get_by_id', 'list_categories'), with 'advanced_search' and 'search_knowledge' being slight deviations. The naming is mostly consistent and readable, with only minor inconsistencies in verb usage.
With 5 tools, this server is well-scoped for a knowledge base domain. Each tool serves a distinct purpose (searching, retrieving by ID/category, listing categories), and the count is appropriate without being too sparse or overwhelming.
The toolset covers core CRUD-like operations for a knowledge base: searching, retrieving by ID and category, and listing categories. A minor gap is the lack of create, update, or delete tools, but for a read-only knowledge base server, this is reasonable and agents can work around it.