runframe-mcp-server

[](https://github.com/runframe/runframe-mcp-server/actions/workflows/ci.yml) [](https://npmjs.com/package/@runframe/mcp-server) [](LICENSE) [](https://nodejs.org)

[Runframe](https://runframe.io) is Slack-native incident management & on-call scheduling for engineering teams. This MCP server lets you manage the full incident lifecycle from your IDE or AI agent.

16 tools covering incidents, on-call, services, postmortems, and teams. Requires Node.js 20+.

• 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

Your IDE / Agent
    ↓ (stdio or HTTP)
MCP Server (this package)
    ↓ (HTTPS, scoped API key)
Runframe API

The server is stateless. It translates MCP tool calls into Runframe API requests, scoped by your API key permissions. No data is stored locally.

Ask your agent:

• *"Acknowledge incident INC-42"* → calls runframe_acknowledge_incident
• *"Who is on call right now?"* → calls runframe_get_current_oncall
• *"Create a postmortem for the database outage"* → calls runframe_create_postmortem
• *"Page the backend team lead about the API latency spike"* → calls runframe_page_someone
• *"List all open SEV1 incidents"* → calls runframe_list_incidents with severity filter

Get your API key from Runframe Settings, then add to your agent:

Claude Code:

claude mcp add runframe -e RUNFRAME_