knowledge-library-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_LIBRARY_ROOT | No | The root directory of the knowledge library. If not set, the server defaults to the parent directory of the mcp-server/ directory. | parent directory of the mcp-server/ directory |
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 |
|---|---|
| list_areasB | The six canonical areas of the knowledge library. |
| search_notesB | Full-text search across the library. Optional |
| get_noteA | Return the markdown content of a note by relative path. |
| list_permanent_notesA | List all permanent notes within one area. |
| get_guidanceA | Return the markdown of |
| list_projectsA | List active projects (directories under |
| create_noteA | Create a new note. Returns relative path. Refuses to overwrite. kind: fleeting | literature | permanent | guidance | project area_or_path: required area name for permanent/guidance; optional sub-path for others. |
| update_noteA | Overwrite an existing note. Refuses if path doesn't already exist. |
| append_fleetingB | Append a timestamped block to today's |
| list_pending_changesA | Return uncommitted changes in the knowledge-library (parsed git status). |
| save_changesA | Stage all changes, commit, push origin main. ONLY call this tool when the user has explicitly approved the change ("save it", "commit that", "looks good, push it"). Drafts iterated in chat without explicit approval should remain uncommitted on disk. |
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
Each tool maps to a distinct resource and action: areas, note content, searches, projects, and git operations are cleanly separated. Even the retrieval tools differ clearly by path-based access, guidance-specific lookup, and area-scoped listing.
All tools follow a consistent snake_case verb_noun pattern: list_* for collections, get_* for single items, create/update/append for mutations, and save/list for git workflow. The naming makes the tool set predictable and easy to navigate.
11 tools is well-scoped for a knowledge library covering capture, search, retrieval, editing, project listing, and git persistence. Each tool serves a clear purpose without redundancy or bloat.
The surface covers create, read, update, search, capture, project listing, and git commit/push workflows. Missing delete/archive and a general list-all-notes operation are workable gaps, but they may be intentional for a permanent knowledge base.