HotCodePush
Book a demo
Login

OTA update MCP server

The OTA update MCP server for Claude Code, Cursor, Codex and ChatGPT: release, pause, roll back and read adoption from a chat. Free for 1,000 MAU.

Get started Read the docs

Connect

Connect, sign in, ask

One command registers the server, the browser approves it once, and the agent asks and acts from then on.

Claude Code — my-app

$ claude mcp add --transport http hotcodepush "https://mcp.hotcodepush.com/mcp"
Added HTTP MCP server hotcodepush with URL: https://mcp.hotcodepush.com/mcp to local config
$ /mcp
hotcodepush: needs authentication, the browser opens the consent page
✓ hotcodepush connected
▸ you, to the agent
Pause the production rollout of My App and tell me how many devices already have it.
▸ list_organizations · list_apps · list_channels · list_releases · pause_release
Paused release #43 on production. 980 of 1,204 devices applied it, 953 confirmed it, 0 failed.
Devices on #43 keep it and nobody new gets it until you resume. Say resume or roll back when you have decided.

Toolsets

What your agent can do

One toolset per resource, the same nouns the CLI has. The docs toolset needs no account at all.

Toolset What the agent does with it Sign-in
app Lists, gets, creates and updates apps, and deletes and transfers one Browser or token
audience Previews the devices a release would reach, and reads the ones an existing release reaches Browser or token
audit-log Lists who did what to which object, when and from where Browser or token
bundle Lists and gets bundles with their deltas, and deletes one Browser or token
channel Lists, gets, creates, updates, deletes, pauses and resumes channels Browser or token
docs Searches the documentation and reads a page whole None
invitation Lists, sends and withdraws invitations Browser
member Lists and gets members, changes a role and removes a member Browser or token
organization Lists and gets organizations, and creates, updates and deletes one Browser or token
release Lists, gets, creates, updates, pauses, resumes and revokes releases, and rolls a channel back Browser or token
sso-provider Reads, verifies and removes the single sign-on provider Browser
statistics Reads the fleet, the update statistics and the usage of an app Browser or token
telemetry-export Reads and tests the telemetry export, lists its deliveries and redelivers one Browser
webhook Lists, gets, creates, updates, deletes and tests webhooks Browser or token
webhook-delivery Lists a webhook's deliveries and redelivers one Browser or token

Last verified 2026-11-07.

Every tool with its parameters is in the docs. Tools by toolset

In practice

Built for the agent's day

The questions a release day asks, answered in the chat you already have open.

  • Release and roll back

    Create a release from a bundle or promote one from staging, widen or pause the rollout, and roll a channel back to the last good release with one request.

    Rollbacks

  • Read adoption and failures

    Ask how many devices run the latest release, how many confirmed it and how many failed with which reason, per channel or per release, as the console shows.

    Update analytics

  • Find why devices skipped

    Ask why devices skip a release. The agent reads the failure reasons per release, looks each code up in the docs and names the fix to apply.

    Troubleshooting

FAQ

MCP server questions

Any client that connects to a remote MCP server over HTTP. ChatGPT, Claude Code, Claude Desktop, Codex, Cursor and VS Code have a setup each in the docs, and every other client takes the URL and one of the two sign-ins. Set up a client
Both work. A client with a browser signs in once on the consent page and refreshes on its own. A script, a pipeline or a client without a browser sends an API token, the same one the REST API takes. Sign-in and tokens
The docs search. An agent searches the documentation and reads a page whole without an account. Everything that touches your apps starts after the sign-in. The docs toolset
Only if you let it. Tools that cannot be undone carry the destructive mark, so the client asks you before running them, and the ones that change who acts or spend money need the browser sign-in, never a token. Reads, writes and destructive tools
No. Uploading stays with the CLI, in your pipeline or on your machine. The server lists what was uploaded and releases it, promotes it between channels, pauses and rolls back. The bundle command

Connect once. Ask from then on.

Free for 1,000 MAU. No credit card.

Get started Book a demo

Questions? Join our Discord or contact us.