Releases MCP Server
Integrates with GitHub Releases to ingest and index release notes from GitHub repositories, allowing search and retrieval of release information across projects.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Releases MCP ServerWhat's new from Anthropic?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
What is this?
"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.
Release Notes Index 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).
Related MCP server: Claude Synergy
Use it
No account or API key needed for reads — all four surfaces are public.
MCP — hosted at agents.releases.sh/mcp (mcp.releases.sh/mcp still
works), listed in the
MCP Registry
as sh.releases/mcp:
claude mcp add --transport http releases https://agents.releases.sh/mcp # Claude Code
codex mcp add releases --url https://agents.releases.sh/mcp # Codex
npx -y mcp-remote https://agents.releases.sh/mcp # stdio bridge (VS Code, Zed, …)CLI — one-off via npx, or brew install buildinternet/tap/releases:
npx @buildinternet/releases get anthropic # what did Anthropic ship lately?
npx @buildinternet/releases search "MCP" # search across every vendorREST API — public GET endpoints on api.releases.sh, spec at
/v1/openapi.json:
curl "https://api.releases.sh/v1/releases/latest?limit=5"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:
npx skills add buildinternet/releases-cli # reader skills — search, MCP, release analysis
# just the skill that writes a releases.json manifest for your own product
npx skills add buildinternet/releases --skill creating-releases-jsonOn Claude Code, the CLI repo also installs as a plugin — the reader skills plus
a bundled MCP connection and a /releases command:
/plugin marketplace add buildinternet/releases-cli
/plugin install releases@releasesRunning 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.
What's in this repo
Path | What |
| Hono API on Cloudflare D1 — the authoritative data plane |
| Remote MCP server at |
| Durable-Object agent-session orchestrator |
| Signs + delivers |
| Next.js frontend, deploys on Vercel |
| Shared code — |
| Managed-agents discovery + worker harness (prompt builder + shared types) |
| Claude Code config — |
How it fits together:
Storage — Cloudflare D1 (FTS5 + Vectorize). The API worker is the sole data plane.
Ingest — adapters for GitHub Releases, RSS/Atom/JSON feeds, and a browser-rendering fallback for feed-less pages (
packages/adapters/). The crawler signs outbound fetches (RFC 9421) as a Cloudflare Verified Bot.AI — changelog parsing, summarization, grouping, and org overviews run in the API worker as direct Anthropic SDK calls.
Agents — discovery + worker run as Anthropic-hosted managed agents; definitions auto-deploy on merge when their source changes.
Contributor mental model
This repo has four kinds of code:
Area | Paths | What to know |
Product surfaces |
| The API worker is the data plane. Web, MCP, CLI, and webhooks read from or route through it. |
Shared packages |
|
|
Hosted operations |
| These power the canonical releases.sh ingest and operator loop. Some paths need hosted credentials, but local work does not. |
Historical context |
| 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.
Per-package detail and project conventions live in AGENTS.md — the agent entry point for working in this repo. Architecture deep-dives are in docs/architecture/, with a reader's guide at docs/README.md.
Local development
Prerequisites: Bun. No external accounts needed for the core loop:
bun run bootstrap # one-command setup: tooling, deps, env files, local D1
bun run doctor # diagnose the setup — reports what's missing and how to fix it
bun run check # lint + type-check + format (the CI gate)
bun test # full test suite, secret-free
bun run dev:api # API worker on local D1
bun run dev:web # Next.js frontendbootstrap is idempotent (safe to re-run; never overwrites your env files or
wipes the local DB) and doctor is read-only. Prefer the manual steps? They're
bun install, copy each *.example env file, then bun run db:reset:local.
AI passes, scrape fetches, and semantic search take your own keys
(ANTHROPIC_API_KEY, Cloudflare Browser Rendering, VOYAGE_API_KEY) and
degrade gracefully without them. Setup detail, environment variables, testing,
deployment, and the full no-accounts / bring-your-own-keys / hosted-only
breakdown live in CONTRIBUTING.md.
License
Apache-2.0. The published npm packages
(releases-core, api-types) are
deliberately MIT for maximum reuse.
This server cannot be deployed
Maintenance
Related MCP Connectors
The only News based AI MCP your agents will ever need — custom categories, global regions, and time-scoped results in one tool. We use multi-vector & sparse-hybrid search to search through thousands of articles across the world to find the exact news you're looking for.
Make your knowledge agent-ready. One MCP endpoint, 5 connectors, 3 search modes.
Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.
Registry of MCP servers, agent skills and plugins: search, filter, comments, likes, publish.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceTracks and manages code changes from Git repositories, generates documentation automatically, and provides AI agents with intelligent access to service documentation through MCP server integration with feature mapping and search capabilities.815MIT
- AlicenseNot gradedqualityAmaintenanceProvides a local, queryable mirror of changelogs from Anthropic and related AI dev tools, enabling agents to discover cross-product workflows and sync updates via MCP.14MIT
- AlicenseAqualityDmaintenanceTracks latest versions and breaking changes for popular SDKs, enabling agents to check version updates and potential breaking changes efficiently.431Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that checks whether a vendor API or SDK is active, deprecated, or sunset, using a curated dataset. Enables agents to verify deprecation status before upgrade/maintenance work.164MIT