MCP server

Run Healkite from Claude Code, Claude Desktop, Cursor or VS Code. Ask in plain language: "set up Healkite in this project", "how is production doing?", "roll back Android 1.0", "invite @alice as a viewer".

Connect

Create a key in the dashboard (API & MCP → Create MCP key). Pick the lowest role that works: Developer ships and rolls back; Viewer is read-only.

claude mcp add healkite \
  --env HEALKITE_API_URL=https://api.healkite.com \
  --env HEALKITE_TOKEN=hk_… \
  -- npx -y @healkite/mcp

Cursor (.cursor/mcp.json) and Claude Desktop:

json

{
  "mcpServers": {
    "healkite": {
      "command": "npx",
      "args": ["-y", "@healkite/mcp"],
      "env": { "HEALKITE_API_URL": "https://api.healkite.com", "HEALKITE_TOKEN": "hk_…" }
    }
  }
}

Without env vars it uses ~/.healkite/config.json from healkite login.

Tools

Area	Tools
Connect	`login`, `whoami`
Set up	`list_apps`, `create_app`, `create_channel`, `app_setup_guide`, `setup_code_signing`, `set_alerts`, `set_push_credentials`, `set_preview_scheme`
Ship	`publish_release`, `check_bundle_size`, `promote_release`, `send_release_to_devices`, `set_release_schedule`, `push_now`
Control	`set_rollout`, `control_rollout`, `set_release_enabled`, `rollback`, `maintenance_mode`
Previews	`publish_preview`, `close_preview`
Experiments	`start_experiment`, `experiment_results`, `conclude_experiment`
Observe	`channel_status`, `list_releases`, `get_release`, `recent_devices`, `device_timeline`
Team	`list_members`, `invite_member`, `set_member_role`, `remove_member`, `list_access_keys`, `create_access_key`, `revoke_access_key`

Every call runs with the key's role, so the assistant can never do more than the key allows. Destructive tools (rollback, turning releases off, maintenance mode, removals) are marked so clients ask before running them.

MCP server

#Connect

#Tools

Connect

Tools