MCP clients

AlertINT runs a persistent MCP Streamable HTTP server on port 9912, started inside alertint serve whenever the ALERTINT_MCP_TOKEN env var is set (presence-based; mcp.enabled: false forces it off). Any MCP-capable AI agent can connect to it and query incidents, evidence packs, and live metrics in natural language.

Endpoint: http://<host>:9912/mcp

Auth: Bearer token — the value of ALERTINT_MCP_TOKEN (or whichever env var mcp.token_env names in your config). The token is an opaque secret — the agent compares it byte-for-byte, so any long random string of printable ASCII works; openssl rand -hex 32 in the docs is just one way to generate one. This is a shared team credential: every client below presents the same value, so store it where teammates can retrieve it (a password manager or secret store) — not only in the deployment that set it. In a Kubernetes setup, read it back from the Secret if it wasn't saved at creation time (kubectl get secret <name> -o jsonpath='{.data.ALERTINT_MCP_TOKEN}' | base64 -d). If the value is lost entirely, set a new one and restart the agent, then update every connected client.

Copy-paste versions of the configs below also ship in the repo under examples/mcp-clients/.

Claude Code#

Create .mcp.json at your project root (or merge into ~/.claude.json for global access), then reload with /mcp:

{
  "mcpServers": {
    "alertint": {
      "type": "http",
      "url": "http://localhost:9912/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ALERTINT_MCP_TOKEN"
      }
    }
  }
}

Cursor#

Merge into ~/.cursor/mcp.json (create if absent), then restart Cursor and check Settings → MCP to confirm the server is listed:

{
  "mcpServers": {
    "alertint": {
      "url": "http://localhost:9912/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ALERTINT_MCP_TOKEN"
      }
    }
  }
}

Windsurf#

Merge into ~/.codeium/windsurf/mcp_config.json (create if absent), then restart Windsurf and check Settings → MCP Servers:

{
  "mcpServers": {
    "alertint": {
      "serverUrl": "http://localhost:9912/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ALERTINT_MCP_TOKEN"
      }
    }
  }
}

Available tools#

Tool	Description
alertint_list_incidents	List incidents with optional status and limit filters.
alertint_get_incident	Get full analysis details for one incident by ID.
alertint_search_alerts	Search raw alerts by label key and value.
alertint_get_evidence_pack	Get the evidence pack and Prometheus metrics for an incident.
alertint_verify_audit	Verify the hash-chained audit log and report any tampering.
prometheus_query	Instant PromQL query against the connected Prometheus (requires Prometheus enabled).
prometheus_query_range	Range PromQL query with auto-stepped resolution (requires Prometheus enabled).
sentry_issues_list	List live, distilled Sentry issues for a project (+ optional environment) by status (unresolved/resolved/ignored); requires the Sentry Error source enabled.
sentry_issues_trace	Return full distilled stacktraces (file:line, function, in_app) for up to 10 Sentry issue ids; requires the Sentry Error source enabled.

All tools read local AlertINT state; the Prometheus tools additionally issue queries to the configured Prometheus instance — see Prometheus.