FleetDeckDocs

MCP 0.1.1

MCP setup

36 tools over Streamable HTTP (stateless POST) or stdio. Exact tool schemas come from the published SDK descriptor.

Connect Claude with FleetDeck sign-in

  1. In Claude, open Settings → Connectors → Add custom connector.
  2. Name it FleetDeck and enter https://fleetdeck.co/api/mcp. Leave OAuth client ID and secret blank.
  3. Click Connect. Sign in on FleetDeck, choose phones and permissions, then click Allow access.
  4. Return to Claude, enable FleetDeck tools and ask it to list your phones.

No API key needs to be copied. The connection appears in your dashboard’s MCP & API key list with “(OAuth)” in its name. Revoke it there to stop access, including refreshed tokens. New phones are not added automatically.

OAuth lifecycle

FleetDeck supports public-client authorization code flow with S256 PKCE, dynamic registration and rotating refresh tokens. Discovery is available at /.well-known/oauth-protected-resource/api/mcp and /.well-known/oauth-authorization-server. The issuer is https://fleetdeck.co; the resource and access-token audience are https://fleetdeck.co/api/mcp.

EndpointRequestResult
POST /oauth/registerJSON redirect_uris, client_name; public auth method none201 client_id and registered metadata
GET /oauth/authorizeresponse_type=code, client_id, exact redirect_uri, code_challenge, code_challenge_method=S256, state, scope, resourceFleetDeck login and explicit phone consent
POST /oauth/tokenForm grant_type=authorization_code, code, client_id, redirect_uri, code_verifier, resourceBearer access token; refresh token with offline_access
POST /oauth/tokenForm grant_type=refresh_token, client_id, refresh_token, resourceNew access and refresh token pair
POST /oauth/revokeForm client_id and token200; revokes the connection

Request scopes mcp offline_access. Codes expire after five minutes and are single-use. Access tokens last up to one hour; the connection and refresh tokens expire after 90 days. Refresh tokens rotate on every use. Reusing an already exchanged code or refresh token revokes that connection. Clients must serialize refreshes and reconnect if a token response is lost. Tokens cannot grant more phones or permissions than the user approved.

For invalid_grant, reconnect rather than replaying an old code or refresh token. For invalid_target, use the exact resource URL. For invalid_client_metadata, use HTTPS callbacks or HTTP loopback callbacks and token_endpoint_auth_method=none. Callback URLs must match registration exactly. If consent expires or the signed-in user changes, restart from Claude. Active plan and device access checks still apply when tools run.

Connect with an API key

bash
codex mcp add fleetdeck --url https://fleetdeck.co/api/mcp --bearer-token-env-var FLEETDECK_API_KEY

Endpoint: https://fleetdeck.co/api/mcp. API keys remain supported. The endpoint uses stateless Streamable HTTP POST with Content-Type: application/json and Accept: application/json, text/event-stream. Let an MCP SDK initialize and negotiate the protocol before tools/list and tools/call. Responses use JSON; notifications return HTTP 202. Unauthenticated requests return 401 with OAuth discovery; authenticated GET and DELETE return 405. Persistent SSE subscriptions are not offered. OAuth access tokens are scoped to MCP; use an API key for the separate REST API or CLI.

Local stdio

json
{
  "mcpServers": {
    "fleetdeck": {
      "command": "fleetdeck",
      "args": [
        "mcp"
      ],
      "env": {
        "FLEETDECK_API_KEY": "<resolve from your secret manager>"
      }
    }
  }
}

Use stdio when the client cannot send Bearer authentication to a remote MCP endpoint. Resolve the illustrative key value through the client’s secret mechanism; environment interpolation in JSON is client-specific.

Response contract

Every tool returns a JSON text block. Screenshot image entries become MCP image blocks and are removed from the duplicated JSON result. Tool exceptions and terminal failed, unknown or cancelled actions set isError: true.

The published MCP descriptor includes exact JSON Schema and annotations for all tools.

Safe workflow

  1. Call fleetdeck_devices, then fleetdeck_capabilities.
  2. Acquire one session and preserve its expiry.
  3. Use fresh screen evidence and a stable requestId for every intended action.
  4. On uncertainty, call fleetdeck_action_status before any new input.
  5. Release the session in cleanup.