Spike.sh MCP server

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect Spike.shFree 50 tool calls / monthPro $9/mo · $90/yr · pricing20 tools

What can I ask?

Turn on the Spike.sh connector, then ask in plain words. The AI picks the tools.

What you can do with Spike.sh in Claude and ChatGPT

For on-call engineers and SRE teams who handle incidents and on-call shifts in Spike.sh.

See which incidents are open and unacknowledged

The AI lists the triggered incidents of a team, with title, priority and severity, so you see the queue that needs action first.

Review an incident and its activity log

The AI opens one incident by its counter id with comments and repeated incidents, and reads the activity log to show who acknowledged, resolved or commented and when.

Find who is on call next

The AI lists a team's on-call schedules and returns the next shift for one, with the user and its start and end time.

Check escalation policies and services

The AI lists a team's escalation policies and services, and opens one to show its alert rules or its open incidents.

Acknowledge or resolve incidents and set priority

The AI acknowledges or resolves one or more incidents, or sets their priority from p1 to p5. This changes live incident state.

Changes data

How do I connect Spike.sh?

Before you connect

The login page asks for your Spike.sh API key.

Find it in the Spike.sh dashboard → Settings → API (app.spike.sh/api). Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.

Claude claude.ai · Desktop

  1. Open Customize → Connectors, then click + Add → Add custom connector.
  2. Enter the name Spike.sh and this URL, then click Add:
    https://spikesh.usefulapi.io/mcp
  3. Claude opens the login page: enter your Spike.sh API key.
  4. In a chat, click + → Connectors and turn on Spike.sh.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

  1. Open Plugins, click +, then Add custom MCP server.
  2. Enter the name Spike.sh and this URL, choose OAuth as the authentication, confirm the warning and create it:
    https://spikesh.usefulapi.io/mcp
  3. ChatGPT opens the login page: enter your Spike.sh API key.
  4. In Plugins, install Spike.sh, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

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

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

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

VS Code

Add to VS Code or add this to .vscode/mcp.json:

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

Codex

Run these commands. The second one opens the login page:

codex mcp add spikesh --url https://spikesh.usefulapi.io/mcp
codex mcp login spikesh

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

https://spikesh.usefulapi.io/mcp

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: the login page asks for your Spike.sh API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Proper user$9/mo · $90/yr10,000 tool calls / month
Pro+per user$39/mo · $390/yr100,000 tool calls / month

Each paid plan covers this Spike.sh server only. Ask your AI to run spike_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with spike_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with spike_upgrade before then undoes the cancel. Or write to [email protected].

Tools 20

Show all 20 tools (the AI picks them for you)

Read only · 13

  • List teamsspike_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.
  • List incidentsspike_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).
  • List triggered incidentsspike_list_triggered_incidents
    List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
  • List acknowledged incidentsspike_list_acknowledged_incidents
    List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
  • Get incidentspike_get_incident
    Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
  • Get incident activity logspike_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).
  • List on-call schedulesspike_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).
  • Get on-call schedulespike_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).
  • Who is on call nextspike_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).
  • List escalation policiesspike_list_escalations
    List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
  • Get escalation policyspike_get_escalation
    Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
  • List servicesspike_list_services
    List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
  • Get servicespike_get_service
    Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).

Changes data · 3

  • Acknowledge incidentsspike_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:[...]}.
  • Resolve incidentsspike_resolve_incidents
    RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
  • Set incident priorityspike_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}.

Your usefulapi plan · 4

  • Usage status (free-tier meter)spike_usage_status
    Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
  • Request a missing featurespike_request_feature
    Tell usefulapi that the user needs something the Spike.sh tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter.
  • Upgrade to Pro or Pro+spike_upgrade
    Get a paid plan for Spike.sh (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
  • Cancel the Pro subscriptionspike_cancel_subscription
    Cancel the caller's Spike.sh Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run spike_upgrade later to undo the cancel before the period ends. Does not count against the meter.

FAQ

What can I do with Spike.sh in Claude or ChatGPT?

See which incidents are open and unacknowledged. Review an incident and its activity log. Find who is on call next. Check escalation policies and services. Acknowledge or resolve incidents and set priority. See what you can do for the details.

Is this an official Spike.sh product?

No. usefulapi is an independent service. It is not affiliated with or endorsed by Spike.sh. The server calls the Spike.sh API with your own Spike.sh access, so it sees only the data that your account can see.

Can I connect Spike.sh to Claude or ChatGPT?

Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.

What do I need to connect?

The login page asks for your Spike.sh API key. See Before you connect for where to find it.

Do I put my Spike.sh key or an Authorization header in the client config?

No. 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: the login page asks for your Spike.sh API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

How do you keep my Spike.sh credentials?

The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Spike.sh API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Spike.sh.

Can the AI change my Spike.sh data?

Yes, if you approve it. 3 of the 16 Spike.sh tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Spike.sh server only. Cancel any time: your paid plan then runs to the end of the paid period. Run spike_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run spike_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run spike_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a Spike.sh tool that I need is missing?

Tell the AI what you wanted to do. It can send the request with spike_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.

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.

Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.

More Observability MCP servers

AirbrakeAll QuietAuvikAxcientBetter StackChecklyCronitorDead Man's SnitchDicksonOneFieldClimateHealthchecks.ioInstatusNodePingPulsewaySensoristSIGNL4SorrySquadcastStatus.ioStatusCakeStatusCastStatusHubStatuspageStatusPage.meStatusPalTemp Stickupdown.io

All Observability servers →