Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Release notes and changelogs from across the web, indexed for agents. Also via CLI and REST API.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://agents.releases.sh/mcpRun this in your terminal
claude mcp add --transport http releases https://agents.releases.sh/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"releases": {
"url": "https://agents.releases.sh/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"releases": {
"type": "http",
"url": "https://agents.releases.sh/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://agents.releases.sh/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.
searchUnified search across the registry and release content. Returns up to four sections — organizations, catalog entries (products + standalone sources folded into one list), curated collections (cross-org playlists), and releases with CHANGELOG chunks interleaved by relevance. Use `
get_latest_releasesGet the most recent releases, optionally filtered by product or organization. Excludes prereleases (canaries / alphas / betas / RCs) by default — pass `include_prereleases: true` to include them. Cursor-paginated: pass `limit` for slice size (default 10), `cursor` to continue fro
list_catalogList catalog entries — products and standalone sources combined into one list with an `entryType: 'product' | 'source'` discriminator per row. Orgs that group multiple sources under a product (e.g. Vercel → Next.js, Turborepo) surface those products; orgs with a single source tha
get_catalog_entryDetail for a single catalog entry — accepts a prod_ id, src_ id, or an org-scoped coordinate in the form orgSlug/slug (e.g. 'vercel/nextjs' or 'vercel/next-js'). Returns the union of product / source detail fields depending on the entry kind. Source entries list tracked CHANGELOG
list_organizationsList all indexed organizations, optionally filtered. Paginated: defaults to 50 entries per page; pass `page: 2` for the next slice. Orgs with zero indexed releases are hidden by default (curator-stub noise); set `include_empty: true` to see them.
get_organizationGet detailed information about a single organization — accounts, tags, sources, products, aliases. When an AI-generated overview exists the response includes a short preview; pass `include_overview: true` to inline the full briefing (with a stale warning if the content is older t
lookup_domainResolve a domain to the org or product that owns it. The domain is normalized first (scheme, `www.`, path, and trailing slash stripped, lowercased), so `https://vercel.com/about` and `vercel.com` both look up the same row. Returns the matching org (with primary-vs-alias distincti
list_collectionsList curated collections — named cross-org playlists (e.g. 'Frontier AI Labs') independent of the fixed category taxonomy. Use `get_collection` for a collection's full member list, or `get_collection_releases` for the interleaved cross-org release feed. Paginated: defaults to 50
get_collectionDetail for a single collection — name, description, and the ordered list of member organizations. Hidden / on-demand orgs never leak through; only publicly visible orgs appear in the member list.
get_collection_releasesInterleaved cross-org release feed for a collection — same shape as `get_latest_releases` but scoped to the collection's member orgs. Cursor-paginated: pass `limit` for slice size (default 20), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind:
get_releaseFetch the full content of a single release by id. Release ids are returned by search or get_latest_releases — pass them here to read the whole entry (e.g. to quote a specific Next.js release note). Accepts the full rel_ form or the bare 21-char nanoid. Cite `URL:` (the original s
followFollow an organization or a product so it appears in your personalized feed (`get_personalized_feed`). Following an organization implicitly includes all of its products. Requires a signed-in user (a `relu_` user key or an OAuth token). `entity` is a typed id — an `org_…` id or a
unfollowStop following an organization or product. Requires a signed-in user. `entity` is an `org_…` or `prod_…` id. Idempotent: unfollowing something you don't follow is a no-op.
list_followsList the organizations and products you follow (newest first). Requires a signed-in user.
get_personalized_feedYour personalized release feed — recent releases from the organizations and products you follow, newest first. Requires a signed-in user. Same item shape as `get_latest_releases`, scoped to your follows. Each item prints `URL:` (the original source — cite that) before `Web:` (the
list_webhooksList your outbound release webhooks, personal or workspace. Requires a signed-in user (a `relu_` user key or an OAuth token). With no `workspace`, lists your personal webhooks (`GET /v1/me/webhooks`) and includes a short list of your workspaces (id, slug, role) so you can target
manage_webhookCreate, update, delete, test, or rotate the signing key of an outbound release webhook — personal or workspace. Requires a signed-in user. This tool sends requests to an external URL you supply and can delete or disable delivery, so treat it as a write. Pass `workspace` (an id or
whats_changedGiven a package and a `from`/`to` version, return the changelog entries between them — `(from, to]`, from exclusive, to inclusive — with summaries and breaking-change verdicts. One call instead of reading N changelog pages to plan an upgrade. `package` is a tracked source slug or
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified against the domain releases.sh (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 335 ms (HTTP 200)
No sign-in needed
Read 18 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.15.2) reached the registry 36 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Release Notes Index
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 → · Use it · What's in this repo · Develop
This repo is the backend for releases.sh (API · MCP · web · ingest) and the source of the command-line tool .
"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 lives in apps/cli/ and ships from this repo (npm + Homebrew).
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, and in the Claude connector directory for Claude on the web, desktop, and mobile:
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 vendor
REST 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 # reader skills — search, MCP, release analysis
npx skills add buildinternet/releases --skill creating-releases-json
On 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
/plugin install releases@releases
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 apps/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.
Every org page carries an AI-maintained overview and exports as JSON, Markdown, or Atom.
| Path | What |
|---|---|
apps/api/ | Hono API on Cloudflare D1 — the authoritative data plane |
apps/mcp/ | Remote MCP server at agents.releases.sh (alias mcp.releases.sh) |
apps/webhooks/ | Signs + delivers release.created events (HMAC-SHA256, retry/DLQ) — docs |
apps/web/ | Next.js frontend, deploys on Vercel |
packages/ | Shared code — core + api-types publish to npm; the rest are private workspaces |
.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 | apps/api/, apps/mcp/, apps/webhooks/, apps/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 | .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 run 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.
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 run test # full test suite, secret-free bun run dev:api # API worker on local D1 bun run dev:web # Next.js frontend
bootstrap 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.
Apache-2.0. The published npm packages (releases-core, api-types) and the Claude Code plugin (plugins/claude/releases) are deliberately MIT for maximum reuse.