PreviewMCP is not available yet. The tools, connection flow and responses below are illustrative.

Planned MCP server

Ask your assistant what’s down.

The planned Model Context Protocol server will let coding agents read service status, active incidents and history while you debug. It will be built after the account and application layers are stable.

Claude CodeCursorVS CodeCodex

1 · Connect an accountPlanned

1. Sign in to IgniteStatus
2. Approve read-only stack access
3. Add the generated server URL to your client

2 · Configuration shapeIllustrative

{
  "server": "<planned HTTP endpoint>",
  "authorization": "Bearer <account token>"
}

Draft tool surface

Proposed read-only tools

These names describe the intended use cases, not a published server contract. The first implementation will reuse the same application services as the web experience.

list_stack

Current status of every followed service with a compact summary.

no arguments

get_service

Status and component breakdown for one service.

slug: string

get_incident

Published timeline for an active or recent incident.

id: string

search_history

Find past incidents by service, component or date range.

query, since?

Illustrative conversation

In practice

preview only · not connected

My pipeline has been queued for 20 minutes. Me or them?

IGNITESTATUS · proposed get_incident resultThem. Azure DevOps Pipelines is degraded.

Sample response: build-agent pool saturation was identified and mitigation is in progress.

MCP remains planned for Phase 9

No package, endpoint, token or paid MCP plan is offered today.

Browse current status