Runframe MCP server
io.github.runframe/runframe-mcp-server·v0.1.5·4 starsMCP server for Runframe incident management covering incidents, on-call, postmortems, and more.
4 stars
Reviews
Write oneNobody has reviewed Runframe yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Runframe tools (16, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
runframe_acknowledge_incidentAcknowledge an incident. This is a distinct action from status change: it auto-assigns the incident to you, stamps the acknowledgement time, and resolves the acknowledge SLA. Idempotent — safe to call multiple times.
runframe_add_incident_eventAdd a timeline entry to an incident (log what happened).
runframe_change_incident_statusTransition an incident to a new status. Valid statuses: new, investigating, fixing, monitoring, resolved, closed. Validates allowed transitions. For acknowledging (which also auto-assigns and tracks SLA), use runframe_acknowledge_incident instead.
runframe_create_incidentwrite actionCreate a new incident from an alert or detection. Assignment happens automatically based on on-call schedules.
runframe_create_postmortemwrite actionCreate a post-mortem for a resolved incident. Required fields depend on your org's configured level.
runframe_escalate_incidentEscalate an incident to the next level in the escalation policy. Sends real notifications.
runframe_get_current_oncallGet who is currently on call. Returns on-call engineers grouped by schedule, with their roles (primary, secondary, backup) and covered services.
runframe_get_escalation_policyGet the escalation policy for a severity level (SEV0-SEV4).
runframe_get_incidentGet full incident details including timeline, participants, and affected services.
runframe_get_postmortemGet the postmortem for a resolved incident.
runframe_get_serviceGet details of a specific service.
runframe_list_incidentsList incidents filtered by status, severity, or team. Returns paginated results.
runframe_list_servicesList all services in your organization.
runframe_list_teamsList all teams in your organization.
runframe_page_someonePage a specific person about an incident. Sends a real notification via the chosen channel. Urgency is automatically derived from incident severity. To notify via both Slack and email, call this tool twice with each channel.
runframe_update_incidentwrite actionUpdate incident fields: title, description, severity, or assignment. For status changes use runframe_change_incident_status instead.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 154 days ago8/15
- Maintainer identityregistry namespace matches repository owner7/10
How Runframe compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 36% of 48,255 servers
- Tools
- 16
- the typical server has 7
- Tools that change things
- 19%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 4
- more than 82% of 28,688 servers
What its tools let an agent do: 16 run or deploy
Install Runframe in Claude Code, Cursor or VS Code
Runs npx -y @runframe/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add runframe-mcp-server -- npx -y @runframe/mcp-server
What the publisher says
From the Runframe repository's README, as published. We do not edit it. Read it on GitHub
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.
17 tools covering incidents, on-call, services, postmortems, teams, and people lookup. Requires Node.js 20+.
Why Use This
- Stay in your editor — acknowledge incidents, page responders, and write postmortems without switching to a browser
- Let agents handle the routine — AI agents can triage, escalate, and update incidents autonomously using scoped API keys
- Zero infrastructure — runs via npx, no server to deploy for local use
How It Works
Your IDE / Agent
↓ (stdio or HTTP)
MCP Server (this package)
↓ (HTTPS, scoped API key)
Runframe APIThe server is stateless. It translates MCP tool calls into Runframe API requests, scoped by your API key permissions. No data is stored locally.
Examples
Ask your agent:
- "Acknowledge incident INC-2026-001" → calls runframeacknowledgeincident
- "Who is on call right now?" → calls runframegetcurrent_oncall
- "Create a postmortem for the database outage" → calls runframecreatepostmortem
- "Page the backend team lead about the API latency spike" → calls runframepagesomeone
- "List all open SEV1 incidents" → calls runframelistincidents with severity filter
- "Find Alex so I can check their open incidents" → calls runframefinduser
Install
Get your API key from settings inside Runframe.io, then add to your agent:
Claude Code:
claude mcp add runframe -e RUNFRAME_API_KEY=rf_your_key_here -- npx -y @runframe/mcp-serverCursor (~/.cursor/mcp.json) · VS Code (.vscode/mcp.json) · Claude Desktop (claudedesktopconfig.json):
{
"mcpServers": {
"runframe": {
"command": "npx",
"args": ["-y", "@runframe/mcp-server"],
"env": { "RUNFRAME_API_KEY": "rf_your_key_here" }
}
}
}Other MCP clients: Add the JSON config above to your client's MCP config file.
Interactive setup wizard:
npx @runframe/mcp-server --setupEnvironment Variables
Transports
stdio (default) — used by MCP clients like Claude Code and Cursor. No network exposure. This is what the install commands above configure.
Streamable HTTP — for containerized or remote deployments. Requires MCPACCESSTOKEN for bearer auth:
RUNFRAME_API_KEY=rf_... \
MCP_ACCESS_TOKEN=your_token \
npx @runframe/mcp-server --transport http --port 3100 --host 127.0.0.1Security Model
Responsibility is split across three boundaries:
- Runframe API handles authorization and scopes via RUNFRAMEAPIKEY.
- This MCP server handles process isolation (stdio) and bearer-token validation (HTTP). It also enforces method filtering, Host/Origin checks on localhost, declared Content-Length validation (1 MB limit), 8 KB header limit, and 15s upstream timeout.
- Your reverse proxy handles TLS, rate limiting, and streamed-body enforcement if you expose HTTP mode to a network.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Runframe: common questions
- Is Runframe MCP server safe?
- Mostly: it is graded B (71/100). Read the Runframe safety report
- How do I install Runframe?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Runframe need an API key?
- Yes. The registry entry asks for
RUNFRAME_API_KEY. - Is Runframe maintained?
- The last commit was 192 days ago (2026-04-26). The latest release is v0.1.5.
- What can I use instead of Runframe?
- Servers from other publishers that do the same job: OneUptime MCP server.
- How does Runframe compare with other MCP servers?
- safety score 71/100 (higher than 36% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 19% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Runframe
Same job from other publishers: the closest match first, then the best rated.
OneUptimeManage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.not reviewedEstablishedA