@call-e/cli

@call-e/cli ships the calle command.

The CLI is not an OAuth server and not an MCP server. It is a local wrapper that uses the CALL-E broker API to complete browser-based login, cache the OAuth token locally, print MCP client configuration, and provide call workflow shortcuts for terminal-based agents.

For install and authentication steps, see docs/install/cli.md.

Commands

calle auth login
calle auth login --start-only --no-browser-open
calle auth status
calle auth logout
calle mcp config
calle mcp tools
calle mcp call plan_call --args-json '{"to_phones":["+15551234567"],"goal":"Confirm the appointment"}'
calle call plan --to-phone +15551234567 --goal "Confirm the appointment"
calle call start --to-phone +15551234567 --goal "Confirm the appointment"
calle call run --plan-id <plan_id> --confirm-token <confirm_token>
calle call status --run-id <run_id>

Defaults:

• Base URL: https://seleven-mcp-sg.airudder.com
• MCP channel: openagent_oauth
• MCP server URL: <baseUrl>/mcp/openagent_oauth
• Broker API: <baseUrl>/api/v1/openagent-auth/*
• Token cache: ~/.calle-mcp/cli

calle auth login opens the brokered login URL, polls the broker session, exchanges the authorized session, and stores the token in a private local cache. The token is not printed to stdout.

calle auth login --start-only --no-browser-open creates or reuses a brokered login session and returns JSON with login_url and assistant_hint.message without polling for completion. This is intended for agent integrations that need to show the authorization link before continuing.

calle mcp config prints a JSON MCP client config:

calle mcp config --base-url https://seleven-mcp-sg.airudder.com

Example output:

{
  "mcpServers": {
    "calle": {
      "type": "http",
      "url": "https://seleven-mcp-sg.airudder.com/mcp/openagent_oauth"
    }
  }
}

For LLM clients that can connect to MCP directly, prefer calle mcp config and let the client use the MCP tool schemas. For terminal-based agents such as Codex, the calle call ... commands provide shortcuts over the same remote MCP tools.

For agent-facing outbound calls, prefer calle call start. It performs planning and execution inside one CLI invocation and does not print execution confirmation data.

Successful command stdout is JSON except --help. Some top-level or local failures may print plain stderr. Access tokens are read from the local cache and are never printed.

Options

See docs/cli-reference.md for the canonical command and option reference, including defaults, required arguments, advanced configuration, and per-command examples.

Telemetry / Usage Data

The CLI sends best-effort usage telemetry to the configured CALL-E service at <base-url>/api/ui-telemetry/track to help diagnose installation, authentication, MCP tool availability, and drop-off before a first plan_call reaches the server.

Collected fields include an anonymous installation ID stored under the CLI cache root, CLI version, integration source, command stage, outcome, error type, and server host/hash. The payload does not include phone numbers, call goals, OAuth tokens, broker login URLs, full argument JSON, transcripts, or contact data.

Disable CLI telemetry with DO_NOT_TRACK=1, CALLE_TELEMETRY=0, or --no-telemetry:

CALLE_TELEMETRY=0 calle auth status
calle mcp tools --no-telemetry

Broker and MCP requests still create service-side security, audit, and business operation logs needed to authenticate users and run calls.

Development

pnpm --filter @call-e/cli test
pnpm --filter @call-e/cli check
pnpm --filter @call-e/cli pack:dry-run

For offline smoke checks and live OAuth/MCP validation, see docs/cli-verification.md.