kb-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KB_DB_PATH | No | Path to the SQLite database file. Defaults to ./data/kb.sqlite3. | ./data/kb.sqlite3 |
| KB_HTTP_HOST | No | Host for the HTTP server. Defaults to 127.0.0.1. | 127.0.0.1 |
| KB_HTTP_PORT | No | Port for the HTTP server. Defaults to 8000. | 8000 |
| KB_TRANSPORT | No | Transport to use. Set to 'http' for Streamable HTTP transport. Defaults to stdio. | |
| KB_AUTH_TOKEN | No | Bearer token for authenticating HTTP transport. Required when KB_TRANSPORT is 'http'. |
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 |
|---|---|
| create_noteC | Create a new note with a title and body, and return the saved note. |
| get_noteB | Retrieve a single note by its id. |
| update_noteC | Replace an existing note's title and body. |
| delete_noteC | Delete a note by its id. |
| search_notesA | Full-text search over note titles and bodies, ranked by relevance. Supports FTS5 syntax: quote a phrase for an exact match, combine terms with AND/OR/NOT, or prefix-match with an asterisk (e.g. kaf*). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_note | Summarize a note's content in a few sentences. |
| draft_reply | Draft a reply to a note in a given tone. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action on a single note resource: create, retrieve, update, delete, and search. There is no overlap or ambiguity; an agent can easily select the correct tool.
All tool names follow a consistent verb_noun pattern in snake_case: create_note, get_note, update_note, delete_note, search_notes. The convention is predictable and readable.
With 5 tools, the set is well-scoped for a note management server. It covers essential operations without bloat, and each tool earns its place.
The server provides full CRUD plus full-text search, covering the core lifecycle. However, it lacks an explicit 'list all notes' operation, which could be a minor gap for some workflows.