MCP server
Spike.sh MCP by usefulapi
io.usefulapi/spikesh
Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Working at last checkVerified publisher: usefulapi.ioAbout 2,778 tokens per request once connected16 tools
https://spikesh.usefulapi.io/mcp
At a glance
- Type
- MCP server
- Publisher
- usefulapi.io (verified by the MCP Registry)
- Status
- Working at last check
- Tools
- 16
- Token cost
- About 2,778 tokens per request
- Sets up in
- Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok
- Last checked
- 26 Oct 2026, 08:29 UTC
Connect it to your agent
Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.
Claude Code
claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp
Claude Desktop
Settings → Connectors → Add custom connector, and paste the URL.
Codex (config.toml)
[mcp_servers.spikesh] url = "https://spikesh.usefulapi.io/mcp"
Gemini CLI
{"mcpServers":{"spikesh":{"httpUrl":"https://spikesh.usefulapi.io/mcp"}}}
Cursor
{"mcpServers":{"spikesh":{"url":"https://spikesh.usefulapi.io/mcp"}}}
VS Code
{"servers":{"spikesh":{"type":"http","url":"https://spikesh.usefulapi.io/mcp"}}}
Antigravity
agy mcp add spikesh https://spikesh.usefulapi.io/mcp
ChatGPT
Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.
OpenAI API (Responses tools)
{"type":"mcp","server_label":"spikesh","server_url":"https://spikesh.usefulapi.io/mcp","require_approval":"always"}
Grok (xAI API tools)
{"type":"mcp","server_label":"spikesh","server_url":"https://spikesh.usefulapi.io/mcp"}
Tools
spike_acknowledge_incidents~195 tokens
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_get_escalation~178 tokens
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).spike_get_incident~183 tokens
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~184 tokens
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_get_on_call~228 tokens
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_get_service~175 tokens
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).spike_list_acknowledged_incidents~141 tokens
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).spike_list_escalations~140 tokens
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).spike_list_incidents~214 tokens
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_on_calls~156 tokens
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_list_services~139 tokens
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).spike_list_teams~113 tokens
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_triggered_incidents~144 tokens
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).spike_resolve_incidents~183 tokens
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~224 tokens
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.spike_who_is_on_call_next~181 tokens
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).
Related MCP servers
- Squadcast MCP by usefulapi
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents. - Better Stack MCP by usefulapi
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents. - All Quiet MCP by usefulapi
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides. - zobrx
Read-only zobrx e-commerce data: P&L, orders, inventory, marketplace, tax & shelf insights. - Uptimepage
Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org. - StatusPal MCP by usefulapi
Read status-page status, services, incidents and metrics; create, update and publish incidents. - Release Radar MCP by usefulapi
Correlate GitHub releases with Sentry issues and PagerDuty incidents. - SYNTHORA x402 Intelligence Mesh
Calibrated intelligence via x402 (USDC Base). ERC-8004 #84581: 272 payments, 49 wallets.
Badge for your README
[](https://aptlynx.net/servers/io.usefulapi/spikesh)
Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents