Open MCP Server

MCP server that wraps the Open Notebook API

Local serverstdioPython

What is the Open MCP server?

Most developer tooling work still happens through a UI a human drives. Open MCP server moves it into the conversation instead. MCP server that wraps the Open Notebook API.

The short version

An MCP (Model Context Protocol) server that provides tools to interact with the Open Notebook API. This server enables AI assistants like Claude to manage notebooks, sources, notes, search content, and interact with AI models through Open Notebook.

  • Notebooks Management — Create, read, update, and delete notebooks
  • Sources Management — Add and manage content sources (links, uploads, text)
  • Notes Management — Create and organize notes within notebooks
  • Search & AI — Search content using vector/text search and ask questions
  • Models Management — Configure and manage AI models
  • Chat Sessions — Create and manage chat conversations

Getting it running

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • search_capabilities — Progressive tool discovery
  • Testing — 1. Browse available tools 2. Test tool calls 3. Inspect responses 4. Debug errors

What it needs from you

Configuration is passed through the environment: OPEN_NOTEBOOK_URL, OPEN_NOTEBOOK_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Python 3.12+ - Open Notebook instance (local or remote) - Dependencies: mcp[cli]>=1.23.2, httpx>=0.28.1

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Open's toolset — search_capabilities, Testing — is a fair guide to whether it matches your workflow. It is maintained by Epochal-dev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
search_capabilitiesProgressive tool discovery
Testing1. Browse available tools 2. Test tool calls 3. Inspect responses 4. Debug errors

How to install the Open MCP server

{
  "mcpServers": {
    "open-notebook": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "OPEN_NOTEBOOK_URL": "your-value",
        "OPEN_NOTEBOOK_PASSWORD": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Python 3.12+ - Open Notebook instance (local or remote) - Dependencies: mcp[cli]>=1.23.2, httpx>=0.28.1
VariableDescriptionRequired
OPEN_NOTEBOOK_URLEndpoint or connection string the server talks to.Yes
OPEN_NOTEBOOK_PASSWORDConfiguration value read at startup.Optional

Example prompts to try

  • Use Open to search capabilities.
  • Use Open to Testing.

Frequently asked questions

It connects Open to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (search_capabilities, Testing) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Open directly.