knowledge-base
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KB_ROOT | No | Path to the knowledge base checkout. Defaults to the directory of the server script. | |
| KB_GIT_AUTHOR_NAME | No | Override the git author name used for commits. Defaults to 'Knowledge base'. | |
| KB_GIT_AUTHOR_EMAIL | No | Override the git author email used for commits. Defaults to 'knowledge-base@localhost'. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kb_searchA | Ranked full-text search over every page in the knowledge base. Returns page paths, titles and matching lines with line numbers to cite or open with kb_read. |
| kb_readA | Read a knowledge base page, whole or a line range. Paths are relative to content/ or start with content/. |
| kb_listA | List knowledge base pages with their titles, optionally only those under one folder. |
| kb_amendA | Create or change one markdown page under content/, then commit it and push it to the tracked branch so it is published. Pass either content (the whole new page) or edit ({ find, replace }, where find must match exactly once). The message becomes the commit title. Pages are never deleted. |
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 4 tools
Each tool covers a distinct operation: search, amend (create/edit), read, and list. No two tools could be confused, with search returning matches and read retrieving page content.
All four tools share the kb_ prefix and use a consistent verb_noun pattern: kb_search, kb_amend, kb_read, kb_list. The naming is uniform and predictable.
Four tools is well-scoped for a knowledge base server, covering the core needs without unnecessary bloat. Each tool earns its place.
The surface provides list, read, search, and amend (covering create and edit). Deletion is explicitly not supported, which is an intentional policy rather than a gap. The domain is fully covered.