Knowledge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_CONFIG | No | Optional. Path to the config file. Knowledge also reads ~/.config/knowledge/config.toml by default. | |
| KNOWLEDGE_APPROVAL_LOG | No | Optional. Where the approval log is written. Default: ~/.local/state/knowledge/approvals.jsonl. | |
| KNOWLEDGE_<MODULE>_ENABLED | No | false turns a module off, e.g. KNOWLEDGE_OPEN_NOTEBOOK_ENABLED=false. | |
| KNOWLEDGE_OPEN_NOTEBOOK_URL | No | Address of your Open Notebook server, e.g. https://notebook.example.com. No path. | |
| KNOWLEDGE_OPEN_NOTEBOOK_PASSWORD | No | Only if your Open Notebook server has a password (OPEN_NOTEBOOK_PASSWORD on the server). Leave it unset otherwise. | |
| KNOWLEDGE_OPEN_NOTEBOOK_REQUIRE_CONFIRM | No | true by default: you approve each new note and link. false lets the assistant save them on its own. Local files always need your approval. | true |
| KNOWLEDGE_OPEN_NOTEBOOK_ALLOWED_NOTEBOOKS | No | Optional. Comma-separated notebook names the assistant may save links and notes to without asking, e.g. Research,Inbox. |
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 |
|---|---|
| open_notebook_notebooksA | List your notebooks, most recently updated first. Page with offset=<next_offset>. |
| open_notebook_searchA | Search sources and notes. mode 'text' matches keywords; 'vector' matches meaning and needs an embedding model set up on the server. Limit a search to one notebook with notebook_id. Page with offset=<next_offset>. |
| open_notebook_notesA | List the notes in one notebook, titles only. Read a note with open_notebook_note_get. Page with offset=<next_offset>. |
| open_notebook_note_getA | Read one note. Long content is cut at max_chars (up to 50000) and marked truncated. |
| open_notebook_source_getA | Read one source: its title, topics, extracted text (cut at max_chars, up to 50000) and the notebooks it belongs to. |
| open_notebook_note_createA | Create a note in a notebook. Without confirm=true it only returns a preview. With confirm=true you are asked to approve it (unless the notebook is pre-approved in settings); the assistant cannot approve on your behalf. Text that looks like a credential is refused. |
| open_notebook_add_sourceA | Add a web link or a local file as a source in one notebook. Give exactly one of url or file_path. Without confirm=true it only returns a preview. With confirm=true you are asked to approve it; the assistant cannot approve for you. A local file is always approved by you, with its full path and size shown, and is never pre-approved in settings. Open Notebook processes the source in the background: check progress with open_notebook_source_get. |
| knowledge_modulesA | Which modules are on, what settings are missing, and what each tool does. Pass a module name for its full settings list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| decision-record | Create a lightweight Architecture Decision Record (ADR) as a numbered Markdown file in a Decisions folder, with context, decision, consequences and alternatives. Use when the user wants to record a technical or product decision, write an ADR, document why something was chosen, or log a choice for later review. |
| getting-started | Set up and check the Knowledge MCP bundle (Open Notebook search, reading and writing). Use when the user installs Knowledge, asks what Knowledge can do, gets a "not_configured", "auth_failed" or "unreachable" error from a knowledge tool, or wants to turn the Open Notebook module on or off. |
| icm-architect | Design a process, idea or body of knowledge into an ICM (Interpretable Context Methodology) workspace, where folder structure is the agent architecture, or restructure an existing folder, repo or vault into one. Use for "make this an ICM", "ICM this", "build me a workspace", "structure this for agents", "map this repo", "audit this folder", "what would a change hit", a second brain, team brain or context map, or turning transcripts and research into material for lectures, scripts or docs. |
| meeting-notes | Create structured meeting notes as a Markdown file with attendees, decisions, action items and follow-up, and optionally save them to an Open Notebook notebook. Use when the user asks to write up a meeting, make meeting notes, record decisions and action items from a call, or turn a transcript into notes. |
| obsidian-markdown | Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes. |
| research-with-sources | Answer a question from the user's own Open Notebook sources and notes, citing each claim to a source, and flag where two sources contradict each other. Use when the user asks what their notes say about a topic, wants an answer backed by their saved material, or asks to compare what sources say. |
| weekly-review | Write a weekly review of what changed in an Open Notebook knowledge base, with done, open and next-week items linked to the notes that show them. Use when the user asks for a weekly review, what they worked on this week, a status summary from their notes, or a standup built from their notebooks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| decision-record/SKILL.md | |
| getting-started/SKILL.md | |
| icm-architect/SKILL.md | |
| icm-architect/assets/templates/CONTEXT.md | |
| icm-architect/assets/templates/bundle-schema.md | |
| icm-architect/assets/templates/claim.md | |
| icm-architect/assets/templates/concept.md | |
| icm-architect/assets/templates/context-map-node.md | |
| icm-architect/assets/templates/context-map-schema.md | |
| icm-architect/assets/templates/entry.md | |
| icm-architect/assets/templates/keep-out.txt | |
| icm-architect/assets/templates/object.md | |
| icm-architect/assets/templates/plan.md | |
| icm-architect/assets/templates/process.md | |
| icm-architect/assets/templates/questionnaire.md | |
| icm-architect/assets/templates/source.md | |
| icm-architect/assets/templates/stage-CONTEXT.md | |
| icm-architect/references/bundle-from-sources.md | |
| icm-architect/references/core.md | |
| icm-architect/references/forms.md | |
| icm-architect/references/system-map.md | |
| icm-architect/scripts/index.py | |
| icm-architect/scripts/links.py | |
| icm-architect/scripts/quotes.py | |
| icm-architect/scripts/viz.py | |
| meeting-notes/SKILL.md | |
| obsidian-markdown/SKILL.md | |
| obsidian-markdown/references/CALLOUTS.md | |
| obsidian-markdown/references/EMBEDS.md | |
| obsidian-markdown/references/PROPERTIES.md | |
| research-with-sources/SKILL.md | |
| weekly-review/SKILL.md |
TDQS
Scored across 8 tools
Each tool maps to a distinct resource+action pair, and the suffix conventions (notes = list, note_get = read) plus explicit descriptions keep the list/read pairs separable. Minor overlap between open_notebook_search scoped to a notebook and open_notebook_notes listing within a notebook, but the descriptions clarify the boundary.
Seven of eight tools share the open_notebook_ prefix and snake_case, which is good. However, verb placement is mixed: noun_verb (open_notebook_note_get, open_notebook_source_get), verb_noun (open_notebook_add_source), and bare nouns (open_notebook_notebooks, open_notebook_notes), and the final tool (knowledge_modules) breaks the prefix entirely.
Eight tools is well within a comfortable range for a notebook/source/note management server. Each tool serves a distinct role: browsing, reading, searching, creating, and one meta/introspection tool.
Read paths and creation are covered (list notebooks, list/read notes, read sources, search, create note, add source), but there is no way to list sources belonging to a notebook and no update or delete operations for notes, sources, or notebooks. The surface supports ingestion and reading but leaves lifecycle management and source browsing as notable gaps.