Runbook Model Context Protocol Server
Connect Runbook to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Runbook Model Context Protocol Server. The runbook mcp server is what makes that connection.
This MCP server integrates with Runbook to allow listing, reading, and searching over documents.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Tools — The Tools tool exposed by this serverConfiguration is passed through the environment: RUNBOOK_BASE_URL, RUNBOOK_API_TOKEN. 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.
The server ships on npm as @runbook-docs/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
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. Runbook's toolset — Tools — is a fair guide to whether it matches your workflow. It is maintained by qloba; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"runbook": {
"command": "npx",
"args": [
"-y",
"@runbook-docs/mcp-server"
],
"env": {
"RUNBOOK_BASE_URL": "https://<YOUR_SUBDOMAIN>.runbook.jp",
"RUNBOOK_API_TOKEN": "your-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| RUNBOOK_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| RUNBOOK_API_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.