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" } }}