io.usefulapi由 usefulapi.io 发布官方发布者v1.36.5更新于 Nov 8, 2026
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
发布方自己的服务：Ably MCP by usefulapi
托管的 Spike.sh 连接器，让助手读取事件、值班表、升级策略与服务，并确认、解决或调整事件优先级。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.usefulapi%2Fspikesh/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"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.
来源：servers/spikesh/README.md，提交 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.
无需输入参数。
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).
teamIdcounterId必填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).
teamIdcounterId必填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).
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).
fromteamIdoncallId必填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).
teamIdoncallId必填List 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).
teamIdescalationId必填List 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).
teamIdcounterId必填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:[...]}.
ids必填teamIdResolve incidents
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
ids必填teamIdSet incident priority
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
ids必填teamIdpriority必填已满足适用检查项的 100%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
io.usefulapi官方发布者
面向 Ably 实时消息的托管 MCP 服务器：查看频道历史、在线状态与占用情况，发布消息，并查看应用用量与配置。
io.usefulapi官方发布者
托管的只读 MCP 服务器，让助手读取 Tiltify 的募捐活动、捐款记录以及捐款人和筹款人排行榜。
io.usefulapi官方发布者
托管的 Termii 服务器，让助手发送短信，并查询钱包余额、DND 状态、发送方 ID 和消息记录。
io.usefulapi官方发布者
托管型 MCP 服务器，让助手读取 Temp Stick 的温度与湿度传感器、其读数以及告警通知。
io.usefulapi官方发布者
将助手连接到 Stibee 邮件营销工作区，可读取地址簿、订阅者和邮件统计，并添加订阅者与分组。
{ "mcpServers": { "spikesh": { "url": "https://spikesh.usefulapi.io/mcp" } }}