このMCPでできること
Manages Spike.sh incident response data, services, teams, escalation policies, on-call schedules, priorities, acknowledgments, and resolutions.
機能
ツール
16
ツール
spike_acknowledge_incidents
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:[...]}.
破壊的操作あり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['ids'], 'properties': {'ids': {'type': 'array', 'items': {'type': 'string'}, 'minItems': 1, 'description': 'Incident ids (the incident `_id` values) to acknowledge.'}, 'teamId': {'type': 'string', 'description': 'The 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_escalation
Get escalation policy
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['escalationId'], 'properties': {'teamId': {'type': 'string', 'description': 'The 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.'}, 'escalationId': {'type': 'string', 'description': "The escalation policy's _id (from spike_list_escalations)."}}}
spike_get_incident
Get incident
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['counterId'], 'properties': {'teamId': {'type': 'string', 'description': 'The 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.'}, 'counterId': {'type': 'string', 'description': "The incident's counterId (its human-facing incident number/id)."}}}
spike_get_incident_activity_log
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).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['counterId'], 'properties': {'teamId': {'type': 'string', 'description': 'The 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.'}, 'counterId': {'type': 'string', 'description': "The incident's counterId."}}}
spike_get_on_call
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).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['oncallId'], 'properties': {'from': {'type': 'string', 'description': 'ISO timestamp to render upcoming shifts from (e.g. "2026-07-19T00:00:00Z").'}, 'teamId': {'type': 'string', 'description': 'The 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.'}, 'oncallId': {'type': 'string', 'description': "The on-call schedule's id (from spike_list_on_calls)."}}}
spike_get_service
Get service
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['counterId'], 'properties': {'teamId': {'type': 'string', 'description': 'The 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.'}, 'counterId': {'type': 'string', 'description': "The service's counterId (from spike_list_services)."}}}
spike_list_acknowledged_incidents
List acknowledged incidents
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'teamId': {'type': 'string', 'description': 'The 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_escalations
List escalation policies
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'teamId': {'type': 'string', 'description': 'The 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_incidents
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).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'page': {'type': 'integer', 'maximum': 9007199254740991, 'minimum': 1, 'description': '1-based page number for pagination.'}, 'teamId': {'type': 'string', 'description': 'The 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.'}, 'perPage': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Results per page.'}}}
spike_list_on_calls
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).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'teamId': {'type': 'string', 'description': 'The 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_services
List services
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'teamId': {'type': 'string', 'description': 'The 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_teams
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.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
spike_list_triggered_incidents
List triggered incidents
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'teamId': {'type': 'string', 'description': 'The 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_incidents
Resolve incidents
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
破壊的操作あり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['ids'], 'properties': {'ids': {'type': 'array', 'items': {'type': 'string'}, 'minItems': 1, 'description': 'Incident ids (the incident `_id` values) to resolve.'}, 'teamId': {'type': 'string', 'description': 'The 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_priority
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}.
破壊的操作あり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['ids', 'priority'], 'properties': {'ids': {'type': 'array', 'items': {'type': 'string'}, 'minItems': 1, 'description': 'Incident ids (the incident `_id` values) to update.'}, 'teamId': {'type': 'string', 'description': 'The 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.'}, 'priority': {'enum': ['p1', 'p2', 'p3', 'p4', 'p5'], 'type': 'string', 'description': 'Priority level: p1 (highest) .. p5 (lowest).'}}}
spike_who_is_on_call_next
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).
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['oncallId'], 'properties': {'teamId': {'type': 'string', 'description': 'The 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.'}, 'oncallId': {'type': 'string', 'description': "The on-call schedule's id."}}}
履歴
最近のツール変更
追加
spike_set_incident_priority
2026年9月21日2:44
追加
spike_resolve_incidents
2026年9月21日2:44
追加
spike_acknowledge_incidents
2026年9月21日2:44
追加
spike_get_service
2026年9月21日2:44
追加
spike_list_services
2026年9月21日2:44
追加
spike_get_escalation
2026年9月21日2:44
追加
spike_list_escalations
2026年9月21日2:44
追加
spike_who_is_on_call_next
2026年9月21日2:44
追加
spike_get_on_call
2026年9月21日2:44
追加
spike_list_on_calls
2026年9月21日2:44
追加
spike_get_incident_activity_log
2026年9月21日2:44
追加
spike_get_incident
2026年9月21日2:44
追加
spike_list_acknowledged_incidents
2026年9月21日2:44
追加
spike_list_triggered_incidents
2026年9月21日2:44
追加
spike_list_incidents
2026年9月21日2:44
追加
spike_list_teams
2026年9月21日2:44
関連MCP
類似のMCPサーバー
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
OSIR Domain Registrar
com.osir/domain-registrar
Manages domain registration and transfers, DNS, VPS instances, SSH keys, hosted email, account funding, and related infrastructur…
hyperping
com.hyperping/hyperping
Manages uptime, HTTP, DNS, port, and API monitoring with outage diagnostics, latency and SLA metrics, alert integrations, escalat…
Boat House
com.boathousecloud/boathouse
Deploys and operates small containerized web applications with releases, rollbacks, persistent data, access controls, secrets, bi…
hookpulse
net.hookpulse/hookpulse
Creates and manages dead-man monitoring endpoints for cron jobs and webhooks, detects missed or failed runs, and provides event, …
Plutus
com.plutus-cloud/plutus-cost-data
Analyzes cloud, AI, and SaaS costs with spend queries, budgets, anomalies, usage metrics, savings recommendations, dashboards, an…
Power Automate MCP Server by Flow Studio
io.github.ninihen1/flowstudio-mcp
Builds, updates, runs, monitors, debugs, and governs Microsoft Power Automate flows, environments, connectors, and run histories.
Tomorrow Central: Cloud Cost Sentinel
com.tomorrowcentral/aws-cloud-cost-sentinel
Looks up AWS prices, estimates architecture and workload costs, compares regions and architectures, and scans linked AWS accounts…