Faultline MCP server

Faultline MCP Server

Faultline is infrastructure monitoring and incident management for DevOps/SRE teams. This repo documents faultline-mcp — Faultline's remote MCP server, which lets AI agents (Claude, Claude Code, Claude Desktop, or anything MCP-compatible) operate Faultline: check infrastructure health, inspect and act on incidents, look up who's on call, and run approved runbooks.

This repo is documentation only. The server is hosted by Faultline at https://mcp.fltln.io/mcp (Streamable HTTP transport) — there's nothing to install or run yourself.

Setup

flt_....

1. Create an API key in Faultline: Settings → API Keys. Keys look like

either X-API-Key: flt... or Authorization: Bearer flt....

1. Point your MCP client at https://mcp.fltln.io/mcp, sending the key as

Claude Code:

claude mcp add --transport http faultline-mcp https://mcp.fltln.io/mcp \
  --header "X-API-Key: flt_..."

Clients that take raw JSON config (Claude Desktop, etc.):

{
  "mcpServers": {
    "faultline": {
      "type": "http",
      "url": "https://mcp.fltln.io/mcp",
      "headers": { "X-API-Key": "flt_..." }
    }
  }
}

Tools

Security

only for the duration of each request, proxied straight through to Faultline's API.

• Scoped to your API key. The server never stores your key — it's used

infrastructure. Its description instructs the calling agent to use it only after diagnose_incident recommended it and you've explicitly confirmed.

• Approval-gated mutation. run_runbook is the only tool that changes

API key — one key can never see or affect another tenant's data.

• Tenant-isolated. Every request is scoped to the tenant that owns the

Support

Questions or issues: support@fltln.io or the Faultline dashboard.