An agent-friendly API for product changelogs. A unified registry via CLI, API, or MCP.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
The latest product releases, indexed for agents.
A registry of release notes from across the web โ pulled from vendor changelogs, normalized into one schema, summarized, and queryable from your terminal, your code, or any MCP client. Readable by you and your agent.
releases.sh ย ยทย Docs ย ยทย CLI repo โ ย ยทย Use it ย ยทย What's in this repo ย ยทย Develop
This repo is the backend for releases.sh (API ยท MCP ยท web ยท ingest). The user-facing command-line tool lives in its own repo โ buildinternet/releases-cli.
"What changed?" is a question agents and developers ask constantly โ before an upgrade, after an incident, when a tool suddenly behaves differently. The answer is scattered across GitHub releases, RSS feeds, changelog pages, and blog posts in a hundred different formats.
Releases collects those into one registry. It watches hundreds of sources across the vendors developers actually depend on, and for every release stores the original content plus an AI-generated title, summary, and breaking-change classification. Each organization gets a maintained overview of what it shipped recently. The web page a human reads and the JSON an agent fetches are the same content.
This repo is the source of the canonical deployment at releases.sh: the API worker (the authoritative data plane), the MCP server, the web frontend, and the ingest pipeline + agent harness that keep the registry fresh. The user-facing CLI ships separately from buildinternet/releases-cli (npm + Homebrew).
No account or API key needed for reads โ all four surfaces are public.
MCP โ hosted at mcp.releases.sh, listed in the
MCP Registry
as sh.releases/mcp:
CLI โ one-off via npx, or brew install buildinternet/tap/releases:
REST API โ public GET endpoints on api.releases.sh, spec at
/v1/openapi.json:
Agent skills โ auto-triggering playbooks, installable into any agent (Claude Code / Codex / Cursor / OpenCode) without checking out anything. Start with the reader skills โ search, MCP lookups, and release analysis โ which is what almost everyone wants:
On Claude Code, the CLI repo also installs as a plugin โ the reader skills plus
a bundled MCP connection and a /releases command:
Running or maintaining the registry itself? This repo also ships
operator skills (source onboarding, parsing, bulk maintenance) โ most need
an admin key: npx skills add buildinternet/releases. See
releases.sh/docs/skills.
Docs โ user-facing documentation is served from the web app at
releases.sh/docs (source in
web/src/content/docs/):
installation ยท
skills ยท
REST API ยท
MCP ยท
webhooks ยท
listing your product.
Agents consuming the product start from releases.sh/llms.txt; the MCP tool catalog and auth model are also covered in docs/architecture/mcp.md. Creating a free account unlocks higher rate limits (mint an API key at releases.sh/account), plus follows, personalized feeds, webhooks, and email digests.
| Path | What |
|---|---|
workers/api/ | Hono API on Cloudflare D1 โ the authoritative data plane |
workers/mcp/ | Remote MCP server at mcp.releases.sh |
workers/discovery/ | Durable-Object agent-session orchestrator |
workers/webhooks/ | Signs + delivers release.created events (HMAC-SHA256, retry/DLQ) โ docs |
web/ | Next.js frontend, deploys on Vercel |
packages/ | Shared code โ core + api-types publish to npm; the rest are private workspaces |
src/agent/ | Managed-agents discovery + worker harness (prompt builder + shared types) |
.claude/ | Claude Code config โ skills/ (canonical skill home), agents/, commands/, workflows/ |
How it fits together:
packages/adapters/). The crawler signs outbound fetches (RFC 9421) as a Cloudflare Verified Bot.This repo has four kinds of code:
| Area | Paths | What to know |
|---|---|---|
| Product surfaces | workers/api/, workers/mcp/, workers/webhooks/, web/ | The API worker is the data plane. Web, MCP, CLI, and webhooks read from or route through it. |
| Shared packages | packages/core/, packages/api-types/, private packages/* | core owns schema and pure helpers; api-types owns wire shapes. Change these first when shared contracts move. |
| Hosted operations | workers/discovery/, managed-agents/, .claude/skills/, .claude/workflows/ | These power the canonical releases.sh ingest and operator loop. Some paths need hosted credentials, but local work does not. |
| Historical context | docs/architecture/, docs/plans/, docs/superpowers/ | Architecture docs are maintained references. Plans and specs are point-in-time design history. |
For normal contributions, start with bun run bootstrap, bun run check, and
bun test. You do not need production Cloudflare, Anthropic, Vercel, email, or
Firecrawl access to work on the core loop. If you are trying to fork or
self-host the full service, read
deploy-coupling.md.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/releases)<a href="https://allmcps.com/mcp/releases"><img src="https://allmcps.com/api/badge/releases?style=directory" alt="Releases on AllMCPs" /></a>