mcp-knowledge-base
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_noteA | Create a new note in the knowledge base. Args: title: A short descriptive title for the note. content: The full body/content of the note (supports markdown). tags: Optional list of tags for categorization (e.g. ["python", "tutorial"]). Returns: The newly created note with its assigned ID. |
| search_notesA | Full-text search across all notes (titles, content, and tags). Args: query: Search query string. Supports FTS5 syntax (e.g. "python OR rust"). limit: Maximum number of results to return (default 10). Returns: List of matching notes ranked by relevance. |
| list_notesA | List all notes, optionally filtered by a tag. Args: tag: If provided, only return notes containing this tag. limit: Maximum number of notes to return (default 20). Returns: List of notes, newest first. |
| get_noteA | Retrieve a single note by ID. Args: note_id: The unique ID of the note. Returns: The note if found, or None. |
| update_noteA | Update an existing note. Only provided fields are changed. Args: note_id: The ID of the note to update. title: New title (optional). content: New content (optional). tags: New tags list (optional). Returns: The updated note, or None if not found. |
| delete_noteA | Delete a note by ID. Args: note_id: The ID of the note to delete. Returns: True if the note was deleted, False if not found. |
| add_taskA | Create a new task. Args: title: Short task title. description: Detailed description of what needs to be done. priority: One of "low", "medium", "high", or "urgent". due_date: Optional due date in ISO format (YYYY-MM-DD). tags: Optional list of tags. Returns: The newly created task. |
| list_tasksA | List tasks with optional filters. Args: status: Filter by status ("todo", "in_progress", or "done"). priority: Filter by priority ("low", "medium", "high", "urgent"). tag: Filter by a specific tag. Returns: List of matching tasks ordered by priority then due date. |
| update_taskA | Update a task. Only provided fields are changed. Args: task_id: The ID of the task to update. title: New title (optional). description: New description (optional). status: New status: "todo", "in_progress", or "done" (optional). priority: New priority: "low", "medium", "high", or "urgent" (optional). due_date: New due date in ISO format (optional). tags: New tags list (optional). Returns: The updated task, or None if not found. |
| delete_taskA | Delete a task by ID. Args: task_id: The ID of the task to delete. Returns: True if deleted, False if not found. |
| get_statsA | Get an overview of the knowledge base: counts of notes and tasks by status. Returns: Dictionary with note count, task counts by status, and tag frequencies. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_review | Generate a daily review of all open tasks and recent notes. Helps with planning and prioritization. |
| summarize_topic | Search the knowledge base for a topic and create a summary. Args: topic: The topic to search for and summarize. |
| weekly_planning | Plan the upcoming week based on current tasks, priorities, and notes. |
| capture_learning | Guided template for capturing what you learned about a subject. Args: subject: What you learned about. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_all_notes | Overview of all notes in the knowledge base. |
| resource_all_tasks | Overview of all tasks grouped by status. |
| resource_stats | Quick stats about the knowledge base. |
TDQS
Scored across 11 tools
Every tool targets a distinct resource and action: notes vs. tasks, with separate CRUD and list/search operations. get_stats provides an overview, and there is no ambiguity between note and task operations.
All tool names follow a consistent verb_noun snake_case pattern (add_note, list_tasks, delete_note, etc.). The naming is uniform and predictable across the entire set.
11 tools is well-scoped for a knowledge base managing notes and tasks. Each tool covers a distinct operation, and there are no redundant or unnecessary tools.
Notes have full CRUD plus search. Tasks have add, list, update, and delete, but lack a dedicated get_task by ID (though list_tasks can filter). This is a minor gap that agents can work around.