CallRail MCP connector
The CallRail connector brings your tracked calls, trackers, companies, tags, form submissions and text threads into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about them and update them within their own CallRail access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which trackers drove the most calls this week?
Working in CallRail with Elaichi
-
List all CallRail calls
-
CallRail calls list page views
-
CallRail calls get recording
How to connect CallRail to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
CallRail MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
CallRail MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
CallRail MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
CallRail MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect CallRail to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with CallRail through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in CallRail is logged.
-
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.”
What connecting CallRail gets you
6 screens from Elaichi, each doing one job for your CallRail account.
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, Cursor or Microsoft Copilot
The agent
Ask about CallRail calls in plain language.
Live calls, trackers and form submissions answer back, no report to build first.
Copy the endpoint
AI apps
Use CallRail from any MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect through one org endpoint, no SDK and no shared API key.
Tool catalog
59 CallRail tools, no code to write.
Calls, trackers, companies, tags, form submissions and SMS threads, ready the moment you connect.
Toolboxes
Every team gets its own CallRail toolbox.
Marketing gets trackers, sales gets calls, client services gets companies, each scoped separately.
Shared connections
Teammates work in CallRail without the key.
One person connects, shares with teams, and nobody else ever sees the API key.
Audit log
Know who touched every CallRail record.
When, who, what happened and which call or tracker, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
CallRail digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch calls
CallRail
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
CallRail
Queued
Workflows
A schedule turns CallRail calls into digests.
Calls are fetched, grouped by tracker, drafted, approved by a person, then posted back.
CallRail health
Refreshed 4 minutes ago · every 15 minutes · from the calls collection
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%
Collections and dashboards
CallRail call volume, computed without a model.
Four metrics, 14 days of calls created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for CallRail
All three can connect CallRail to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over CallRail tools | Allow or restrict single CallRail tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per CallRail call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting bulk updates or user deletion. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for CallRail?
Yes. Both let Claude, ChatGPT or Cursor use CallRail. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every CallRail call.
How is Elaichi different from Composio for CallRail?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to CallRail: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put CallRail in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot