R

releases.sh

Releases is a registry of product changelogs and release notes. It indexes updates from software vendors and serves them through a website, API, MCP server, and command-line tool.

4 integrations · MCP · REST · CLI

releases.sh exposes a public REST API, a public remote MCP server, and a CLI; reads are public for the network surfaces, while the CLI can log in with a Releases-issued bearer token for account-scoped operations and higher rate limits.

discovered 2mo ago
MCP servers1
REST · OpenAPI2
CLI1
Credentials
Releases API key / access tokenbearerGet token ↗

Optional for reads. Run releases login to sign in; it opens your browser and mints a personal read-only key stored for the CLI. For a pre-issued token, run releases auth login --token <token>. The REST API docs also say account endpoints accept a user API key minted via Account → API Keys on releases.sh, or an OAuth access token from an app you authorized. For CI/non-interactive use, set RELEASES_API_KEY. See the agent authentication guide and REST API auth section.

Releases API keyapi_key

Optional. Search, browse, and MCP reads work with no credential; presenting a token raises your rate-limit tier (anonymous < signed-in account < machine token) and unlocks account-scoped actions. Sign in with releases login — it opens your browser (OAuth device authorization) and mints a personal, read-only key (relu_…). Already issued a token (e.g. a write/admin relk_… key during the closed beta)? Store it with releases auth login --token <token>. The token is sent to https://api.releases.sh (and https://mcp.releases.sh) as Authorization: Bearer <token>; RELEASES_API_KEY in the environment overrides the stored credential (handy for CI).

conventions · 5/8 published

Publish these signals → /publishing