otakit — Claude Code MCP server for Capacitor OTA releases
Wires your agent into OtaKit so it can inspect a project, push a build, publish a release and roll it back. Useful when you ship OTA updates to a Capacitor app.
claude mcp add --transport http otakit https://console.otakit.app/mcpWhat otakit does
OtaKit is an open-source framework for delivering over-the-air updates to Capacitor apps. This MCP server exposes the console to your coding agent: it reads the project, decides if the build can go out over the air at all, uploads it, and pauses for your approval before anything lands on a device.
Two ways to connect. Remote over HTTP at https://console.otakit.app/mcp, or locally through npx -y @otakit/cli, which runs the CLI as a stdio process and needs Node.js plus npm access. Claude users can take a plugin that bundles the server with the OtaKit Agent Skill. Everyone else can run npx -y @otakit/cli@latest connect from the project directory — it detects the client and shows which file it intends to rewrite. Add --dry-run to see the plan without writing.
The server works with OtaKit objects: an app identified by appId, a bundle, a release, a channel such as staging, and a runtime version. Nothing uploads without an authenticated console session, so sign in first. Self-hosted installs live at your own address; the minimal stack is a Next.js console, Postgres and an S3-compatible bucket behind a CDN.
What it helps with
- upload a fresh Capacitor web build and promote it to a channel
- check whether a given change is safe to ship over the air
- list bundles and releases for an app
- roll back a release that broke on devices
- watch device events after a rollout
Example prompts for the agent
- Connect otakit and list the releases for this
appId - Upload the current build and release it to the
stagingchannel - Revert the last release back to the previous bundle
How to install otakit
1Platform CLI: remote server
claude mcp add --transport http otakit https://console.otakit.app/mcp2Platform CLI
claude mcp add otakit -- npx -y @otakit/cli1Platform CLI: remote server
codex mcp add otakit --url https://console.otakit.app/mcp2Platform CLI
codex mcp add otakit -- npx -y @otakit/cliConfig file
{
"mcpServers": {
"otakit": {
"url": "https://console.otakit.app/mcp"
}
}
}{
"mcpServers": {
"otakit": {
"command": "npx",
"args": [
"-y",
"@otakit/cli"
]
}
}
}Config file
{
"servers": {
"otakit": {
"type": "http",
"url": "https://console.otakit.app/mcp"
}
}
}{
"servers": {
"otakit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@otakit/cli"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http otakit https://console.otakit.app/mcp2Platform CLI
gemini mcp add otakit npx -y @otakit/cliStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about otakit
How do I install otakit in Claude Code?
Through the plugin marketplace: run claude plugin marketplace add OtaKit/otakit, then claude plugin install otakit@otakit. Sign in first with npx -y @otakit/cli@latest login.
What does otakit do?
It hands your agent OtaKit tooling: inspect a Capacitor project, upload a build, publish a release, monitor updates and revert them. The agent asks for approval before a release reaches a device.
Do I need an OtaKit account?
Yes, the server talks to the OtaKit console, so an authenticated session is required. On a self-hosted setup, point the client at your own address instead of https://console.otakit.app/mcp.
