Runframe MCP Server

If you already use Runframe, the runframe mcp server is the piece that lets your assistant work with it directly. MCP server for Runframe incident management — any agent, any IDE, one system of record.

What the server does

17 tools covering incidents, on-call, services, postmortems, teams, and people lookup. 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

Installation

@runframe/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: RUNFRAME_API_KEY, RUNFRAME_API_URL, MCP_ACCESS_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.

Where it fits

Plenty of cloud and infrastructure 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. It is maintained by runframe; 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.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.