Runframe

Manage incidents fromClaude Code, Cursor, or VS Code

Your AI agent already knows your codebase. Now it can create incidents, page on-call engineers, and track resolution through Runframe. No new tool to learn.

Your agent already knows your system better than ours ever will.

The agent running in your IDE has read your codebase, seen your commits, and helped you debug at 2 AM. It knows your deploy history and your architecture. It just can't create an incident, page someone, or update a timeline. Runframe fixes that.

Tools across the full incident lifecycle.

npx @runframe/mcp-server --setup. Works with Claude, Cursor, Windsurf, VS Code. One config file, no custom integration.

Declare incidents with severity, change status, acknowledge, update, and resolve. All through structured MCP calls.

When the agent detects something it can't fix alone, it pages the on-call engineer. Slack DM, email, and escalation policies all apply.

Agents add investigation findings, log links, and remediation steps to the incident timeline. The human responder walks in with full context.

Look up who is on-call for a service, check escalation policies, list teams. The agent knows who to page before it pages them.

After resolution, agents can create postmortem drafts from incident data. Timeline, impact, and action items are already captured.

npx @runframe/mcp-server --setup. It writes the config file for your AI tool. Takes 30 seconds.

Your monitoring agent, CI pipeline, or coding assistant spots a problem. It creates an incident via MCP with severity and context.

Runframe pages the on-call engineer via Slack and email. The agent's findings are already on the timeline.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Seamlessly bring real-time production context—logs, metrics, and traces—into your local environment to auto-fix code faster.

Provides access to OpenTelemetry traces and metrics through Logfire.

Zabbix MCP Server with all functions and validations

MCP to interact with Alertmanager - observability alerts management tool

An MCP server for integrating AI agents with the SkyWalking observability platform and its ecosystem.

Monitor uptime, manage incidents, configure alerting, and query third-party dependency status through DevHelm's monitoring platform

Access and manage Grafana resources, including dashboards, datasources, Prometheus, Loki, and alerting.

A server for querying Loki logs from Grafana.

An MCP server for log analysis using the LogAI framework, with optional Grafana and GitHub integrations.

A Go-based server to query Grafana Loki logs using the Model Context Protocol (MCP).