Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DBNoPath to the SQLite database file, provided via the --db flag (e.g. kb-mcp --db ~/.kb-mcp/kb.db).
HTTPNoEnable the Streamable HTTP transport with the --http flag (e.g. kb-mcp --http --port 8765).
PORTNoPort for the Streamable HTTP transport, provided via the --port flag (e.g. kb-mcp --http --port 8765).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

A personal knowledge base of notes and bookmarks.

  • Use search_notes before answering questions about things the user saved; cite note ids.

  • Use add_note / save_bookmark only when the user asks to save something.

  • delete_note is permanent: confirm with the user first.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_notesB

Full-text search over notes and bookmarks, best matches first.

get_noteA

Fetch one note or bookmark in full.

list_notesA

List notes, most recently updated first. Paginate with offset / next_offset.

list_tagsB

All tags in use, with how many notes carry each.

add_noteC

Save a new note.

save_bookmarkB

Save a link with a title and optional notes.

update_noteA

Change a note's title, body or tags. Fields left out stay as they are.

delete_noteB

Permanently delete a note or bookmark. Confirm with the user first.

Prompts

Interactive templates invoked by user choice

NameDescription
summarize_tagSummarise everything saved under one tag.
find_relatedAsk the model to find notes connected to one note, using search_notes.

Resources

Contextual data attached and managed by the client

NameDescription
tagsEvery tag with its note count.
statsCounts of notes, bookmarks and tags.

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have clearly distinct purposes (list/search/get/add/update/delete), and the descriptions distinguish search_notes from list_notes well. The main ambiguity is the note/bookmark boundary: get_note and delete_note operate on 'note or bookmark', but creation splits into add_note vs save_bookmark, and it's unclear whether update_note applies to bookmarks.

Naming Consistency4/5

Names follow a predictable verb_noun snake_case pattern (list_tags, search_notes, get_note, update_note, delete_note). The only deviation is the create pair using different verbs, add_note vs save_bookmark, which adds mild inconsistency to an otherwise uniform set.

Tool Count5/5

Eight tools is well-scoped for a knowledge-base server: list/search/read, two create paths, update, delete, and tag listing. Each tool earns its place and no tool looks like filler.

Completeness4/5

Note lifecycle is fully covered (create, read, list, search, update, delete) and tags can be set via update_note and enumerated via list_tags. The gap is bookmarks: there is no way to update a bookmark's URL/title/tags, and update_note is described only for notes, leaving bookmark maintenance a dead end.