Runframe MCP Server

Runframe is the complete incident lifecycle platform for engineering teams, covering incident response, on-call, and status pages. This MCP server lets you manage those workflows from your IDE or AI agent. Its 17 documented tools cover runframe, incident, postmortem. It runs locally over stdio via the published package.

People connecting communication tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-04-26 · ★ 4 · #73 OF 99 MAINTAINED COMMUNICATION · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Runframe MCP Server

before you install - you'll need

Set RUNFRAME_API_KEY, MCP_ACCESS_TOKEN before connecting.

Claude Code

claude mcp add runframe-runframe-mcp-server -- npx -y @runframe/mcp-server

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "runframe-runframe-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@runframe/mcp-server"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @runframe/mcp-server - published under the repo owner's npm scope (@runframe)

registry namespace io.github.runframe is GitHub-verified and matches the repo owner

03 · What Runframe MCP Server can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can list incidents with filters and pagination, get incident by ID or number, create an incident, and update title, description, severity, or assignment.

The 17 tools it gives your agent

Extracted from the project's README - what runframe-mcp-server lets an agent do.

runframe_list_incidents
- List incidents with filters and pagination
runframe_get_incident
- Get incident by ID or number
runframe_create_incident
- Create an incident
runframe_update_incident
- Update title, description, severity, or assignment
runframe_change_incident_status
- Move to a new status (new, investigating, fixing, monitoring, resolved, closed)
runframe_acknowledge_incident
- Acknowledge (auto-assigns, tracks SLA)
runframe_add_incident_event
- Add a timeline entry
runframe_escalate_incident
- Escalate to the next policy level
runframe_page_someone
- Page a responder via Slack or email
runframe_get_current_oncall
- Who is on call right now
runframe_list_services
- List services
runframe_get_service
- Get service details
show all 17 tools
runframe_create_postmortem
- Create a postmortem
runframe_get_postmortem
- Get postmortem for an incident
runframe_list_teams
- List teams
runframe_get_escalation_policy
- Get escalation policy for a severity level
runframe_find_user
- Search users by name or email, with optional inactive-user support for historical lookups

Limitations (from the README)

- Read-only for schedules - you can query on-call and escalation policies but not modify them via MCP - Requires a Runframe account and API key

Latest releases

v0.1.15 · 2026-04-26

Updated the MCP server to match Runframe’s new public service key format. · Changes: · Replaced SER-00001 examples with opaque svc_... service keys. · Added service key validation for MCP tools.…

v0.1.14 · 2026-04-20

Runframe MCP server v0.1.14. · Highlights: · align MCP with the finalized V1 incident contract · use incident numbers in incident path parameters · switch incident event payloads to comment · switch incident paging to…

v0.1.13 · 2026-04-20

Runframe MCP server v0.1.13. · Highlights: · align MCP with the latest V1 API contract changes · switch on-call filtering to team_name · update postmortem action items to owner_email · read organization_name from auth…

04 · Who maintains Runframe MCP Server

runframe-mcp-server is maintained by runframe. It's the only MCP server we track from this author; the repo dates to Mar 2026.

05 · Facts

category
communication - ranked #73 of 99 actively-maintained communication servers as of 2026-08-25.
registry
io.github.runframe/runframe-mcp-server (active, first published 2026-04-05)
packages
npm:@runframe/mcp-server

06 · Runframe MCP Server FAQ

Is Runframe MCP Server still maintained?

Yes - as of 2026-08-25, its last commit was 2026-04-26. We re-verify nightly.

What can Runframe MCP Server do?

With this server connected, an agent can list incidents with filters and pagination, get incident by ID or number, create an incident, and update title, description, severity, or assignment.

How do I install Runframe MCP Server?

Run `npx -y @runframe/mcp-server`. The README documents 2 environment variables (RUNFRAME_API_KEY, MCP_ACCESS_TOKEN) to set first. Set RUNFRAME_API_KEY, MCP_ACCESS_TOKEN before connecting. You can also paste the ready-made client config above.

Does Runframe MCP Server run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Runframe MCP Server