Skip to content

CallRail MCP connector

The CallRail connector brings your tracked calls, trackers, companies, tags, form submissions and text threads into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about them and update them within their own CallRail access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect CallRail to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect CallRail once

  1. Open Connections, choose Add connection, and pick CallRail.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a CallRail API key. One person generates a token in CallRail and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

callrail
CallRail
Allium
Amplitude
Artie
Botify
DoiT
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

CallRail MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

CallRail MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

CallRail MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect CallRail to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with CallRail through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Marketing

    See which campaigns drove today's calls

    Ask for this morning's calls grouped by tracker and source, and find out which landing page or ad the caller looked at before dialing.

  • Sales

    Catch up on a lead after the call

    Pull the call, its recording and the pages the caller visited beforehand, then tag it as a qualified lead without opening CallRail.

  • Client services

    Report every client company's calls monthly

    List each company in your CallRail account with its call volume, top trackers and form submissions, ready to paste into a client update.

  • Marketing

    Set up a tracker for a new campaign

    Describe the campaign and have a new tracker created and tagged so the calls it brings in are separated from day one.

  • Operations

    Tag and update calls in bulk

    Find every untagged call from last week and apply the right tags and notes across all of them in one pass.

  • Support

    Review form submissions and text threads

    Read through the form submissions and SMS threads that came in overnight, and spot the ones nobody has answered yet.

Try asking

  • “Which trackers drove the most calls this week?”
  • “Summarize yesterday's calls for Acme Dental and tag the new leads.”
  • “Show form submissions from the spring campaign landing page.”

See all 59 CallRail tools below

AI tools

CallRail tools for your AI agents

59 tools are ready to call through Elaichi's MCP endpoint the moment you connect CallRail, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting CallRail gets you

6 screens from the product, each doing one job for your CallRail account.

The agent

Ask about CallRail calls in plain language.

Live calls, trackers and form submissions answer back, no report to build first.

  • calls
  • trackers
  • companies
  • form submissions

Ask Elaichi to work across your apps.

Which trackers drove the most calls this week?

Summarize yesterday's calls for Acme Dental and tag the new leads.

Show form submissions from the spring campaign landing page.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Use CallRail from any MCP client.

Claude, ChatGPT and Cursor connect through one org endpoint, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

59 CallRail tools, no code to write.

Calls, trackers, companies, tags, form submissions and SMS threads, ready the moment you connect.

  • List all CallRail calls
  • CallRail calls list page views
  • CallRail calls get recording
  • Create a CallRail call
ElaichiTools
Tool Action Description
List all CallRail calls List List calls in a CallRail account, filterable by date range, direction, company, tracker, and tags. Returns: id, answered, business_phone_number, customer_city, customer_country, customer_name, customer_phone_number, customer_state, direction, duration, recording, recording_duration, start_time, tracking_phone_number, voicemail, agent_email, lead_status, note, tags, source, campaign, medium,…. Required: account_id.
CallRail calls list page views List List the web page views from the visitor session that generated a CallRail call. Returns page view records: page_url, referrer_url, created_at. Required: call_id, account_id.
CallRail calls get recording Get Get the recording for a CallRail call by id. Returns: url, page, per_page, total_pages, total_records. Required: call_id, account_id.
Create a CallRail call Create Create an outbound call in CallRail. Returns the created call record: id, direction, customer_phone_number, tracking_phone_number, duration, start_time, recording. Required: account_id, caller_id, customer_phone_number, business_phone_number.
Get single CallRail call by ID Get Get details for a single call in CallRail by id. Returns: id, answered, business_phone_number, customer_city, customer_country, customer_name, customer_phone_number, customer_state, direction, duration, recording, recording_duration, recording_player, start_time, tracking_phone_number, voicemail, agent_email, milestones, keywords_spotted. Required: id, account_id.

Toolboxes

Every team gets its own CallRail toolbox.

Marketing gets trackers, sales gets calls, client services gets companies, each scoped separately.

  • Marketing
  • Sales
  • Client services
  • Support
ElaichiToolboxes
Name Source template Tools Created

Marketing toolbox

CallRail · trackers and campaign calls

CallRail starter 18 Mar 4, 2026

Sales toolbox

CallRail · calls, recordings and lead tags

— 9 Mar 2, 2026

Client services toolbox

CallRail · companies and client reporting

— 24 Feb 27, 2026

Support toolbox

CallRail · form submissions and SMS threads

CallRail starter 6 Feb 19, 2026

Operations toolbox

CallRail · tags and bulk updates

— 31 Jan 30, 2026

Leadership toolbox

CallRail · call volume across companies

— 12 Jan 22, 2026

Shared connections

Teammates work in CallRail without the key.

One person connects, shares with teams, and nobody else ever sees the API key.

  • Marketing
  • Sales
  • Client services
  • Support
ElaichiConnections
Connection Scope Status Access
CA

CallRail (Marketing)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
CA

CallRail (Sales)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
CA

CallRail (Client services)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
CA

CallRail (Support)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
CA

CallRail (Agency accounts)

Connected by Clara Nowak

Personal • Active Not shared
CA

CallRail (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Know who touched every CallRail record.

When, who, what happened and which call or tracker, in an append-only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

CallRail Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

CallRail Calls Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

CallRail Calls List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns CallRail calls into digests.

Calls are fetched, grouped by tracker, drafted, approved by a person, then posted back.

CallRail digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch calls

    CallRail

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    CallRail

    Queued

Collections and dashboards

CallRail call volume, computed without a model.

Four metrics, 14 days of calls created and a team breakdown, refreshed on schedule.

CallRail health

Refreshed 4 minutes ago · every 15 minutes · from the calls collection

Live

Calls

1,284 ↓ 12%

Trackers

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Calls created

Last 14 days

By team

Share of activity

Marketing 34%

Sales 27%

Client services 21%

Support 18%

FAQ

Frequently asked questions

How do I connect CallRail to Claude?

Connect CallRail in Elaichi by pasting the API key from your CallRail account settings, then open Claude and go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once Claude is connected, sign in as yourself and start asking about your CallRail calls.

Does CallRail work with ChatGPT and Cursor as well as Claude?

Yes. Once CallRail is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect CallRail once and every client sees it.

What can an AI agent actually do with my CallRail data?

An agent connected to CallRail can list and read calls, fetch a call's recording and the pages the caller viewed, create and update calls, trackers, tags and companies, and read form submissions and SMS threads. In practice that means asking which tracker drove the most calls this week, tagging last week's leads in bulk, or summarizing a client's form submissions. Short, specific asks work better than long paragraphs.

Does connecting CallRail give the AI access to every company in my account?

No. Every request to CallRail runs as the person who signed in, so the agent sees only the companies, calls and trackers that person can already see in CallRail. Elaichi can narrow that further with restrictions, and it can never widen it beyond what CallRail itself allows.

Can my team share one CallRail connection?

Yes. One person connects CallRail in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who read a recording or tagged a call.

Can I stop an agent from deleting or changing things in CallRail?

Yes. In Elaichi, restrictions on CallRail apply per action, so you can allow reading calls and form submissions while blocking bulk updates or user deletion. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

What happens to a CallRail connection when someone leaves?

Offboarding a person in Elaichi ends their access to CallRail through every client at once. A CallRail connection that was shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting CallRail once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

Does the CallRail MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. CallRail is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put CallRail in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.