# runframe-mcp-server [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/runframe/runframe-mcp-server  
**GitHub Stars:** 4  
**npm Downloads (last month):** 180  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/runframe-mcp-server

## Description
MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.

## Tools
Capabilities this server exposes over MCP:

- **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
- **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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "runframe-mcp-server": {
    "command": "npx",
    "args": ["-y","@runframe/mcp-server"],
    "env": {
      "RUNFRAME_API_KEY": "",
      "RUNFRAME_API_URL": "",
      "MCP_ACCESS_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `RUNFRAME_API_KEY`, `RUNFRAME_API_URL`, `MCP_ACCESS_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What runframe-mcp-server MCP server does

runframe-mcp-server MCP server exposes Runframe’s incident-management workflows to MCP-compatible clients. It covers incident investigation and updates, on-call lookup, service records, team and escalation-policy discovery, user searches, and postmortems. The available operations can support both read-only investigation and authorized changes to operational records.

Incident tools can list records with filters and pagination, retrieve an incident by ID or number, create and update incidents, move them through statuses, acknowledge them, add timeline events, escalate them, and page a responder through Slack or email. Other tools identify the current on-call person, list or inspect services, find teams and escalation policies, and create or retrieve postmortems.

## How it works

The server acts as a stateless translation layer. An MCP client sends a tool call over stdio or streamable HTTP, and the process makes an HTTPS request to the Runframe API using the configured API key. No application data is stored locally.

Authorization comes from the scopes attached to the Runframe API key. Read and write operations require different Runframe permissions, including incident, on-call, service, postmortem, team, and user scopes. In HTTP mode, a separate bearer token protects access to the MCP endpoint.

The incident tools follow Runframe’s public V1 API conventions. Incident creation uses public service keys, while incident paths use incident numbers such as `INC-2026-001`. User and team lookup tools can help resolve the email addresses and exact team names needed for filtering or assignment.

## Setup and configuration

Install the package with Node.js 20 or newer and obtain an API key from Runframe settings. For a local client, the usual command is:

```bash
npx -y @runframe/mcp-server
```

Set `RUNFRAME_API_KEY` in the client configuration. `RUNFRAME_API_URL` can override the default `https://runframe.io` endpoint. An interactive setup command is also available:

```bash
npx @runframe/mcp-server --setup
```

stdio is the default transport and is suitable for clients such as Claude Code, Cursor, VS Code, and Claude Desktop. Streamable HTTP can be started with `--transport http`, a port, and a host. HTTP deployments require `MCP_ACCESS_TOKEN`; multiple comma-separated tokens support rotation. Docker runs HTTP transport on port 3100 by default.

## Tools and capabilities

The 17 tools are grouped as follows:

- Incidents: list, retrieve, create, update, change status, acknowledge, add events, escalate, and page responders.
- On-call: retrieve the current on-call assignment.
- Services: list services and retrieve service details.
- Postmortems: create a postmortem or retrieve one for an incident.
- Teams: list teams and retrieve a severity-based escalation policy.
- Users: search by name or email, with filters for inactive and active users.

Incident creation defaults severity to `SEV2` when omitted, accepts an idempotency key, and enforces title, description, and service-count limits from the V1 contract. Valid SLA configuration is required for the requested severity.

## Limitations and notes

runframe-mcp-server MCP server does not provide its own authorization model for Runframe actions; the API key’s scopes determine what calls can do. HTTP mode does not provide TLS, rate limiting, or general internet-facing protection. A reverse proxy should handle TLS and rate limiting, and private networking or a VPN is preferred for remote exposure.

The server validates HTTP method and host-related requests, limits declared content length to 1 MB and headers to 8 KB, and applies a 15-second upstream timeout. Runframe API rate-limit responses are returned as 429 errors with retry guidance. Before creating incidents, discover valid public service keys with the service-list tool; use the user and team tools when exact email or team identifiers are needed.

_Full upstream README: https://allmcps.com/mcp/runframe-mcp-server/readme_