Voice
CallHub MCP connector
The CallHub connector brings contacts, phonebooks, tags, calling teams and campaigns into Elaichi, so Claude, ChatGPT or any MCP client can add supporters, tag them and check campaign usage within each person's own CallHub access.
- Connects with an API key
- Free 14-day trial
- No credit card
Add these 40 canvass sign-ups to the Precinct 12 phonebook
Working in CallHub with Elaichi
-
Get single CallHub contact by ID
-
List all CallHub phonebook contacts
-
Get single CallHub tag by ID
How to connect CallHub to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
CallHub 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.
CallHub 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.
CallHub 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.
CallHub 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.
CallHub 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 CallHub 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 CallHub through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in CallHub is logged.
-
Organizing
Add new supporters after a canvass
Hand over the sign-up sheet and have the new names created as CallHub contacts in one batch, with the right tags already on them.
-
Field
Move a list into the right phonebook
Add a batch of contacts to a phonebook before a call shift, or pull them out once the shift is done, without editing one row at a time.
-
Volunteer coordination
Set up a calling team for Saturday
Create a new team in CallHub, add the volunteers who confirmed, and update agents who changed shifts, all from a plain request.
-
Compliance
Honor a do-not-call request right away
When someone asks to stop being called, add them to the do-not-call list on the spot so no future campaign reaches them.
-
Communications
Adjust a texting campaign before it goes out
Update a peer-to-peer texting campaign's details and review which campaigns are live, so the message that goes out is the one you meant.
-
Operations
Check credits before a big push
Ask how many credits recent campaigns used and what is left, so the next calling or texting run is budgeted before it starts.
Try asking
- “Add these 40 canvass sign-ups to the Precinct 12 phonebook”
- “Tag every contact who asked about housing with Housing”
- “How many credits did the GOTV texting campaign use this week?”
What connecting CallHub gets you
6 screens from Elaichi, each doing one job for your CallHub account.
Ask Elaichi to work across your apps.
Add these 40 canvass sign-ups to the Precinct 12 phonebook
Tag every contact who asked about housing with Housing
How many credits did the GOTV texting campaign use this week?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about supporters and get live answers.
Type a plain question and the agent reads CallHub contacts, phonebooks and campaigns.
Copy the endpoint
AI apps
One endpoint for every AI client.
Connect CallHub once and use it from Claude, ChatGPT, Cursor or Microsoft Copilot with no shared key.
Tool catalog
29 CallHub tools, no code to write.
Contacts, phonebooks, tags, teams, agents and campaigns, covered the moment you connect.
Toolboxes
Every team gets its own CallHub toolbox.
Organizers, volunteer leads and compliance each work from a toolbox scoped to their job.
Shared connections
Share the connection, never the API key.
One organizer connects CallHub, teammates work through it without ever seeing a credential.
Audit log
Every CallHub change has a name on it.
See who added a contact, edited a team or flagged a number, and when.
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.
CallHub digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
CallHub
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
CallHub
Queued
Workflows
A schedule starts the work, a person approves.
New CallHub contacts are fetched, grouped, drafted into a digest, approved, then posted back.
CallHub health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Phonebooks
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Field 34%
Volunteer desk 27%
Fundraising 21%
Communications 18%
Collections and dashboards
CallHub health, computed without a model.
Four metrics, 14 days of contacts created and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for CallHub
All three can connect CallHub 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 CallHub tools | Allow or restrict single CallHub 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 CallHub 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.
CallHub tools for your AI agents
29 tools are ready to call through Elaichi's MCP endpoint the moment you connect CallHub, 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 CallHub to Claude?
Connect CallHub in Elaichi first: CallHub signs in with an API key, so you paste the key from your CallHub account and Elaichi holds it. There is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and your CallHub contacts, phonebooks and teams are ready to ask about.
Does CallHub work with ChatGPT and Cursor as well as Claude?
Yes. Once CallHub 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 CallHub once and every client sees it.
What can an AI agent actually do with my CallHub data?
With CallHub connected, an agent can create and update contacts, add or remove them from phonebooks in bulk, create and apply tags, and add people to the do-not-call list. It can also set up calling teams, update team agents, list your campaigns, update a peer-to-peer texting campaign and report on credits usage. Short concrete asks, such as "add these ten names to the Ward 3 phonebook", work better than long paragraphs.
Does connecting CallHub give the AI access to all of my account?
No. Every request to CallHub runs as the person who signed in, so the agent only sees the contacts, phonebooks, teams and campaigns that person can already reach in CallHub. Elaichi can narrow that further with roles and restrictions, and it never widens what CallHub itself allows.
Can I stop an agent from deleting or changing things in CallHub?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and creating CallHub contacts while restricting deletion of contacts, tags or teams. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a CallHub connection when someone leaves?
Offboarding a person in Elaichi ends their access to CallHub through every client at once. If they connected a shared CallHub account, that connection keeps working for everyone else on the team. Disconnecting CallHub once in Elaichi removes it from every client at the same time.
Does the CallHub MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. CallHub 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 CallHub?
Yes. Both let Claude, ChatGPT or Cursor use CallHub. 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 CallHub call.
How is Elaichi different from Composio for CallHub?
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 CallHub: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put CallHub 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