CALL-E Integrations

The fastest path — paste this into any AI agent (Claude Code, Codex, Cursor, and more):

Install CALL-E for me: https://open.heycall-e.com/document/mcp-archive/CALL-E-installation-guide.md

Your agent handles the rest.

SDK — five lines to your first call:

import { CalleClient } from "@call-e/calle"; // pnpm add @call-e/calle

const client = new CalleClient({ apiKey: "your_api_key" });
const call = await client.calls.createAndWait({
  task: "Call +15550123456 and confirm tomorrow's 9am appointment.",
});
console.log(call.status, call.taskCompleted);

• What is CALL-E?
• Capabilities
• Get Started
  • Agent Install
  • MCP
  • SDK
  • API
• Supported Regions and Languages
• Examples
• Troubleshooting
• In Development
• Repository Structure
• Telemetry
• Development
• Community

CALL-E automates goal-driven phone tasks that scripted voice bots cannot handle.

Traditional calling platforms use prebuilt bots optimized for high-volume, repetitive scripts. CALL-E is different: you describe a goal, and CALL-E figures out how to achieve it over the phone. It handles natural conversation, adapts to unexpected responses, and returns a structured result when the call ends.

This makes CALL-E practical for tasks where a rigid script would fail — appointment confirmations, research calls, follow-ups, lead qualification.

Call lifecycle:

flowchart LR
    A["Goal + phone number"] --> B["Plan"]
    B --> C{"Details\ncomplete?"}
    C -- "Missing info" --> D["Clarify"]
    D --> B
    C -- "Confirmed" --> E["Dial"]
    E --> F["Live conversation"]
    F --> G["Structured result\n+ transcript\n+ summary"]

Goal-Driven Long Tasks — CALL-E plans a multi-step task end-to-end: it designs the calling approach, executes the calls, learns from real outcomes, and continuously improves its strategy over time. This goes beyond single calls — CALL-E learns how to achieve each phone-based goal more reliably across attempts. This feature is under active development and not yet generally available.

Choose the integration path that fits your use case:

Paste this single prompt into your agent for automatic setup:

Install CALL-E for me: https://open.heycall-e.com/document/mcp-archive/CALL-E-installation-guide.md

Works in Claude Code, Codex, Cursor, and any agent that can run shell commands. The linked guide stays up to date, so the prompt never changes.

For manual setup, expand the table below or see the full install guide.

CALL-E exposes a Streamable HTTP MCP endpoint. Any compatible MCP client can connect, authorize via OAuth, and run CALL-E with three tools.

Endpoint:

https://seleven-mcp-sg.airudder.com/mcp/openagent_oauth

Transport: Streamable HTTP

Tool flow:

sequenceDiagram
    participant Client as MCP Client
    participant CE as CALL-E
    participant Phone

    Client->>CE: plan_call(goal, phone)
    CE-->>Client: plan_id, confirm_token, ready_to_run=true
    Note over Client: User confirms intent
    Client->>CE: run_call(plan_id, confirm_token)
    CE-->>Client: run_id
    CE-)Phone: Outbound call
    Note over Client,CE: Wait ~60s, then poll while call is in progress
    loop Until terminal status
        Client->>CE: get_call_run(run_id)
        CE-->>Client: status, activity, transcript
    end

Tools:

For OAuth details, tool details, and MCP setup, see the MCP guide.

CALL-E server SDKs are available for TypeScript and Python. Use them in trusted backend services, workers, and automation systems.

Install:

# TypeScript
pnpm add @call-e/calle

# Python
pip install calle-ai

Set your API key:

export CALLE_API_KEY="calle_live_key"

Get your API key from the CALL-E dashboard.

TypeScript:

import { CalleClient } from "@call-e/calle";

const client = new CalleClient({ apiKey: process.env.CALLE_API_KEY! });

const call = await client.calls.createAndWait({
  task: "Call <E164_PHONE> and confirm whether they can attend Friday lunch.",
  resultSchema: {
    type: "object",
    required: ["can_attend"],
    properties: {
      can_attend: { type: "string", enum: ["yes", "no", "unknown"] },
    },
  },
});

console.log(call.status);
console.log(call.taskCompleted);
console.log(call.completionConfidence);
console.log(call.structuredResult);
console.log(call.evidence);

Python:

import os
from calle import CalleClient

client = CalleClient(api_key=os.environ["CALLE_API_KEY"])

call = client.calls.create_and_wait(
    task="Call <E164_PHONE> and confirm whether they can attend Friday lunch.",
    result_schema={
        "type": "object",
        "required": ["can_attend"],
        "properties": {
            "can_attend": {"type": "string", "enum": ["yes", "no", "unknown"]},
        },
    },
)

print(call["status"])
print(call["task_completed"])
print(call["structured_result"])
print(call["evidence"])

The CALL-E Developer API provides direct HTTP access for any trusted backend, worker, or workflow system.

Set credentials:

export CALLE_API_KEY="calle_live_key"
export CALLE_BASE_URL="https://api.heycall-e.com"

Endpoints:

Create a call:

curl "$CALLE_BASE_URL/v1/calls" \
  --request POST \
  --header "Authorization: Bearer $CALLE_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: wf_123_friday_lunch" \
  --data '{
    "task": "Call each recipient and ask whether they can attend Friday lunch.",
    "recipients": [
      { "phones": ["<E164_PHONE>"],
        "region": "US",
        "locale": "en-US"
      }
    ],
    "result_schema": {
      "type": "object",
      "required": ["completed_count"],
      "properties": {
        "completed_count": {
          "type": "integer"
        }
      }
    },
    "recipient_result_schema": {
      "type": "object",
      "required": ["can_attend"],
      "properties": {
        "can_attend": {
          "type": "string",
          "enum": ["yes", "no", "unknown"]
        }
      }
    },
    "metadata": {
      "workflow_run_id": "wf_123"
    },
    "webhook_url": "https://example.com/calle/webhook"
  }'

Read a result:

curl "$CALLE_BASE_URL/v1/calls/call_123" \
  --header "Authorization: Bearer $CALLE_API_KEY"

Terminal call result:

{
  "status": "completed",
  "task_completed": true,
  "completion_confidence": { "score": 0.92, "label": "high" },
  "evidence": ["The recipient said they can attend Friday lunch."],
  "structured_result": { "completed_count": 1 },
  "recipients": [
    {
      "structured_result": { "can_attend": "yes" },
      "attempts": [
        {
          "transcript_turns": [
            { "offset_seconds": 0, "speaker": "bot", "text": "Hi, I am calling about Friday lunch." },
            { "offset_seconds": 4, "speaker": "user", "text": "Yes, I can attend." }
          ]
        }
      ]
    }
  ]
}

For authentication, webhooks, and the full reference, see the API docs.

Use these country codes with the SDK and API recipient settings.

Notes

• Local means calls are placed using a local phone line for the destination country or region.
• International means calls are currently placed using CALL-E's international phone numbers and are primarily intended for testing. For production use with a local phone number, contact the CALL-E team to enable a local line for the destination country.

Runnable demos are in examples/:

These are starting-point demos, not the canonical SDK or API contract.

If installation, authentication, or MCP tool verification fails, see the CALL-E troubleshooting guide.

Common issues covered:

• Cursor sandbox network restrictions — CONNECT tunnel failed, response 403 means the Cursor agent shell is blocking outbound HTTPS. Fix: switch Cursor Auto-Run Mode to Run Everything (Unsandboxed) in Cursor Settings → Agents.
• calle auth login failures — fetch failures, login errors, and token cache issues.
• Missing MCP tools — how to confirm that plan_call, run_call, and get_call_run are available after install.

This is a multi-ecosystem integration monorepo. Each integration has its own package and marketplace entry point.

For layout rules and marketplace naming conventions, see docs/agent-integration-layout.md.

The calle CLI sends best-effort usage telemetry to help diagnose installation, authentication, and tool availability issues.

What is collected: anonymous installation ID, CLI version, integration source (e.g. claude/claude_code_plugin/<version>), command stage, outcome, error type, and server host hash.

What is never collected: phone numbers, call goals, OAuth tokens, broker login URLs, transcripts, or contact data.

Opt out with any of:

DO_NOT_TRACK=1 calle auth status
CALLE_TELEMETRY=0 calle auth status
calle auth status --no-telemetry

Broker and MCP requests still create service-side security, audit, and operational logs required to run calls.

Requires Node >=22 and pnpm >=10.18.3, Changesets, and GitHub Actions.

pnpm install
pnpm check
pnpm test
pnpm pack:dry-run

pnpm --filter @call-e/core check
pnpm --filter @call-e/core test
pnpm --filter @call-e/cli check
pnpm --filter @call-e/cli test
pnpm --filter @call-e/codex-plugin check
pnpm --filter @call-e/codex-plugin test
pnpm --filter @call-e/claude-plugin check
pnpm --filter @call-e/claude-plugin test
pnpm --filter @call-e/cursor-plugin check
pnpm --filter @call-e/cursor-plugin test
pnpm --filter @call-e/openclaw-cli-skill check
pnpm --filter @call-e/openclaw-cli-skill test
pnpm --filter @call-e/skills-sh-skill check
pnpm --filter @call-e/skills-sh-skill test
pnpm run check:examples

For user-visible package changes, add a changeset. The release workflow publishes changed @call-e/* packages to npm and maintains the @call-e/codex-plugin@latest and @call-e/claude-plugin@latest install aliases.

See CONTRIBUTING.md for pull request guidelines.

• Website: heycall-e.com
• Docs: docs.heycall-e.com
• Discord: discord.gg/6AbXUzUV8w