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 数据;元工具可更改你的订阅。

安装

在 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 集成