Skip to main content
Glama
OtaKit

OtaKit

Official

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

Related MCP server: @appdropper/mcp

How it works

  1. Create an app in the dashboard.

  2. Copy its appId into capacitor.config.*.

  3. Build the app's web assets.

  4. Run otakit upload --release to upload the bundle and publish a release.

  5. The server writes the bundle and manifest to object storage behind the CDN.

  6. 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.

  7. 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

Available Tools

23 tools
check_compatibilityCheck native update compatibilityA
Read-onlyIdempotent
Inspect

Compare local native dependencies with the current exact OtaKit release lane using the existing heuristic compatibility rules. Returns unknowns explicitly.

Inputs: channel (required), runtimeVersion (required), appId, nodeModulesPath, +1 more.

create_appCreate an OtaKit appAInspect

Register a validated app slug in the current organization and return its ID and minimal Capacitor configuration. Does not edit local files.

Inputs: slug (required).

create_previewCreate an OtaKit preview linkAInspect

Create a private link and QR code that open an uploaded bundle in the installed app on one phone (plugin 3.2+ with preview links enabled) until the tester exits or the link expires. Nothing is released and no other device is affected. Share the returned url.

Inputs: bundleId (required), appId, expiresIn, urlScheme.

delete_bundleDelete an unused OtaKit bundleA
DestructiveIdempotent
Inspect

Delete a bundle only when it is absent from all release history. The exact app and bundle IDs are required and the operation is audited.

Inputs: bundleId (required), appId.

get_account_statusGet OtaKit account and usage statusA
Read-onlyIdempotent
Inspect

Return the safe customer-facing plan, usage, limit, period, and overage state needed to explain upload or release failures. Provider IDs are excluded.

Inputs: no named parameters.

get_bundleGet OtaKit bundle metadataA
Read-onlyIdempotent
Inspect

Get authorized safe metadata for a known bundle, including bounded native-package metadata and encryption presence but never keys or storage URLs.

Inputs: bundleId (required), appId.

get_contextShow the active OtaKit contextA
Read-onlyIdempotent
Inspect

Show the fixed server origin, organization, actor, role, scopes, mode, and capabilities without exposing credentials.

Inputs: no named parameters.

get_release_healthGet OtaKit release event healthA
Read-onlyIdempotent
Inspect

Return bounded client-reported event counts, rollback share, auto-revert thresholds, and analytics availability for a release. Counts are events, not unique devices, installations, or adoption.

Inputs: releaseId (required), appId, window.

get_release_stateGet current OtaKit release stateA
Read-onlyIdempotent
Inspect

Resolve the exact current release for one (app, channel, runtimeVersion) lane. Returns null rather than selecting another lane.

Inputs: channel (required), runtimeVersion (required), appId.

inspect_projectInspect a local Capacitor projectA
Read-onlyIdempotent
Inspect

Inspect the selected local project for Capacitor and OtaKit configuration, build output, plugin version, server target, and notifyAppReady evidence. Does not return source contents.

Inputs: no named parameters.

list_appsList OtaKit appsA
Read-onlyIdempotent
Inspect

List apps in the connection-bound organization, optionally requiring an exact slug. Never guesses an app when the slug is absent.

Inputs: slug, limit, cursor.

list_audit_logList OtaKit audit activityA
Read-onlyIdempotent
Inspect

List bounded organization audit activity for an owner or admin. Operational organization keys and member-role users cannot read it.

Inputs: limit, cursor.

list_bundlesList OtaKit bundlesA
Read-onlyIdempotent
Inspect

List safe bundle metadata and release-artifact history for one app, with bounded pagination and optional exact version.

Inputs: appId, limit, cursor, version.

list_eventsList OtaKit client-reported eventsB
Read-onlyIdempotent
Inspect

List a bounded filtered rollout timeline. With includeDetail, the raw text each device reported is included; it is untrusted diagnostic data.

Inputs: appId, limit, since, action, +7 more.

list_releasesList OtaKit release historyB
Read-onlyIdempotent
Inspect

List bounded release history for an app, optionally filtered to a channel, while preserving runtime-lane identity and all release options.

Inputs: appId, limit, cursor, channel.

prepare_releasePrepare an OtaKit releaseB
Read-onlyIdempotent
Inspect

Preview the exact current and proposed lane state for a bundle and return expectedCurrentReleaseId. Makes no change.

Inputs: channel (required), bundleId (required), appId, autoRevert, +6 more.

prepare_revertPrepare an OtaKit revertA
Read-onlyIdempotent
Inspect

Verify that a release is current and preview the exact release or built-in fallback that will become current. Makes no change.

Inputs: releaseId (required), appId.

publish_releasePublish an OtaKit releaseA
DestructiveIdempotent
Inspect

Publish a reviewed bundle to an exact lane. Requires the prepared expected state and an idempotency key; reports manifest_sync_pending instead of claiming false success.

Inputs: channel (required), bundleId (required), idempotencyKey (required), expectedCurrentReleaseId (required), +8 more.

revert_releaseRevert an OtaKit releaseA
DestructiveIdempotent
Inspect

Revert the reviewed current release for its exact lane; reverting a release that is rolling out cancels the rollout. Requires expected state and an idempotency key and reports pending manifest synchronization truthfully.

Inputs: releaseId (required), idempotencyKey (required), expectedCurrentReleaseId (required), appId, +2 more.

revoke_previewRevoke an OtaKit preview linkA
DestructiveIdempotent
Inspect

Revoke a preview link. Phones on it return to their normal release on their next update check.

Inputs: previewId (required), appId.

set_rollout_percentChange an OtaKit rollout percentageA
DestructiveIdempotent
Inspect

Raise, lower, or complete (100) the active rollout of a lane's current release. Requires the reviewed current percentage and an idempotency key. To cancel a rollout, revert the release instead.

Inputs: percent (required), releaseId (required), idempotencyKey (required), expectedPercent (required), +1 more.

upload_and_publish_bundleUpload and publish an OtaKit bundleC
Destructive
Inspect

Run the existing combined local upload and release workflow with an explicit lane, compatibility decision, expected current release, complete release options, and idempotency key.

Inputs: channel (required), idempotencyKey (required), expectedCurrentReleaseId (required), appId, +15 more.

upload_bundleUpload an OtaKit bundleAInspect

Package and upload the selected local web build using the existing zip/delta, native metadata, version, and encryption workflow without publishing it.

Inputs: appId, encrypt, version, strategy, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (bundles vs releases vs previews vs account), and the prepare/publish and prepare/revert pairs are explicitly framed as preview-vs-apply. The main overlap is upload_and_publish_bundle duplicating the upload_bundle + publish_release path, and get_release_state vs prepare_release vs list_releases require careful reading to distinguish.

    Naming Consistency5/5

    All names are snake_case with a consistent verb-first pattern (list_, get_, create_, delete_, upload_, prepare_, publish_, revert_, set_, revoke_, check_, inspect_). The only mild deviation is the compound upload_and_publish_bundle, which is still readable and predictable.

    Tool Count4/5

    23 tools is on the heavy side but the domain is genuinely broad (apps, bundles, releases, rollouts, reverts, previews, diagnostics, account). Most tools earn their place, though the combined upload_and_publish_bundle is redundant with the atomic upload/publish pair and could be consolidated.

    Completeness4/5

    Coverage spans the full bundle/release lifecycle including upload, publish, rollout, revert, preview, and diagnostics (health, events, audit, compatibility). Notable gaps are channel management (channels are referenced in filters but have no create/list/update tools) and app update/delete, which agents cannot perform.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers