io.usefulapiPublished by usefulapi.ioOfficial publisherv1.36.5Updated Nov 8, 2026
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
The publisher's own server: Ably MCP by usefulapi
Hosted Spike.sh connector that lets an assistant read incidents, on-call schedules, escalations and services, and acknowledge, resolve or reprioritize…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Fspikesh/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"spike-sh-by-usefulapi": {
"type": "http",
"url": "https://spikesh.usefulapi.io/mcp"
}
}
}Manage Spike.sh incident response from Claude, Cursor, or any MCP client — read incidents, on-call schedules, escalation policies and services, and acknowledge, resolve, or set the priority of incidents. Hosted, no local install: connect with your Spike.sh API key.
Live endpoint: https://spikesh.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://spikesh.usefulapi.io/mcp.claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Spike.sh credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/spikesh/
On first connect you'll paste your Spike.sh API key (Spike.sh → Settings → API). It's validated, stored per-user, and scoped to you — no keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with spike_upgrade (it returns a Stripe Checkout link). Cancel any time with spike_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running spike_upgrade before then undoes the cancel. Or write to [email protected].
MIT — see LICENSE. Documentation only; the server is hosted.
Source: servers/spikesh/README.md at commit 4046075
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.
Takes no parameters.
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).
pageteamIdperPageList triggered incidents
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
teamIdList acknowledged incidents
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
teamIdGet incident
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
teamIdcounterIdrequiredGet 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).
teamIdcounterIdrequiredList 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).
teamIdGet 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).
fromteamIdoncallIdrequiredWho 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).
teamIdoncallIdrequiredList escalation policies
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
teamIdGet escalation policy
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
teamIdescalationIdrequiredList services
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
teamIdGet service
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
teamIdcounterIdrequiredAcknowledge 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:[...]}.
idsrequiredteamIdResolve incidents
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
idsrequiredteamIdSet incident priority
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
idsrequiredteamIdpriorityrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably realtime messaging: inspect channel history, presence and occupancy, publish messages, and review app usage and configuration.
io.usefulapiOfficial publisher
Hosted read-only MCP server that lets an assistant read Tiltify campaigns, donations and top donor and fundraiser leaderboards.
io.usefulapiOfficial publisher
Hosted Termii server that lets an assistant send SMS, check wallet balance, DND status, sender IDs and message history.
io.usefulapiOfficial publisher
Hosted MCP server that lets an assistant read Temp Stick temperature and humidity sensors, their readings and alert notifications.
io.usefulapiOfficial publisher
Connects an assistant to a Stibee email marketing workspace to read address books, subscribers and email stats, and to add subscribers and group members.
{ "mcpServers": { "spikesh": { "url": "https://spikesh.usefulapi.io/mcp" } }}