Releases

Official16 toolsLive

by buildinternet · TypeScript

An agent-friendly API for product changelogs. A unified registry via CLI, API, or MCP.

sh.releases/mcp (Model Context Protocol Server)

sh.releases/mcp provides an agent-friendly API for product changelogs. It acts as a unified registry of release notes pulled from vendor changelogs, normalized into a single schema, summarized, and made queryable from the terminal, code, or an MCP client.

🛠️ Key Features

Unified registry of release notes
Pulls changelogs from vendor sources
Normalizes release data into one schema
Summarizes and indexes results for query
Accessible via CLI, API, or MCP

🚀 Use Cases

Querying the latest product releases from an MCP client
Using release notes for agent workflows
Terminal or code-based release-note retrieval
Roadmap planning based on changelog summaries

⚡ Developer Benefits

One normalized schema for changelog data
Consistent access methods via CLI, API, and MCP
Queryable, agent-readable release notes

⚠️ Limitations

The provided description does not specify authentication, rate limits, or update frequency.

Topics

agent-skillsapimcprelease-noteschangelogsregistryagentscliroadmap-planning

Captured live from the server via tools/list.

search

Unified 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 `type` to narrow the surfaces you want and skip the expensive paths. For example, pass `type: ['catalog']` to look up a known entity by name (fast, registry-only); pass `type: ['releases']` when you only care about release content and want to avoid entity lookups. Omit `type` to search all four. Collections surface via two paths: a direct match on the collection's name/description (lexical in every mode, plus a vector match in hybrid/semantic mode) and a member rollup that includes every collection containing one of the matched orgs. Member rollups carry a list of result-set org slugs that triggered the rollup so a UI can render an "includes X" hint. Use `entity` (product slug / prod_ id OR source slug / src_ id) to scope release results to one catalog entry. Product identifiers expand to every source under the product. Use `organization` to scope to a whole org. Release retrieval defaults to hybrid (FTS5 + semantic vectors fused via RRF); it silently degrades to lexical when vector infra is unavailable and flags the result.

Parameters13

query	string	required	Search query
type	array	optional	Which sections to return. Omit to return all four. Use to skip expensive paths — e.g. ['catalog'] for registry-only lookups, ['releases'] for pure release search, ['collections'] for a quick playlist lookup.
organization	string	optional	Scope release results to sources belonging to this organization. Accepts an org_ id, slug, or registered domain.
domain	string	optional	Scope to the org owning this domain. Input is normalized (scheme/path/www stripped, lowercased), so `https://vercel.com/` and `vercel.com` both work. Falls back to a 'no match' message when the domain isn't owned by anything indexed. Use this instead of `organization` when you have a URL-shaped input.
entity	string	optional	Scope release results to one catalog entry. Accepts a prod_ id (expands to every source under the product), a src_ id, or an org-scoped coordinate in the form orgSlug/slug (e.g. 'vercel/nextjs'). Bare slugs without an org prefix are not accepted.
product	string	optional	Scope release results to a specific product's sources. Accepts a prod_ id or an org-scoped coordinate in the form orgSlug/productSlug (e.g. 'vercel/next-js'). Bare slugs without an org prefix are not accepted. When both `entity` and `product` are supplied, `entity` takes precedence. The resolved product coordinate is echoed on `_meta.search.product`.
limit	number	optional	Max results per section (default 20)
mode	string	optional	Release-retrieval strategy. 'hybrid' (default) fuses FTS + vector results. 'lexical' is legacy FTS only. 'semantic' is vectors only. Falls back to lexical if vector infra is unavailable.
include_coverage	boolean	optional	Include releases grouped as coverage of another (e.g. marketing posts that re-announce a platform release). Defaults to false so each underlying launch appears once.
include_empty	boolean	optional	Include orgs with zero indexed releases in the `orgs` section. Default false — empty orgs are stubs and surface as noise. Scoping by `domain` ignores this and always returns the resolved org.
kind	string	optional	Filter to a specific source/product kind. Release hits resolve through `source.kind ?? product.kind`; catalog hits filter on the row's own kind. The orgs and collections sections are unaffected; changelog chunk hits are unaffected.
since	string	optional	Keep only release hits published at or after this bound. Accepts an ISO date/datetime (`2026-01-01`) or relative shorthand (`90d`, `4w`, `6m`, `2y`). Filters `published_at`; undated releases are dropped. Only the releases section is affected — great for capability-discovery queries like 'who added X in the last 90 days'.
until	string	optional	Keep only release hits published at or before this bound. Same input formats as `since`.

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query"
    },
    "type": {
      "description": "Which sections to return. Omit to return all four. Use to skip expensive paths — e.g. ['catalog'] for registry-only lookups, ['releases'] for pure release search, ['collections'] for a quick playlist lookup.",
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "orgs",
          "catalog",
          "releases",
          "collections"
        ]
      }
    },
    "organization": {
      "description": "Scope release results to sources belonging to this organization. Accepts an org_ id, slug, or registered domain.",
      "type": "string"
    },
    "domain": {
      "description": "Scope to the org owning this domain. Input is normalized (scheme/path/www stripped, lowercased), so `https://vercel.com/` and `vercel.com` both work. Falls back to a 'no match' message when the domain isn't owned by anything indexed. Use this instead of `organization` when you have a URL-shaped input.",
      "type": "string"
    },
    "entity": {
      "description": "Scope release results to one catalog entry. Accepts a prod_ id (expands to every source under the product), a src_ id, or an org-scoped coordinate in the form orgSlug/slug (e.g. 'vercel/nextjs'). Bare slugs without an org prefix are not accepted.",
      "type": "string"
    },
    "product": {
      "description": "Scope release results to a specific product's sources. Accepts a prod_ id or an org-scoped coordinate in the form orgSlug/productSlug (e.g. 'vercel/next-js'). Bare slugs without an org prefix are not accepted. When both `entity` and `product` are supplied, `entity` takes precedence. The resolved product coordinate is echoed on `_meta.search.product`.",
      "type": "string"
    },
    "limit": {
      "description": "Max results per section (default 20)",
      "type": "number"
    },
    "mode": {
      "description": "Release-retrieval strategy. 'hybrid' (default) fuses FTS + vector results. 'lexical' is legacy FTS only. 'semantic' is vectors only. Falls back to lexical if vector infra is unavailable.",
      "type": "string",
      "enum": [
        "lexical",
        "semantic",
        "hybrid"
      ]
    },
    "include_coverage": {
      "description": "Include releases grouped as coverage of another (e.g. marketing posts that re-announce a platform release). Defaults to false so each underlying launch appears once.",
      "type": "boolean"
    },
    "include_empty": {
      "description": "Include orgs with zero indexed releases in the `orgs` section. Default false — empty orgs are stubs and surface as noise. Scoping by `domain` ignores this and always returns the resolved org.",
      "type": "boolean"
    },
    "kind": {
      "description": "Filter to a specific source/product kind. Release hits resolve through `source.kind ?? product.kind`; catalog hits filter on the row's own kind. The orgs and collections sections are unaffected; changelog chunk hits are unaffected.",
      "type": "string",
      "enum": [
        "platform",
        "sdk",
        "mobile",
        "desktop",
        "docs",
        "integration",
        "tool"
      ]
    },
    "since": {
      "description": "Keep only release hits published at or after this bound. Accepts an ISO date/datetime (`2026-01-01`) or relative shorthand (`90d`, `4w`, `6m`, `2y`). Filters `published_at`; undated releases are dropped. Only the releases section is affected — great for capability-discovery queries like 'who added X in the last 90 days'.",
      "type": "string"
    },
    "until": {
      "description": "Keep only release hits published at or before this bound. Same input formats as `since`.",
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_latest_releases

Get 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 from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts — a release added between calls won't shift the slice.

Parameters11

product	string	optional	Filter to a product's cross-source release feed. Accepts a prod_ id (expands to ALL sources under the product), a src_ id (single source), or an org-scoped coordinate in the form orgSlug/productSlug (e.g. 'vercel/next-js'). Bare slugs without an org prefix are not accepted. Mirrors the REST ?product= expansion — multi-source products (e.g. Next.js with GitHub releases + blog) return releases from all of their sources interleaved.
organization	string	optional	Filter to sources belonging to this organization. Accepts an org_ id, slug, or registered domain.
type	string	optional	Filter by release type: 'feature' for individual releases, 'rollup' for seasonal/quarterly catch-all posts. Omit to include both.
kind	string	optional	Filter to releases from sources of a specific kind. Resolves through `source.kind ?? product.kind`, so an SDK repo with no own kind still matches its product's kind. Omit to include all kinds.
limit	integer	optional	Slice size (1–200). Defaults to 10.
cursor	string	optional	Opaque continuation token from a prior call's `_meta.pagination.nextCursor`. Pass to fetch the next slice. Stale cursors are silently ignored — the call returns a fresh head of the feed.
include_coverage	boolean	optional	Include releases grouped as coverage of another (e.g. marketing posts that re-announce a platform release). Defaults to false so each underlying launch appears once.
include_prereleases	boolean	optional	Include prerelease tags (alphas, betas, RCs, canaries). Defaults to false so the feed matches the public web view.
since	string	optional	Keep only releases published at or after this bound. Accepts an ISO date/datetime (`2026-01-01`) or relative shorthand (`90d`, `4w`, `6m`, `2y`). Filters `published_at`; undated releases are dropped.
until	string	optional	Keep only releases published at or before this bound. Same input formats as `since`.
minImportance	integer	optional	Only include releases with an AI-scored `importance` >= this value (1-5; 5=landmark, 1=housekeeping). Releases with no score (unscored) are excluded when this is set. Mirrors the REST `?minImportance=` filter.

Raw schema

{
  "type": "object",
  "properties": {
    "product": {
      "description": "Filter to a product's cross-source release feed. Accepts a prod_ id (expands to ALL sources under the product), a src_ id (single source), or an org-scoped coordinate in the form orgSlug/productSlug (e.g. 'vercel/next-js'). Bare slugs without an org prefix are not accepted. Mirrors the REST ?product= expansion — multi-source products (e.g. Next.js with GitHub releases + blog) return releases from all of their sources interleaved.",
      "type": "string"
    },
    "organization": {
      "description": "Filter to sources belonging to this organization. Accepts an org_ id, slug, or registered domain.",
      "type": "string"
    },
    "type": {
      "description": "Filter by release type: 'feature' for individual releases, 'rollup' for seasonal/quarterly catch-all posts. Omit to include both.",
      "type": "string",
      "enum": [
        "feature",
        "rollup"
      ]
    },
    "kind": {
      "description": "Filter to releases from sources of a specific kind. Resolves through `source.kind ?? product.kind`, so an SDK repo with no own kind still matches its product's kind. Omit to include all kinds.",
      "type": "string",
      "enum": [
        "platform",
        "sdk",
        "mobile",
        "desktop",
        "docs",
        "integration",
        "tool"
      ]
    },
    "limit": {
      "description": "Slice size (1–200). Defaults to 10.",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "cursor": {
      "description": "Opaque continuation token from a prior call's `_meta.pagination.nextCursor`. Pass to fetch the next slice. Stale cursors are silently ignored — the call returns a fresh head of the feed.",
      "type": "string"
    },
    "include_coverage": {
      "description": "Include releases grouped as coverage of another (e.g. marketing posts that re-announce a platform release). Defaults to false so each underlying launch appears once.",
      "type": "boolean"
    },
    "include_prereleases": {
      "description": "Include prerelease tags (alphas, betas, RCs, canaries). Defaults to false so the feed matches the public web view.",
      "type": "boolean"
    },
    "since": {
      "description": "Keep only releases published at or after this bound. Accepts an ISO date/datetime (`2026-01-01`) or relative shorthand (`90d`, `4w`, `6m`, `2y`). Filters `published_at`; undated releases are dropped.",
      "type": "string"
    },
    "until": {
      "description": "Keep only releases published at or before this bound. Same input formats as `since`.",
      "type": "string"
    },
    "minImportance": {
      "description": "Only include releases with an AI-scored `importance` >= this value (1-5; 5=landmark, 1=housekeeping). Releases with no score (unscored) are excluded when this is set. Mirrors the REST `?minImportance=` filter.",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

list_catalog

List 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 that isn't part of a product surface it directly as an `entryType: 'source'` entry. Either shape is a reasonable thing to pass to `search(entity: ...)`. Paginated: defaults to 50 entries per page. Pass `page: 2` for the next slice. The footer surfaces the total when more pages exist.

Parameters4

organization	string	optional	Organization to scope to. Accepts an org_ id, slug, domain, or name.
kind	string	optional	Filter to catalog entries of a specific kind. Matches each row's own kind (a product's kind, or a standalone source's kind) — no source→product inheritance on this catalog surface. Omit to include all kinds.
page	integer	optional	1-based page number. Defaults to 1.
limit	integer	optional	Entries per page (1–200). Defaults to 50.

Raw schema

{
  "type": "object",
  "properties": {
    "organization": {
      "description": "Organization to scope to. Accepts an org_ id, slug, domain, or name.",
      "type": "string"
    },
    "kind": {
      "description": "Filter to catalog entries of a specific kind. Matches each row's own kind (a product's kind, or a standalone source's kind) — no source→product inheritance on this catalog surface. Omit to include all kinds.",
      "type": "string",
      "enum": [
        "platform",
        "sdk",
        "mobile",
        "desktop",
        "docs",
        "integration",
        "tool"
      ]
    },
    "page": {
      "description": "1-based page number. Defaults to 1.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "limit": {
      "description": "Entries per page (1–200). Defaults to 50.",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_catalog_entry

Detail 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 files by path and byte size. Pass `include_changelog: true` to inline the root CHANGELOG, or `changelog_path` / `changelog_offset` / `changelog_limit` / `changelog_tokens` to embed a specific file or slice — heading-aligned, supports per-package files in monorepos (e.g. `packages/next/CHANGELOG.md`), and emits `totalTokens` / `sliceTokens` for LLM context budgeting. Files over 1MB are flagged as truncated so you know the tail is missing.

Parameters6

identifier	string	required	Catalog entry identifier: prod_ id, src_ id, or org-scoped coordinate orgSlug/slug (e.g. 'vercel/nextjs'). Bare slugs without an org prefix are not accepted.
include_changelog	boolean	optional	When true, inline the root tracked CHANGELOG for a source-kind entry. Ignored for products.
changelog_path	string	optional	Specific CHANGELOG path for a source-kind entry (e.g. 'packages/next/CHANGELOG.md'). Passing this implies include_changelog.
changelog_offset	number	optional	Character offset into the selected CHANGELOG. Snapped forward to the next heading unless 0. Passing this implies include_changelog.
changelog_limit	number	optional	Target slice size in characters. Slice ends at a heading boundary. Defaults to 40000 when slicing without a token budget. Passing this implies include_changelog.
changelog_tokens	number	optional	Target slice size in tokens (cl100k_base). Takes precedence over changelog_limit. Recommended brackets: 2000, 5000, 10000, 20000. Passing this implies include_changelog.

Raw schema

{
  "type": "object",
  "properties": {
    "identifier": {
      "type": "string",
      "description": "Catalog entry identifier: prod_ id, src_ id, or org-scoped coordinate orgSlug/slug (e.g. 'vercel/nextjs'). Bare slugs without an org prefix are not accepted."
    },
    "include_changelog": {
      "description": "When true, inline the root tracked CHANGELOG for a source-kind entry. Ignored for products.",
      "type": "boolean"
    },
    "changelog_path": {
      "description": "Specific CHANGELOG path for a source-kind entry (e.g. 'packages/next/CHANGELOG.md'). Passing this implies include_changelog.",
      "type": "string"
    },
    "changelog_offset": {
      "description": "Character offset into the selected CHANGELOG. Snapped forward to the next heading unless 0. Passing this implies include_changelog.",
      "type": "number"
    },
    "changelog_limit": {
      "description": "Target slice size in characters. Slice ends at a heading boundary. Defaults to 40000 when slicing without a token budget. Passing this implies include_changelog.",
      "type": "number"
    },
    "changelog_tokens": {
      "description": "Target slice size in tokens (cl100k_base). Takes precedence over changelog_limit. Recommended brackets: 2000, 5000, 10000, 20000. Passing this implies include_changelog.",
      "type": "number"
    }
  },
  "required": [
    "identifier"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

list_organizations

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

Parameters6

query	string	optional	Search across org name, slug, domain, and account handles
platform	string	optional	Filter to orgs with an account on this platform
include_empty	boolean	optional	Include orgs with zero indexed releases. Default false — empty orgs are stubs from in-flight discovery or broken parsers and surface as noise on the public catalog.
category	string	optional	Filter to a single category slug (e.g. `ai`, `devops`). Aliases (e.g. `e-commerce`) resolve to their canonical category (`commerce`); unknown values are ignored (unfiltered).
page	integer	optional	1-based page number. Defaults to 1.
limit	integer	optional	Entries per page (1–200). Defaults to 50.

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Search across org name, slug, domain, and account handles",
      "type": "string"
    },
    "platform": {
      "description": "Filter to orgs with an account on this platform",
      "type": "string"
    },
    "include_empty": {
      "description": "Include orgs with zero indexed releases. Default false — empty orgs are stubs from in-flight discovery or broken parsers and surface as noise on the public catalog.",
      "type": "boolean"
    },
    "category": {
      "description": "Filter to a single category slug (e.g. `ai`, `devops`). Aliases (e.g. `e-commerce`) resolve to their canonical category (`commerce`); unknown values are ignored (unfiltered).",
      "type": "string"
    },
    "page": {
      "description": "1-based page number. Defaults to 1.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "limit": {
      "description": "Entries per page (1–200). Defaults to 50.",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_organization

Get 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 than 30 days since last write).

Parameters2

identifier	string	required	Organization identifier. Accepts an org_ id, slug, domain, name, or account handle.
include_overview	boolean	optional	When true, inline the full AI-generated overview instead of the default first-paragraph preview.

Raw schema

{
  "type": "object",
  "properties": {
    "identifier": {
      "type": "string",
      "description": "Organization identifier. Accepts an org_ id, slug, domain, name, or account handle."
    },
    "include_overview": {
      "description": "When true, inline the full AI-generated overview instead of the default first-paragraph preview.",
      "type": "boolean"
    }
  },
  "required": [
    "identifier"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

lookup_domain

Resolve 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 distinction) and any products whose alias targets the same domain. Pure resolution — does not probe the domain or materialize anything; unknown domains surface a 'no match' message. Use `lookup_domain` when you have a URL-shaped input; use `get_organization` when you already have a slug or id.

Parameters1

domain

string

required

Domain to resolve. Any URL-shaped form is accepted; the server normalizes it.

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to resolve. Any URL-shaped form is accepted; the server normalizes it."
    }
  },
  "required": [
    "domain"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

list_collections

List 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 entries per page; pass `page: 2` for the next slice.

Parameters2

page	integer	optional	1-based page number. Defaults to 1.
limit	integer	optional	Entries per page (1–200). Defaults to 50.

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "description": "1-based page number. Defaults to 1.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "limit": {
      "description": "Entries per page (1–200). Defaults to 50.",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_collection

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

Parameters1

slug

string

required

Collection slug (e.g. 'frontier-ai-labs').

Raw schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Collection slug (e.g. 'frontier-ai-labs')."
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_collection_releases

Interleaved 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: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts.

Parameters4

slug	string	required	Collection slug (e.g. 'frontier-ai-labs').
limit	integer	optional	Slice size (1–200). Defaults to 20.
cursor	string	optional	Opaque continuation token from a prior call's `_meta.pagination.nextCursor`. Stale cursors are silently ignored — the call returns a fresh head of the feed.
include_prereleases	boolean	optional	Include prerelease tags (alphas, betas, RCs). Defaults to false so the feed matches the public web view.

Raw schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Collection slug (e.g. 'frontier-ai-labs')."
    },
    "limit": {
      "description": "Slice size (1–200). Defaults to 20.",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "cursor": {
      "description": "Opaque continuation token from a prior call's `_meta.pagination.nextCursor`. Stale cursors are silently ignored — the call returns a fresh head of the feed.",
      "type": "string"
    },
    "include_prereleases": {
      "description": "Include prerelease tags (alphas, betas, RCs). Defaults to false so the feed matches the public web view.",
      "type": "boolean"
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_release

Fetch 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_<nanoid> form or the bare 21-char nanoid.

Parameters1

string

required

Release id — 'rel_<nanoid>' or a bare 21-char nanoid

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Release id — 'rel_<nanoid>' or a bare 21-char nanoid"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

follow

Follow 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 `prod_…` id — as returned by `search`, `get_organization`, or `get_catalog_entry`. Idempotent: following something you already follow is a no-op.

Parameters1

entity

string

required

Entity to follow — an `org_…` or `prod_…` id (from search / get_* results).

Raw schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Entity to follow — an `org_…` or `prod_…` id (from search / get_* results)."
    }
  },
  "required": [
    "entity"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

unfollow

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

Parameters1

entity

string

required

Entity to unfollow — an `org_…` or `prod_…` id.

Raw schema

{
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Entity to unfollow — an `org_…` or `prod_…` id."
    }
  },
  "required": [
    "entity"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

list_follows

List the organizations and products you follow (newest first). Requires a signed-in user.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

get_personalized_feed

Your 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. Cursor-paginated: pass `cursor` from a prior response's `_meta.pagination.nextCursor` and optional `limit` (1–100, default 30).

Parameters2

cursor	string	optional	Opaque cursor from a previous page's `_meta.pagination.nextCursor`.
limit	integer	optional	Entries per page (1–100). Defaults to 30.

Raw schema

{
  "type": "object",
  "properties": {
    "cursor": {
      "description": "Opaque cursor from a previous page's `_meta.pagination.nextCursor`.",
      "type": "string"
    },
    "limit": {
      "description": "Entries per page (1–100). Defaults to 30.",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

whats_changed

Given 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 a GitHub `owner/repo` coordinate (set `ecosystem: "github"` for a bare coordinate). Reads already-indexed releases only. If the package isn't in the catalog you'll get a clear 'not tracked' answer (npm/PyPI names may not be mapped to a source yet).

Parameters5

package	string	required	Package identifier — a source slug or a GitHub "owner/repo" coordinate.
from	string	required	Version you're upgrading FROM (exclusive).
to	string	required	Version you're upgrading TO (inclusive).
ecosystem	string	optional	Optional resolution hint; "github" enables matching a bare owner/repo.
minImportance	integer	optional	Only include entries with an AI-scored `importance` >= this value (1-5; 5=landmark, 1=housekeeping). Entries with no score (unscored) are excluded when this is set.

Raw schema

{
  "type": "object",
  "properties": {
    "package": {
      "type": "string",
      "description": "Package identifier — a source slug or a GitHub \"owner/repo\" coordinate."
    },
    "from": {
      "type": "string",
      "description": "Version you're upgrading FROM (exclusive)."
    },
    "to": {
      "type": "string",
      "description": "Version you're upgrading TO (inclusive)."
    },
    "ecosystem": {
      "description": "Optional resolution hint; \"github\" enables matching a bare owner/repo.",
      "type": "string",
      "enum": [
        "npm",
        "pypi",
        "github"
      ]
    },
    "minImportance": {
      "description": "Only include entries with an AI-scored `importance` >= this value (1-5; 5=landmark, 1=housekeeping). Entries with no score (unscored) are excluded when this is set.",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    }
  },
  "required": [
    "package",
    "from",
    "to"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

README.md11 KBView on GitHub

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

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:

bash

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:

bash

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:

bash

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:

bash

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-json

On Claude Code, the CLI repo also installs as a plugin — the reader skills plus a bundled MCP connection and a /releases command:

code

/plugin marketplace add buildinternet/releases-cli
/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.

An organization page: AI-maintained overview of recent releases, source list, and JSON/Markdown/Atom export

_{Every org page carries an AI-maintained overview and exports as JSON, Markdown, or Atom.}

What's in this repo

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:

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.

Contributor mental model

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.

Local development

Prerequisites: Bun. No external accounts needed for the core loop:

bash

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.

License

Apache-2.0. The published npm packages (releases-core, api-types) are deliberately MIT for maximum reuse.

Install

Tools (16)

searchget_latest_releaseslist_catalogget_catalog_entrylist_organizationsget_organizationlookup_domainlist_collections

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://agents.releases.sh/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://agents.releases.sh/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

sh.releases/mcp (Model Context Protocol Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

search

get_latest_releases

list_catalog

get_catalog_entry

list_organizations

get_organization

lookup_domain

list_collections

get_collection

get_collection_releases

get_release

follow

unfollow

list_follows

get_personalized_feed

whats_changed

Release Notes Index

What is this?

Use it

What's in this repo

Contributor mental model

Local development

License

Install

Remote endpoint

Related servers