Skip to main content
Glama

Spike.sh MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
80.7% over 54 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
m190/usefulapi-mcp
GitHub Stars
0

TDQS

A4.2/5.0

Scored across 16 tools

Disambiguation5/5

Each tool targets a distinct resource and action (e.g., incidents, escalations, on-calls, services, teams) with no overlap. Incident tools are further subdivided by status and action, making misselection unlikely.

Naming Consistency5/5

All tools follow a 'spike_verb_noun' pattern with snake_case. Verbs are consistently action-oriented (list, get, acknowledge, resolve, set), with only one longer name (spike_who_is_on_call_next) that still fits the pattern.

Tool Count5/5

16 tools is well-scoped for an incident management server. It covers listing, fetching, and mutating incidents, plus supporting resources (escalations, on-calls, services, teams) without being overwhelming.

Completeness4/5

The tool surface covers the core incident lifecycle (trigger, acknowledge, resolve, priority) and provides read access to related resources. Minor gaps exist (no create/update/delete for non-incident resources), but the set is complete for typical incident response workflows.

Available Tools

16 tools
spike_acknowledge_incidentsAcknowledge incidents
Destructive
Inspect

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:[...]}.

ParametersJSON Schema
NameRequiredDescriptionDefault
idsYesIncident ids (the incident `_id` values) to acknowledge.
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_get_escalationGet escalation policy
Read-only
Inspect

Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
escalationIdYesThe escalation policy's _id (from spike_list_escalations).
spike_get_incidentGet incident
Read-only
Inspect

Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
counterIdYesThe incident's counterId (its human-facing incident number/id).
spike_get_incident_activity_logGet incident activity log
Read-only
Inspect

Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
counterIdYesThe incident's counterId.
spike_get_on_callGet on-call schedule
Read-only
Inspect

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).

ParametersJSON Schema
NameRequiredDescriptionDefault
fromNoISO timestamp to render upcoming shifts from (e.g. "2026-07-19T00:00:00Z").
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
oncallIdYesThe on-call schedule's id (from spike_list_on_calls).
spike_get_serviceGet service
Read-only
Inspect

Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
counterIdYesThe service's counterId (from spike_list_services).
spike_list_acknowledged_incidentsList acknowledged incidents
Read-only
Inspect

List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_list_escalationsList escalation policies
Read-only
Inspect

List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_list_incidentsList incidents
Read-only
Inspect

List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number for pagination.
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
perPageNoResults per page.
spike_list_on_callsList on-call schedules
Read-only
Inspect

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).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_list_servicesList services
Read-only
Inspect

List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_list_teamsList teams
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

spike_list_triggered_incidentsList triggered incidents
Read-only
Inspect

List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_resolve_incidentsResolve incidents
Destructive
Inspect

RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.

ParametersJSON Schema
NameRequiredDescriptionDefault
idsYesIncident ids (the incident `_id` values) to resolve.
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
spike_set_incident_prioritySet incident priority
Destructive
Inspect

Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.

ParametersJSON Schema
NameRequiredDescriptionDefault
idsYesIncident ids (the incident `_id` values) to update.
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
priorityYesPriority level: p1 (highest) .. p5 (lowest).
spike_who_is_on_call_nextWho is on call next
Read-only
Inspect

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).

ParametersJSON Schema
NameRequiredDescriptionDefault
teamIdNoThe 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams.
oncallIdYesThe on-call schedule's id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 16 tool updates
    • Changedspike_acknowledge_incidents1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_get_escalation1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_get_incident1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_get_incident_activity_log1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_get_on_call1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_get_service1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_acknowledged_incidents1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_escalations1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_incidents1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_on_calls1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_services1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_teams1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_list_triggered_incidents1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_resolve_incidents1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_set_incident_priority1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedspike_who_is_on_call_next1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 16 tool updates
    • First observedspike_acknowledge_incidents
    • First observedspike_get_escalation
    • First observedspike_get_incident
    • First observedspike_get_incident_activity_log
    • First observedspike_get_on_call
    • First observedspike_get_service
    • First observedspike_list_acknowledged_incidents
    • First observedspike_list_escalations
    • First observedspike_list_incidents
    • First observedspike_list_on_calls
    • First observedspike_list_services
    • First observedspike_list_teams
    • First observedspike_list_triggered_incidents
    • First observedspike_resolve_incidents
    • First observedspike_set_incident_priority
    • First observedspike_who_is_on_call_next

Related MCP Connectors

Related MCP Servers

  • pagerduty-mcp

    chenzhaoxuan0
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.
    MIT
  • StackWitness by stackwitness

    StackWitnessofficial

    stackwitness
    F
    license
    Not graded
    quality
    C
    maintenance
    Let agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).
    -

  • PagerDuty MCP Server

    dinesh-it
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to interact with PagerDuty services, incidents, schedules, and on-call management through natural language.
    -

  • jira-alerts-mcp

    rrvrs
    A
    license
    A
    quality
    A
    maintenance
    Enables interaction with Jira Service Management Operations alerts and on-call schedules, including searching alerts, reading notes and activity logs, acknowledging, closing, annotating, adding responders, and querying current and next on-call rotations.
    28
    80 npm
    4
    Apache 2.0
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources