MCP

What it does

RetraceKit exposes a remote MCP server at https://api.retracekit.cloud/mcp. Agents in Cursor, Claude Code, Codex, VS Code, and other MCP clients can list the project, read issues and incidents, change status, and request AI explanations — the same triage surface as the app.

API key

Use the same project API key as the SDK (from project settings in the app). No separate MCP token.

Client setup

Any Streamable HTTP MCP client needs the URL https://api.retracekit.cloud/mcp and header Authorization: Bearer <project-api-key>. Cursor example ( mcp.json):

{
  "mcpServers": {
    "retracekit": {
      "url": "https://api.retracekit.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ${env:RETRACE_KIT_API_KEY}"
      }
    }
  }
}

Set RETRACE_KIT_API_KEY to the project API key (same value as SDK apiKey). Claude Code, Codex, VS Code Copilot, Windsurf, Zed, and similar tools use the same URL and Bearer header in their own MCP config. Restart or reload MCP if tools do not appear.

Tools

• list_projects — the authenticated project
• list_issues / get_issue / update_issue_status
• list_incidents / get_incident / update_incident_status
• list_issue_incidents — incidents linked to an issue
• explain_issue / explain_incident — AI briefs

Issue statuses: OPEN, RESOLVED, IGNORED. Manual incident statuses: INVESTIGATING, RESOLVED, ACTIVE.

Refs

• Issue: {projectKey}-{issueKey} — e.g. PRO-123
• Incident: {projectKey}-I{incidentKey} — e.g. PRO-I1

List tools take projectKey (not UUID). Detail and status tools take the human-readable ref.

Announce and examples: RetraceKit remote MCP.