Check infrastructure health, manage incidents, and run runbooks in Faultline.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-fltln-faultline": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Check infrastructure health, manage incidents, and run runbooks in Faultline.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP Server for kubernetes management commands
MCP server for ZenML - browse stacks, pipelines, runs, artifacts & trigger pipeline runs via API
MCP Security Weekly
Get CVE alerts and security updates for io.fltln/faultline and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
flt_....https://mcp.fltln.io/mcp, sending the key as
either X-API-Key: flt_... or Authorization: Bearer flt_....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_..." }
}
}
}
| Tool | What it does |
|---|---|
list_services | Monitor inventory with current status (optional status filter) |
get_service | One service + its 10 most recent checks (for diagnosis) |
list_incidents | Open incidents (or status: "resolved" for history) |
get_incident | Full incident record: timeline, AI summary, post-mortem |
acknowledge_incident | Acknowledge an incident — stops further escalation |
resolve_incident | Resolve with an optional note (recorded on the timeline) |
who_is_on_call | Current on-call per schedule, with shift end time |
list_anomalies | Recent learned-baseline latency anomalies (observed vs baseline, z-score, hours sustained, auto-opened incident if any) |
diagnose_incident | Recommend the next action (run runbook / escalate / resolve / wait) + candidate runbooks. Analysis only — changes nothing |
run_runbook | Execute one chosen runbook against an incident — mutates infrastructure (can restart/scale services) |
run_runbook is the only tool that changes
infrastructure. Its description instructs the calling agent to use it only
after diagnose_incident recommended it and you've explicitly confirmed.Questions or issues: support@fltln.io or the Faultline dashboard.