Ask your agent what changed.

releasedapp is an MCP server. Add it to the agent you already code with, sign in with GitHub once when it asks, and your dependency watchlist becomes something it can read and update for you.

Setup

One URL for every agent: https://releasedapp.org/mcp. There is no API key. The first time the agent connects, it opens a browser tab where you sign in with GitHub and approve — after that it keeps a token of its own, scoped to your account, that you can revoke from Settings at any time.

Claude Code from the Claude Code docs

claude mcp add --transport http releasedapp https://releasedapp.org/mcp

Then, inside a session, run /mcp and pick releasedapp to complete the sign-in.

Cursor from the Cursor docs

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "releasedapp": { "url": "https://releasedapp.org/mcp" }
  }
}

Cursor shows a “Needs login” state on the server; clicking it opens the sign-in.

Codex from the Codex docs

codex mcp add releasedapp --url https://releasedapp.org/mcp
codex mcp login releasedapp

Or add [mcp_servers.releasedapp] with url = "https://releasedapp.org/mcp" to ~/.codex/config.toml, then codex mcp login releasedapp.

Antigravity untested

In the IDE: menu → MCP Servers → Manage MCP Servers → View raw config. Antigravity uses serverUrl rather than url:

{
  "mcpServers": {
    "releasedapp": { "serverUrl": "https://releasedapp.org/mcp" }
  }
}

We have not been able to verify Antigravity's sign-in against this server yet. If it asks you for a client id instead of opening a sign-in tab, tell us — that is a one-line fix on our side.

Anything else

Any client that speaks MCP over Streamable HTTP with OAuth 2.1 works: the server publishes standard discovery documents and registers clients dynamically. The reference walk-through is scripts/mcp-smoke.mjs in the repository — every step of the flow, with no client library, so a misbehaving agent can be compared against it.

What the agent can do

Exactly what you can do in the dashboard, and nothing more. Every tool acts on your watchlist alone.

whats_newReleases newer than the versions you are on, across everything you watch. The daily digest, on demand. Empty means quiet — that is the point.
list_packagesYour watchlist: the version you are on, the latest known, days since it shipped, muted or not.
import_manifestSend a package.json, pyproject.toml, requirements.txt, Cargo.toml, composer.json, Gemfile, pubspec.yaml, mix.exs or .csproj. Direct dependencies join the watchlist with their pinned versions; re-sending after an upgrade moves the pins. Lockfiles are not accepted.
mute_packageKeep watching, but leave it out of what's-new and the digest.
remove_packageStop watching.

Things to try

“Send my package.json to releasedapp.” · “What changed in my dependencies since I pinned them?” · “Anything with a major bump I should read the changelog for?” · “I upgraded fastapi — re-send the manifest.”

Email is optional

By default nothing is sent. The agent is how you find out, when you ask. If you would rather be told, turn on the email digest in Settings — it goes out once a day and only on days something you watch actually shipped.