Cursor
Cursor’s agent can run terminal commands and call MCP tools. Either works; the CLI keeps tokens out of the model’s context.
With the CLI and the skill
Section titled “With the CLI and the skill”-
Install the CLI and sign in:
Terminal window curl -fsSL https://github.com/angler-ai/the-runbook-app/releases/latest/download/install.sh | shrunbook login https://runbooks.example.comInstalling the CLI has the other ways, such as building from source.
-
Install the skill:
Terminal window runbook skill install --agent cursor --therunbook --scope projectThat writes
.cursor/skills/therunbook/in this repository. Without--scope projectit goes to~/.cursor/skills/. -
Give the agent its own credential:
Terminal window runbook token create --agent --name cursor --expires-in 30d \--scope runbooks:read --scope executions:read --scope executions:act --jsonExport the secret as
RUNBOOK_TOKENin the terminal Cursor’s agent uses. -
Ask the agent, in agent mode:
Work the next agent step of run exe_01JD2X6PZ5R8E2W4Y6A0C3D5F7.
Over MCP
Section titled “Over MCP”{ "mcpServers": { "runbook": { "command": "runbook", "args": ["mcp", "serve"] } }}{ "mcpServers": { "runbook": { "url": "https://runbooks.example.com/mcp" } }}Cursor shows the server as needing sign-in; connect it from Cursor’s MCP settings, sign in with an email code and tick the scopes it may use.
{ "mcpServers": { "runbook": { "url": "https://runbooks.example.com/mcp", "headers": { "Authorization": "Bearer ${env:RUNBOOK_TOKEN}" } } }}Put the file in ~/.cursor/mcp.json instead to make the server available in
every project.
Writing runbooks in Cursor
Section titled “Writing runbooks in Cursor”With the MCP server connected, Cursor’s agent can draft a runbook, validate
it and save it as a draft (validate_runbook, save_runbook_draft). A
person with runbooks:publish publishes it. See draft a runbook from an
incident doc.