Release Radar MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.41.2Updated Nov 14, 2026

Correlate GitHub releases with Sentry issues and PagerDuty incidents.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableDeveloper Tools Security & Monitoring

Server details

Identifier: io.usefulapi/release-radar
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 29, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to usefulapi.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Frelease-radar.svg)](https://sourceweft.com/mcp/io.usefulapi%2Frelease-radar?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted MCP server that correlates GitHub deployments, Sentry issues and PagerDuty on-call data into incident snapshots and handoff briefings.

What you can do: Combine GitHub deploys, Sentry issues and PagerDuty on-call into a "what broke since last deploy" view
Get a right-now incident snapshot of unresolved Sentry issues, active PagerDuty incidents and current on-call
Prepare a start-of-shift on-call handoff briefing across all three services
Fetch low-level building blocks: latest GitHub deployment or release for a repo, and recent unresolved Sentry issues
Check monthly usage, request a missing feature, upgrade or cancel the subscription
When to use it: Useful for on-call engineers and teams that want an assistant to answer "what broke since the last deploy" or "what is on fire right now" without switching between GitHub, Sentry and PagerDuty.
Requirements: Remote streamable HTTP endpoint; no local install. Sign-in is via OAuth with Release Radar credentials entered on first connect; no API key or Authorization header goes in the client config. The server needs access to your GitHub, Sentry and PagerDuty data, and each service degrades independently if its credentials are missing.

Before you install

Free plan is limited to 50 tool calls per month; paid plans cost $9/month (Pro) or $39/month (Pro+), and upgrades return a Stripe Checkout link that charges immediately, with no refund for the current period on cancellation. Release Radar credentials are stored per user, and the server reads data from GitHub, Sentry and PagerDuty on your behalf. Meta tools can change your subscription.

Installation

In SourceWeft

Open Release Radar MCP by usefulapi in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Frelease-radar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

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

Tool	Type	What it does
`release_radar_whats_broken_since_last_deploy`	read	What's broken since the last deploy?
`release_radar_incident_snapshot`	read	Current incident snapshot
`release_radar_oncall_handoff`	read	On-call handoff briefing
`release_radar_github_latest_deploy`	read	Latest GitHub deploy/release
`release_radar_sentry_recent_issues`	read	Recent unresolved Sentry issues
`release_radar_usage_status`	meta	Usage status (free-tier meter)
`release_radar_request_feature`	meta	Request a missing feature
`release_radar_upgrade`	meta	Upgrade to Pro or Pro+
`release_radar_cancel_subscription`	meta	Cancel 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

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

Source: servers/release-radar/README.md at commit f22f848

Tools

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).

Parametersreporequiredownerrequiredenvironmentsentry_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.

Parametersurgencysentry_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.

Parametersreporequiredownerrequiredsentry_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.

Parametersreporequiredownerrequiredenvironment

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.

ParameterslimitenvironmentstatsPeriodsentry_project

Version history

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

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Productivity & Workflow20 toolsNov 14, 2026

Plan	Price	Limit
Free	$0	50 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