Skip to content

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.

  • 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 CallHub to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect CallHub once

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

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

  3. Paste a CallHub API key. One person generates a token in CallHub 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.

callhub
CallHub
1Password
360learning
7shifts
Acquire
Active Ants
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.

CallHub 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.

CallHub 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.

CallHub 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 CallHub 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 CallHub through Elaichi

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

  • 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?”

See all 29 CallHub tools below

AI tools

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.

See it in Elaichi

What connecting CallHub gets you

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

The agent

Ask about supporters and get live answers.

Type a plain question and the agent reads CallHub contacts, phonebooks and campaigns.

  • contacts
  • phonebooks
  • teams
  • tags

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 or Cursor

MCP clients

One endpoint for every AI client.

Connect CallHub once and use it from Claude, ChatGPT or Cursor with no shared 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

29 CallHub tools, no code to write.

Contacts, phonebooks, tags, teams, agents and campaigns, covered the moment you connect.

  • Create a CallHub contact
  • Delete a CallHub contact by ID
  • Get single CallHub contact by ID
  • Update a CallHub contact by ID
ElaichiTools
Tool Action Description
Create a CallHub contact Create Create a new CallHub contact. Returns the created contact record including id, url, phonebooks, contact, mobile, first_name, last_name, and email. Required: contact (the phone number used in all voice campaigns).
Delete a CallHub contact by ID Delete Delete a CallHub contact by id. Returns an empty 204 response on success. Required: id.
Get single CallHub contact by ID Get Get a single CallHub contact by id. Returns the contact record including id, url, phonebooks, contact, mobile, first_name, last_name, and email. Required: id.
Update a CallHub contact by ID Update Update an existing CallHub contact by id. Returns the updated contact record including id, url, phonebooks, contact, mobile, first_name, and last_name. Required: id and contact (the phone number used in all voice campaigns).
Create a CallHub contact tag Create Create one or more tags on a CallHub contact. Returns the created tag objects including name, crm_type, crm_id, id, pk_str, and created_date. Required: contact_id, name.

Toolboxes

Every team gets its own CallHub toolbox.

Organizers, volunteer leads and compliance each work from a toolbox scoped to their job.

  • Organizing
  • Volunteer coordination
  • Communications
  • Compliance
ElaichiToolboxes
Name Source template Tools Created

Organizing toolbox

CallHub · contacts and phonebooks

CallHub starter 18 Mar 4, 2026

Volunteer coordination toolbox

CallHub · calling teams and agents

— 9 Mar 2, 2026

Communications toolbox

CallHub · texting campaigns and tags

— 24 Feb 27, 2026

Compliance toolbox

CallHub · do-not-call requests

CallHub starter 6 Feb 19, 2026

Fundraising toolbox

CallHub · donor contacts and call lists

— 31 Jan 30, 2026

Operations toolbox

CallHub · credits usage and campaign info

— 12 Jan 22, 2026

Shared connections

Share the connection, never the API key.

One organizer connects CallHub, teammates work through it without ever seeing a credential.

  • Field
  • Volunteer desk
  • Fundraising
  • Communications
ElaichiConnections
Connection Scope Status Access
CA

CallHub (Field)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
CA

CallHub (Volunteer desk)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
CA

CallHub (Fundraising)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
CA

CallHub (Communications)

Connected by Daniel Ortega

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

CallHub (Compliance)

Connected by Clara Nowak

Personal • Active Not shared
CA

CallHub (Regional north)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every CallHub change has a name on it.

See who added a contact, edited a team or flagged a number, and when.

  • 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]

CallHub Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

CallHub Contacts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

CallHub Contacts 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 starts the work, a person approves.

New CallHub contacts are fetched, grouped, drafted into a digest, approved, then posted back.

CallHub digest

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

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch contacts

    CallHub

    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

    CallHub

    Queued

Collections and dashboards

CallHub health, computed without a model.

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

CallHub health

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

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one CallHub connection?

Yes. One person connects CallHub in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs into Elaichi as themselves, so every contact added or team changed in CallHub is logged under their own name.

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 blocking deletion of contacts, tags or teams. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put CallHub 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.