Release Radar MCP by usefulapi

io.usefulapi由 usefulapi.io 發布官方發布者v1.41.2更新於 Nov 14, 2026

Correlate GitHub releases with Sentry issues and PagerDuty incidents.

發布方自己的服務：Ably MCP by usefulapi

已驗證Streamable HTTP可網頁執行開發者工具安全與監控

概覽

AI 產生的概覽

託管型 MCP 伺服器，把 GitHub 部署、Sentry 問題與 PagerDuty 值班資訊關聯成事故快照與交接簡報。

可以做什麼
  • 把 GitHub 部署、Sentry 問題與 PagerDuty 值班資訊整合成「上次部署後出了什麼問題」的檢視
  • 取得即時事故快照：未解決的 Sentry 問題、進行中的 PagerDuty 事故與目前值班人員
  • 產出跨三項服務的交接班簡報
  • 取得底層資料：儲存庫最新的 GitHub 部署或發行，以及近期未解決的 Sentry 問題
  • 查看本月用量、提出功能需求、升級或取消訂閱
適用情境
適合值班工程師與團隊，讓助理直接回答「上次部署後出了什麼問題」或「現在哪裡出狀況」，不必在 GitHub、Sentry 與 PagerDuty 之間來回切換。
執行需求
遠端 streamable HTTP 端點，無需本機安裝。首次連線時透過 OAuth 登入並填寫 Release Radar 憑證；用戶端設定不需要 API 金鑰或 Authorization 標頭。伺服器需要存取你的 GitHub、Sentry 與 PagerDuty 資料，缺少某項憑證時該服務會單獨降級。
安裝前請注意
免費方案每月僅 50 次工具呼叫；付費方案為 Pro 每月 9 美元、Pro+ 每月 39 美元，升級會回傳 Stripe 結帳連結並立即扣款，取消後當期不退費。Release Radar 憑證依使用者儲存，伺服器會代你讀取 GitHub、Sentry 與 PagerDuty 資料；meta 工具可變更你的訂閱。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Release Radar MCP by usefulapi，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.usefulapi%2Frelease-radar/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "release-radar-by-usefulapi": {
      "type": "http",
      "url": "https://release-radar.usefulapi.io/mcp"
    }
  }
}

README

Release Radar MCP by usefulapi

Correlate GitHub releases with Sentry issues and PagerDuty incidents. Hosted, no local install.

Live endpoint: https://release-radar.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://release-radar.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http release-radar https://release-radar.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "release-radar": {      "url": "https://release-radar.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, and the login page asks for your Release Radar credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/release-radar/

On first connect you'll paste your Release Radar credentials. They are validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
release_radar_whats_broken_since_last_deployreadWhat's broken since the last deploy?
release_radar_incident_snapshotreadCurrent incident snapshot
release_radar_oncall_handoffreadOn-call handoff briefing
release_radar_github_latest_deployreadLatest GitHub deploy/release
release_radar_sentry_recent_issuesreadRecent unresolved Sentry issues
release_radar_usage_statusmetaUsage status (free-tier meter)
release_radar_request_featuremetaRequest a missing feature
release_radar_upgrademetaUpgrade to Pro or Pro+
release_radar_cancel_subscriptionmetaCancel the Pro subscription

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.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this server only. Ask your AI to run release_radar_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 release_radar_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 release_radar_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT

來源：servers/release-radar/README.md，提交 f22f848

工具

5

release_radar_whats_broken_since_last_deploy

What's broken since the last deploy?

COMPOSITE. Finds the latest GitHub deployment/release for a repo, then queries Sentry for unresolved issues SINCE that deploy's timestamp (the deploy time drives the Sentry window), then looks up who's currently on-call in PagerDuty — and synthesizes one situational-awareness object. Degrades gracefully: if Sentry or PagerDuty creds are absent it returns what it can plus a note. GitHub is required (it's the anchor).

輸入參數repo必填owner必填environmentsentry_project

release_radar_incident_snapshot

Current incident snapshot

COMPOSITE. A right-now on-call picture: top unresolved Sentry issues + active (triggered/acknowledged) PagerDuty incidents + who's currently on-call, fused into one snapshot with a human summary. Each service degrades independently if its creds are missing.

輸入參數urgencysentry_project

release_radar_oncall_handoff

On-call handoff briefing

COMPOSITE. A start-of-shift briefing for whoever is currently on call, fusing all three services: (a) PagerDuty current on-call + any active (triggered/acknowledged) incidents they're inheriting, (b) the GitHub deployment/release that most recently shipped (what's live), and (c) Sentry's top unresolved errors. Correlates them into one object — including a heads-up when a fresh deploy coincides with active incidents (a likely culprit). Degrades gracefully: every service is optional; whatever's unconfigured or failing is named in `notes` and the briefing still returns. Never crashes.

輸入參數repo必填owner必填sentry_project

release_radar_github_latest_deploy

Latest GitHub deploy/release

Low-level building block: the latest GitHub deployment for a repo (falls back to the latest release), returning sha + timestamp. Used internally by release_radar_whats_broken_since_last_deploy. GitHub: GET /repos/{owner}/{repo}/deployments.

輸入參數repo必填owner必填environment

release_radar_sentry_recent_issues

Recent unresolved Sentry issues

Low-level building block: unresolved Sentry issues over a relative window. Sentry: GET /api/0/projects/{org}/{project}/issues/?query=is:unresolved.

輸入參數limitenvironmentstatsPeriodsentry_project

版本歷史

26
  1. v1.41.2最新Nov 14, 2026
  2. v1.41.1Nov 13, 2026
  3. v1.40.0Nov 12, 2026
  4. v1.39.3Nov 11, 2026
  5. v1.38.5Nov 8, 2026
  6. v1.38.4Nov 7, 2026
  7. v1.37.3Nov 5, 2026
  8. v1.37.2Nov 5, 2026
  9. v1.37.1Nov 4, 2026
  10. v1.37.0Nov 3, 2026
  11. v1.36.1Nov 3, 2026
  12. v1.35.0Nov 1, 2026
  13. v1.33.0Oct 31, 2026
  14. v1.32.0Oct 31, 2026
  15. v1.31.2Oct 30, 2026
  16. v1.31.0Oct 30, 2026
  17. v1.26.0Oct 26, 2026
  18. v1.22.3Oct 25, 2026
  19. v1.22.0Oct 25, 2026
  20. v1.21.0Oct 24, 2026
  21. v1.18.0Oct 23, 2026
  22. v1.16.4Oct 22, 2026
  23. v1.16.3Oct 21, 2026
  24. v1.11.1Oct 9, 2026
  25. v1.10.0Oct 9, 2026
  26. v1.0.0Sep 29, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Usefulapi 整合

Ably MCP by usefulapi

io.usefulapi官方發布者

針對 Ably 的託管 MCP 伺服器，讓助理檢視頻道、線上狀態與用量統計、發布訊息，並查看應用程式設定。

Streamable HTTP可網頁執行
溝通與協作15 個工具Nov 14, 2026

ROLLER MCP by usefulapi

io.usefulapi官方發布者

唯讀存取 ROLLER 場館資料：搜尋預訂、查詢產品可用性，並查看賓客、免責聲明、禮品卡與每日報表。

Streamable HTTP可網頁執行
資料與分析42 個工具Nov 14, 2026

Planerio MCP by usefulapi

io.usefulapi官方發布者

託管的 Planerio 連接器，讓助理讀取排班、人力需求、可用人員、員工資料、缺勤與年假天數。

Streamable HTTP可網頁執行
效率與工作流6 個工具Nov 14, 2026

Marmin MCP by usefulapi

io.usefulapi官方發布者

唯讀存取 Marmin 的阿聯酋電子發票資料：發票、貸項通知單、UBL XML、Peppol 狀態與業務檔案。

Streamable HTTP可網頁執行
金融10 個工具Nov 14, 2026

Oyster MCP by usefulapi

io.usefulapi官方發布者

面向 Oyster 的遠端 MCP 伺服器，讓助理讀取團隊、休假、費用、合約與發票資料，並核准或拒絕相關申請。

Streamable HTTP可網頁執行
效率與工作流20 個工具Nov 14, 2026