Open Notebook
Connect Claude Code or Cursor to your Open Notebook instance so agents can search and update project notes without leaving the editor.
Overview
Open Notebook MCP is a MCP server for the Build phase that wraps your Open Notebook API so agents can read and write project notebooks over stdio.
What is this MCP server?
- Stdio MCP server (open-notebook-mcp on PyPI) wrapping the full Open Notebook HTTP API
- Requires OPEN_NOTEBOOK_URL plus optional OPEN_NOTEBOOK_PASSWORD when APP_PASSWORD is enabled
- Version 0.3.0 in server metadata with GitHub source at Epochal-dev/open-notebook-mcp
- Keeps notebook knowledge beside agent sessions instead of duplicating context in every prompt
- Server manifest version 0.3.0
- One primary PyPI package identifier: open-notebook-mcp
- Two documented environment variables (URL required, password optional secret)
Community signal: 30 GitHub stars.
What problem does it solve?
Agents lose long-lived research and specs when context lives only in chat threads instead of a notebook your stack can query.
Who is it for?
Indie builders self-hosting Open Notebook who want agent-native note sync during implementation and iteration.
Skip if: Teams without an Open Notebook instance or anyone who only needs ephemeral in-chat summaries with no persistent API backend.
What do I get? / Deliverables
After install, your agent can maintain a shared Open Notebook corpus tied to OPEN_NOTEBOOK_URL while you keep building and shipping.
- Agent-callable access to Open Notebook API operations via MCP
- Persistent notebook updates driven from agent sessions
- Authenticated connection when OPEN_NOTEBOOK_PASSWORD is configured
Recommended MCP Servers
Journey fit
Open Notebook is primarily where builders attach structured notes and project context to the product they are building, which maps to documentation and living specs during Build. The MCP layer exposes your self-hosted Open Notebook API so agents can read and write notebooks alongside code—canonical shelf is build/docs rather than a one-off integration hook.
How it compares
MCP integration to a notebook API, not a built-in Claude skill or hosted note SaaS.
Common Questions / FAQ
Who is io.github.Epochal-dev/open-notebook for?
It is for solo builders and small teams running Open Notebook who want Claude Code, Cursor, or similar agents to call the notebook API through MCP.
When should I use io.github.Epochal-dev/open-notebook?
Use it when project notes, specs, or research should live in Open Notebook and be updated or searched by your agent during build and follow-up work.
How do I add io.github.Epochal-dev/open-notebook to my agent?
Install the PyPI package open-notebook-mcp, set OPEN_NOTEBOOK_URL (and OPEN_NOTEBOOK_PASSWORD if required), and register the stdio MCP server in your agent’s MCP config.