Spike.sh MCP server. Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Add to your MCP config, then reload & authorize:
{
"mcpServers": {
"spikesh": {
"url": "https://spikesh.usefulapi.io/mcp"
}
}
}| Tool | Type | What it does |
|---|---|---|
spike_list_teams | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | List on-call schedules 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 | read | Get on-call schedule 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 | read | 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 | read | List escalation policies List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped). |
spike_get_escalation | read | Get escalation policy Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped). |
spike_list_services | read | List services List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped). |
spike_get_service | read | Get service Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped). |
spike_acknowledge_incidents | write | 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 | write | 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 | write | 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_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
spike_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Spike.sh tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Read-only; does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.