About this integration
MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.5
- Package
- @runframe/mcp-server
- Last compatibility test
- Not independently tested
Connect your agent
@runframe/mcp-serverExisting catalog identity, slug, repository, package, version, endpoint, transport, registry metadata, and prior source facts are preserved by the eligibility-update path. Publisher documentation was reviewed without executing incident actions; write tools can alter incident state or page responders.
Capabilities: Incident triage and lifecycle updates, On-call and escalation lookup, Service and team lookup, Postmortem and responder workflows
Connected profiles
Additional details
io.github.runframe/runframe-mcp-server
Source ↗ · Checked 2026-09-170.1.5
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17RUNFRAME_API_KEY
Source ↗ · Checked 2026-09-17@runframe/mcp-server
Source ↗ · Checked 2026-09-190.1.15
Source ↗ · Checked 2026-09-19The server is documented as stateless and runs locally through npx; the reviewed listing connection remains stdio rather than the separately available HTTP mode.
Source ↗ · Checked 2026-09-19RUNFRAME_API_KEY is required and scopes downstream Runframe API requests; HTTP mode additionally requires MCP_ACCESS_TOKEN but is outside this stdio qualification.
Source ↗ · Checked 2026-09-19The existing listing remains a stdio connection spawned with npx -y @runframe/mcp-server and RUNFRAME_API_KEY in the client environment.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19