Knowledge
The server lets an AI assistant work with a self-hosted Open Notebook: inspect modules/settings, browse notebooks and notes, search sources and notes, read content, and create notes or add sources with approval.
List notebooks, including archived ones and paging.
Search sources and notes by keyword or vector similarity, optionally within one notebook.
List notes in a notebook and read individual notes with truncation limits.
Read source details, extracted text, topics, notebooks, and processing/embedding status.
Preview and create notes in a notebook after user approval, unless pre-approved.
Preview and add a web link or local file as a source after approval; local files are never pre-approved.
Inspect enabled modules, missing settings, available skills, version, publisher, and config file.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Knowledge search my notebooks for notes from the Q3 planning meeting"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Knowledge
Made by Seaynic Labs. Need tools like this built around your own systems? We do that.
Knowledge lets an AI assistant search, read and write the notes in your self-hosted Open Notebook, and comes with skills that teach it to do that work well: meeting notes, decision records, weekly reviews and source-backed research.
It is a bundle: tools, skills and instructions in one install. The tools are one server made of modules. You switch on the modules you use. New modules arrive switched off, so an update never changes what your assistant can do until you choose to.
Security card | |
Network | Only the Open Notebook server you configure (KNOWLEDGE_OPEN_NOTEBOOK_URL). Open Notebook fetches the links you add, not Knowledge. Nothing else, no telemetry. |
Files | Reads its config file ( |
Secrets | API keys and passwords come from your environment or config file. They are never tool arguments and never returned to the model. |
Read-only tools | 6: |
Needs your approval |
|
Startup cost | about 4,600 tokens (8 tools, 7 skill prompts) |
Changes | Tool descriptions are locked by hash ( |
Skills
Skill | What it does | Source |
| Checks the settings, runs the first calls, explains approvals and errors | Seaynic Labs (MIT) |
| Answers from your notebooks, cites each claim, flags sources that disagree | Seaynic Labs (MIT) |
| Done, open and next-week items from the notes you changed this week | Seaynic Labs (MIT) |
| Structured meeting notes as a Markdown file, optionally saved to a notebook | Seaynic Labs (MIT) |
| A numbered Architecture Decision Record in a | Seaynic Labs (MIT) |
| Organises a knowledge base as a folder structure that agents can walk | Jake Van Clief (MIT), credits |
| Obsidian-flavoured Markdown: wikilinks, callouts, properties | Steph Ango (MIT), credits |
Skills reach every app. Claude Code and other skill-aware apps read the skills/ folder. Any MCP app gets the same text as prompts: getting-started, for example, is the prompt named getting-started. Third-party skills keep their own license files. See CREDITS.md.
Related MCP server: Obsidian MCP Server
Install
Knowledge needs Python 3.11 or newer. With uv you don't install anything ahead of time:
uvx knowledge-bundle-mcp --versionOr with pip:
pip install knowledge-bundle-mcpPinned install. For a fixed setup, pin the exact version. The plugin manifest pins it the same way:
uvx knowledge-bundle-mcp==0.2.1 --versionAs a Claude Code plugin. One install gives you the MCP server and the skills. This needs the seayniclabs/plugins marketplace, which is published with the release:
/plugin marketplace add seayniclabs/plugins
/plugin install knowledge@seayniclabsThe plugin still needs your Open Notebook address in its settings. The plugin file is .claude-plugin/plugin.json.
First five minutes
Set
KNOWLEDGE_OPEN_NOTEBOOK_URLto your server's address (step 2 below shows where).Run the check. It prints
okorFIXfor each item and exits 0 when everything is ready:knowledge-bundle-mcp --doctorStart your assistant and ask it to list your notebooks. It calls
open_notebook_notebooksand shows you the names.Ask it to search a word you know is in one of your notes. It calls
open_notebook_search.Ask it to save a note. It shows a preview first, then asks you to approve the save in your app.
Settings
Set these as environment variables in your MCP client's config, or put them in a config file (see below). Knowledge starts without any of them and tells you what's missing when you call a tool.
Variable | Module | What it is |
| open_notebook | Address of your Open Notebook server, e.g. |
| open_notebook | Only if your server has a password ( |
| open_notebook |
|
| open_notebook | Optional. Comma-separated notebook names the assistant may save links and notes to without asking, e.g. |
| any | Optional. Where the approval log is written. Default: |
| any |
|
Config file (optional). Knowledge also reads ~/.config/knowledge/config.toml, or the file named by KNOWLEDGE_CONFIG. Environment variables win over the file.
[open_notebook]
url = "https://notebook.example.com"
password = "change-me"
require_confirm = trueAdd it to your MCP client
Most clients use the same JSON shape. Put it where your client keeps MCP servers:
{
"mcpServers": {
"knowledge": {
"command": "uvx",
"args": ["knowledge-bundle-mcp"],
"env": {
"KNOWLEDGE_OPEN_NOTEBOOK_URL": "https://notebook.example.com"
}
}
}
}Client | Where the config goes |
Claude Desktop |
|
Claude Code |
|
Cursor |
|
VS Code |
|
Sonique, Hermes, OpenClaw, others | Any client that launches a stdio MCP server: command |
Over HTTP. For clients that connect to a URL instead of launching a process:
knowledge-bundle-mcp --transport http --port 8765It serves streamable HTTP at http://127.0.0.1:8765/mcp. It listens only on your own machine by default. Put authentication in front of it before exposing it anywhere else.
Try these
Paste any of these into your assistant once Knowledge passes --doctor:
"List my notebooks and tell me which one changed most recently."
"Search my notebooks for what I wrote about the Q3 budget, and cite each note."
"Write a weekly review of the notes I changed this week, using the weekly-review skill."
"Make an ADR for choosing SQLite over Postgres for the prototype, with the alternatives table filled in."
"Save this link to my Research notebook: https://example.com/article. Show me the preview first."
Tools
Tool | What it returns |
| Which modules are on, which settings are missing, the skills, and the publisher. Call this first. |
| Your notebooks, most recently updated first, paged |
| Matching sources and notes. |
| The notes in one notebook, titles only, paged |
| One note's content, cut at |
| One source: title, topics, extracted text, notebooks, processing status |
| Saves a note after you approve it. Without |
| Adds a web link, or a local file you name, as a source. Preview first; you approve it. Processed in the background. |
Every tool returns structured data with a published schema, so an assistant can work with the results instead of parsing text. Errors always look like knowledge.<module>.<code>: <message> Fix: <hint>.
Safety
Knowledge only calls the Open Notebook server you configure. It sends nothing anywhere else and keeps no data of its own.
open_notebook_note_createandopen_notebook_add_sourcechange your notebooks, so you approve each one. When the assistant asks to save, Knowledge asks you directly through your MCP client (MCP elicitation) and shows the notebook, the title and the full text or link. The assistant can't answer that question for you.A local file is read only after you name it, and it is uploaded only after you approve its full path and size. Files named like credential stores (
.env,.netrc, private keys,*.pem,*.key) and files in~/.ssh,~/.awsor~/.gnupgare refused.Some MCP clients can't ask you questions yet. In those, Knowledge refuses to write unless you've pre-approved the notebook with
KNOWLEDGE_OPEN_NOTEBOOK_ALLOWED_NOTEBOOKS, or turned approval off withKNOWLEDGE_OPEN_NOTEBOOK_REQUIRE_CONFIRM=false. Local files are never pre-approved.Before anything is written or sent, text that looks like a credential (API keys, tokens, private keys, passwords in URLs) is refused. The error names the kind of credential found, never the value.
Use an
https://address for your server, and give the password only to Knowledge, not to other tools.
Develop
uv venv && uv pip install -e '.[dev]'
.venv/bin/pytest
python3 scripts/check_skills.py
.venv/bin/python scripts/tool_lock.py --check
.venv/bin/python scripts/security_card.py --checkscripts/tool_lock.py (without --check) rewrites tool-manifest.lock.json after a deliberate change to a tool, prompt or instruction. Add a changelog line in the same commit.
Security
Report a vulnerability privately through GitHub (Security tab, "Report a vulnerability"). See SECURITY.md. Every approval, decline and refusal is logged locally in ~/.local/state/knowledge/approvals.jsonl: titles, notebook names and sizes, never the text. Set KNOWLEDGE_APPROVAL_LOG to move it.
License
MIT. Published by Seaynic Labs. Third-party skills are credited in CREDITS.md and keep their own licenses.
Built by Seaynic Labs. We build tools like this around a business's own systems: local-first, with a person approving every change. See custom integrations.
Available Tools
8 toolsknowledge_modulesARead-only
Which modules are on, what settings are missing, and what each tool does. Pass a module name for its full settings list.
Inputs: module. Returns: skills, modules, version, homepage, +2 more
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.
Inputs: notebook_id (required), url, title, confirm, +1 more. Returns: kind, note, path, status, +8 more
open_notebook_notebooksARead-only
List your notebooks, most recently updated first. Page with offset=<next_offset>.
Inputs: limit, offset, include_archived. Returns: limit, offset, has_more, notebooks, +1 more
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.
Inputs: title (required), content (required), notebook_id (required), confirm. Returns: id, note, title, created, +6 more
open_notebook_note_getARead-only
Read one note. Long content is cut at max_chars (up to 50000) and marked truncated.
Inputs: note_id (required), max_chars. Returns: id, title, content, created, +4 more
open_notebook_notesARead-only
List the notes in one notebook, titles only. Read a note with open_notebook_note_get. Page with offset=<next_offset>.
Inputs: notebook_id (required), limit, offset. Returns: limit, notes, offset, has_more, +2 more
open_notebook_searchARead-only
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>.
Inputs: query (required), mode, limit, offset, +3 more. Returns: hits, mode, limit, query, +4 more
open_notebook_source_getARead-only
Read one source: its title, topics, extracted text (cut at max_chars, up to 50000) and the notebooks it belongs to.
Inputs: source_id (required), max_chars. Returns: id, title, status, topics, +8 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Turn your notes, links and conversations into a Living Brain your AI tools share and build on.
Personal context for every AI: search, read, and write back to your private Markdown library.
Self-hostable shared brain for you and your AI agents — docs, flows, meetings, decisions, rationale
Personal wiki and memory layer for AI assistants. Persistent, structured memory across sessions.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants like Claude and Codex to read, write, search, and traverse Markdown notes stored in a self-hosted knowledge base.-
- AlicenseBqualityDmaintenanceEnables AI assistants to search, create, and manage notes in an Obsidian vault via 40+ local tools.5214 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to read and write to a personal knowledge vault of markdown notes, projects, and tasks, with tooling for search, capture, daily logs, and project management across different AI tools.2344 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to capture, search, update, and delete notes in a local Markdown vault with automatic categorization and tagging, making knowledge management seamless.6 npm1MIT