Skip to content
MCP server

Spike.sh MCP by usefulapi

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set…

Install
Runs
Remotely
Version
1.40.0
Listing updated
4 days ago

About Spike.sh MCP by usefulapi

Spike.sh MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.

Install

Run in a terminal

claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp

Add to Settings → Connectors → Add custom connector

https://spikesh.usefulapi.io/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "spikesh": {
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "spikesh": {
      "type": "http",
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "spikesh": {
      "serverUrl": "https://spikesh.usefulapi.io/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "spikesh": {
      "type": "http",
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}

Tools this server provides (16)

Read directly from the server.

spike_list_teams
List all teams in the Spike.sh organization — {teams:[{_id, name, uid, private, org}]}. NOT team-scoped (no x-team-id needed). The `_id` values here are what you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams.
spike_list_incidents
List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).
spike_list_triggered_incidents
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
spike_list_acknowledged_incidents
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
spike_get_incident
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
spike_get_incident_activity_log
Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).
spike_list_on_calls
List a team's on-call schedules — {oncalls:[...]}. Each on-call has an id, name, timezone, and layers. Use the id with spike_get_on_call / spike_who_is_on_call_next. Spike: GET /on-calls (team-scoped).
spike_get_on_call
Get one on-call schedule by id — {oncall:{_id, name, timezone, teams, users, activeShift, renderedShifts}}. `from` optionally sets the window start for rendered shifts. Spike: GET /on-calls/{oncallId} (team-scoped).
spike_who_is_on_call_next
Get the NEXT scheduled shift for an on-call schedule — {nextShift:{userId, startTimeInUTC, endTimeInUTC}} (or {} if none). Spike: GET /on-calls/{oncallId}/who-is-on-call-next (team-scoped).
spike_list_escalations
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
spike_get_escalation
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
spike_list_services
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
spike_get_service
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
spike_acknowledge_incidents
ACKNOWLEDGES one or more incidents — this CHANGES live incident state (stops escalation and marks them as being worked on). Spike: POST /incidents/acknowledge with {ids:[...]}.
spike_resolve_incidents
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
spike_set_incident_priority
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.

Spike.sh MCP by usefulapi FAQ

How do I add Spike.sh MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp