Cockpit API has three distinct integration surfaces. Choose the surface that matches the job before sending credentials.
#When to use Cockpit
Use Cockpit to coordinate coding agents on the account owner's computer, send work to an existing mission and follow deliveries, reviews and tests. Use remote MCP for a cloud agent and the local API for an agent already running on the Cockpit computer. The website does not run projects or provide a public coding sandbox.
#Public website API
The OpenAPI 3.1.1 specification describes integration discovery, desktop license activation and app-login exchange. Each operation has a unique operationId, description and typed schemas for agent tools. GET /api returns discovery links without authentication.
POST /api/v1/license accepts JSON with key, deviceId and optional label and appVersion. The account owner generates the key in the dashboard. This key does not authorize the local mission API. New trials require a card confirmed in Stripe before activation. Obtain the owner's permission before activating a computer. The limit is 120 requests per IP per hour.
POST /api/v1/app-login accepts the secret from a login initiated by the desktop application and an optional label. Poll every two seconds for up to ten minutes. A 202 response means browser approval is pending; 200 returns the new key once. Keep keys and secrets out of logs.
Errors from this API contain error, code, message and resolution. On 429, honor Retry-After. OAuth keeps its protocol error format and MCP keeps JSON-RPC errors.
#Cockpit remote MCP server
Connect your MCP client to https://cockpit.vep.sh/mcp using Streamable HTTP. The endpoint accepts POST and OPTIONS; it does not provide a GET SSE stream. Follow OAuth discovery at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. The client uses PKCE and the account owner authorizes a specific computer and mission.
After authorization, send Authorization: Bearer <access_token>, initialize the MCP connection, discover the actual tools using tools/list and invoke tools through tools/call. Tool definitions come from the connected desktop: do not assume tool names. The desktop must remain open and online with its relay enabled and mission shared. The limit is 240 requests per grant per minute. Mission permissions still apply.
Read the connection walkthrough. This page documents the server; /mcp itself is a protocol endpoint and returns 405 to GET.
#Local API and CLI
The local API and WebSocket run on the desktop server, usually http://127.0.0.1:4000. Fetch /api/openapi.json there for its specification and use the token configured by the account owner. Never send that token to the public website.
The server commands describe the CLI in a compiled source checkout. This guide does not offer an official Cockpit package published on npm, PyPI or Homebrew. Provider CLIs are separate tools.
#Self-serve onboarding
Create an account, confirm your card and plan in Stripe, download Cockpit and generate your license key in the dashboard. The free trial lasts 7 days from card confirmation. After the trial, the chosen subscription is charged automatically unless cancelled. AI provider accounts and costs are separate. Try automation in a disposable local project; there is no separate hosted sandbox or shared public API key.