Knowledge Base MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level | INFO |
| CATEGORIES | No | Categories (comma-separated) | people,recipes,meetings,procedures,tasks |
| SERVER_NAME | No | Server name | Knowledge Base |
| KNOWLEDGE_BASE_PATH | No | Knowledge base location | ~/knowledge-base |
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 |
|---|---|
| create_categoryC | Create a new category or subcategory in the knowledge base |
| delete_categoryC | Delete a category and optionally all its contents |
| rename_categoryB | Rename a category while keeping it in the same parent location |
| move_categoryC | Move a category to a different parent location |
| list_categoriesB | List all categories in a hierarchical tree structure |
| add_noteB | Create a new note in the knowledge base (supports hierarchical categories) |
| search_notesB | Search through all notes by query, category path, or tags |
| get_noteC | Retrieve the full content of a specific note |
| update_noteC | Update an existing note's content or tags |
| list_notesB | List all notes, optionally filtered by category path or tag |
| delete_noteC | Delete a note from the knowledge base |
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 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are clearly separated by resource (note vs. category) and action (create, delete, get, list, update, etc.), making it easy for an agent to select the correct one without confusion.
All tool names follow a consistent verb_noun pattern (e.g., add_note, create_category, list_notes). The naming is uniform throughout, using snake_case and clear action verbs that align with the tool's function.
With 11 tools, the count is well-scoped for a knowledge base server. Each tool serves a distinct and necessary function, covering core operations for managing notes and categories without being excessive or insufficient.
The tool set provides complete CRUD/lifecycle coverage for both notes and categories. It includes creation, retrieval, updating, deletion, listing, and search operations, with no obvious gaps that would hinder agent workflows in this domain.