Firebreak

v0.1.0

A powerful MCP server built with NitroStack

Connection Setup

Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server): 

{
  "mcpServers": {
    // your other mcp servers
    "firebreak": {
      "url": "http://firebreak-6ad62218-limbo-alive-oss-connect.app.nitrocloud.ai/mcp"
    }
  }
}

Connect remote tools directly via Claude's Web UI:

Add custom connector BETA
Connect Claude to your data and tools. Learn more about connectors or get started with pre-built ones.
Advanced settings
Only use connectors from developers you trust. Anthropic does not control which tools developers make available and cannot verify that they will work as intended or that they won't change.
Building an MCP server? Report issues and subscribe to updates here

Configure custom tools directly via ChatGPT's Web UI:

New App
Icon (optional)
PNG only. Best results at 256 x 256 px or larger. Max file size: 10 KB
Name
Description (optional)
Connection
Authentication
Custom MCP servers introduce risk. Learn more
OpenAI hasn't reviewed this MCP server. Attackers may attempt to steal your data or trick the model into taking unintended actions, including destroying data.
Read the guide

Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json): 

{
  "mcpServers": {
    // your other mcp servers
    "firebreak": {
      "serverUrl": "http://firebreak-6ad62218-limbo-alive-oss-connect.app.nitrocloud.ai/mcp"
    }
  }
}

Add the following configuration block to your Codex configuration file (~/.codex/config.toml): 

[mcp_servers.firebreak]
url = "http://firebreak-6ad62218-limbo-alive-oss-connect.app.nitrocloud.ai/mcp"

Connect directly using the Server-Sent Events endpoint: 

http://firebreak-6ad62218-limbo-alive-oss-connect.app.nitrocloud.ai/mcp
Available Tools
list_incidents

List Firebreak incidents. Defaults to active ones. Use this first when the user asks what is broken, on fire, or failing.

get_incident

Get one Firebreak incident with status, deployments, top suspects, the proposed action and recent timeline. Use after list_incidents. Accepts the incident id (inc_…) or its number (e.g. 12 for INC-12).

get_suspects

Show the commits most likely to have caused an incident, ranked by a deterministic score with evidence (files and functions that match the error). Use when the user asks what broke or which commit caused it.

get_analysis

Get the AI-written explanation and fix suggestions for an incident, if available. This is advisory; suspects and actions are computed without AI.

get_timeline

Get the ordered audit trail of an incident: alerts, ranking, proposals, approvals, rollback, health checks.

propose_rollback

Propose rolling production back to the last good deployment for an incident. Runs safety checks. Does NOT change production: a human must approve in Firebreak (approveUrl). Safe to call twice; returns the existing proposal.

get_action_status

Get the status of a rollback: awaiting approval, executing, verifying with live health checks, verified, or failed. Call repeatedly to follow progress.

approve_action

Approve a proposed rollback so Firebreak executes it on Vercel and verifies recovery. This changes production. Only call when the user has explicitly said to approve this specific action. Requires a key with the 'Approve rollbacks' permission.

list_services

List the services Firebreak protects (GitHub repo + Vercel project + health URL) and whether each has an active incident.