How do I install Otakit?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Otakit need an API key?

No required environment variable is listed on this record.

When was Otakit last checked?

Last checked 2026-11-11. Inspect, upload, release, monitor, and revert OtaKit Capacitor OTA updates.

Otakit MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://console.otakit.app/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.otakit-otakit https://console.otakit.app/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.otakit-otakit": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://console.otakit.app/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.12.0
License

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

OtaKit

Fully open-source, self-hostable over-the-air update framework for Capacitor apps. Release updates directly to your Capacitor app without app store reviews.

Try it for free: OtaKit.app

Self-hosting

OtaKit is hosted-first — the managed service at otakit.app runs everything for you — but the entire platform is in this repo and can run on your own infrastructure. The minimal stack is the console (a standard Next.js app), Postgres, and an S3-compatible bucket behind a CDN.

Full step-by-step guide: otakit.app/docs/self-host

How it works

Create an app in the dashboard.
Copy its appId into capacitor.config.*.
Build the app's web assets.
Run otakit upload --release to upload the bundle and publish a release.
The server writes the bundle and manifest to object storage behind the CDN.
On the next app launch or resume, the plugin fetches the manifest from the CDN, compares it to the current bundle, and downloads the new version if available.
If notifyAppReady() is called within the timeout, the new bundle is confirmed. Otherwise the plugin rolls back to the previous bundle automatically.

MCP & Agent Skills

Ask Claude Code, Codex, or VS Code to ship an update and it reads your Capacitor project, checks whether the change is safe to send over the air, uploads the build, and stops for your approval before anything reaches a device.

One command from your project directory:

npx -y @otakit/cli@latest connect

It detects your client, signs you in if needed, and prints the console, organization, project, and app it resolved — plus the exact file it will write — before writing anything. --dry-run shows the plan and writes nothing.

Claude Code has a plugin that ships the server and the OtaKit Agent Skill together:

npx -y @otakit/cli@latest login

claude plugin marketplace add OtaKit/otakit
claude plugin install otakit@otakit

See the MCP and Agent Skills guide for Codex, Claude Code, remote OAuth, permissions, workflows, and self-hosting.

Core concepts

App — the Capacitor app identified by its appId
Bundle — one uploaded web build zip with a version, hash, and size
Release — a promotion of a bundle to a channel, which publishes a manifest to the CDN
Channel — an optional release track such as staging
Runtime version — an optional native compatibility lane configured in the plugin

Packages

packages/capacitor-plugin — the runtime that lives inside the mobile app
packages/cli — CLI for uploading bundles and creating releases
packages/mcp-core — shared MCP contracts, tool catalog, and server registration
packages/site — public site, docs, contact, legal pages
packages/console — dashboard, API, auth, billing, and Prisma schema
packages/ingest — Cloudflare Worker for device event ingestion
tinybird/ — Tinybird datasources and pipes for event analytics

packages/
  capacitor-plugin/   Capacitor OTA plugin
  cli/                Upload + release CLI
  mcp-core/           Shared MCP contracts and tool catalog
  ingest/             Cloudflare Worker event ingest service
  site/               Next.js public site + docs
  console/            Next.js dashboard + API + auth + billing
tinybird/             Tinybird event analytics project
examples/
  demo-app/           Demo Capacitor app wired to the local plugin

Package docs

Local development

Node.js 20.9+, pnpm 9+
The console app (packages/console) requires Postgres and R2-compatible storage. See packages/console/.env.example.
Device event analytics optionally require the ingest service (packages/ingest) and a Tinybird workspace.
See each package README for setup details.

pnpm install
pnpm dev        # starts the console app in dev mode

License

MIT

Otakit

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Otakit?

Does Otakit need an API key?

What transport does Otakit use?

When was Otakit last checked?

Documentation

OtaKit

Self-hosting

How it works

MCP & Agent Skills

Core concepts

Packages

Package docs

Local development

License