ReleaseRocket
MCP server
The ReleaseRocket MCP server lets a coding agent (Claude Code, Cursor, VS Code) list your releases, read generated content including blog MDX, and, with the right key scope, create, generate, and publish. It is a thin layer over the public REST API and uses the same project API key. ReleaseRocket never holds a write token to your repo; your agent writes files with your own permissions.
Endpoint
| MCP server | https://mcp.releaserocket.io/mcp |
|---|---|
| REST API | https://api.releaserocket.io/v1 |
The transport is streamable HTTP. Authentication is a project API key sent as a bearer token in the Authorization header; there is no OAuth flow. Keys are created by project admins under Settings, then API keys, inside the app.
Connect with Claude Code
claude mcp add --transport http releaserocket https://mcp.releaserocket.io/mcp \
--header "Authorization: Bearer rr_xxxxxxxx..."Replace rr_xxxxxxxx... with a real key. A read key is enough to list releases and pull content; a full key is needed to publish. Configs for Cursor and VS Code are in the MCP connect guide.
Tools
The tools an agent sees are filtered by the scope of its key. A read key never sees the write or publish tools.
| Tool | What it does | Scope |
|---|---|---|
| list_releases | List releases, filter by status | read |
| get_release | Release detail plus its changelog | read |
| get_release_content | One channel's output (blog, social, email, chat, web) | read |
| create_release | Create a draft release from a commit range | write |
| generate_release_content | Generate channel content for a release | write |
| publish_release | Publish to channels | full |
Docs
- MCP connect guide (Claude Code, Cursor, and VS Code configs)
- API keys (Create and revoke keys, choose a scope)
- API reference (The REST endpoints behind the tools)
- Limits and errors (Rate limit buckets and error shapes)
- Developers overview (Base URLs, authentication, and scopes)