Skip to content

Connectors / CRM

CRM MCP connectors for Claude, ChatGPT and Cursor

20+ CRM connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

https://api.elaichi.ai/mcp The same for every user.
  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

In practice

What teams do with CRM connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Sales

  • Catch the company record up after a call

    Tell the agent what happened on the call and it adds a comment to the Sellsy company, so the history is current before the next touch.

  • Catch a contact up after a call

    Tell the agent what changed on the call and it updates the Highlevel contact, applies the right tag and adds the rep who now owns the relationship as a follower.

  • Ask pipeline questions in plain language

    Which companies came in this week with no owner, which contacts have gone quiet, what is closing this month. Every answer is scoped to what that person can already see in HubSpot.

Marketing

  • Review new leads before handoff

    Pull the leads that came in this week, check what is filled in and what is missing, and tidy up notes before they go to a rep.

  • Add event leads straight into Pipedrive

    Paste a list of names, companies and emails from a webinar or trade show and the agent creates the people and organizations in Pipedrive and opens a deal for the ones worth following.

  • Check which lead sources convert

    List the lead sources set up in Zendesk Sell and the leads that came from each, then compare them against the pipeline stages to see where webinar and paid leads actually end up.

Operations

  • Clean up contacts and individuals in bulk

    Walk through Virtuous contacts that need a corrected address, a renamed individual or a merged duplicate, and apply the updates one confirmed change at a time.

  • Keep custom fields tidy and consistent

    Add, rename or retire a contact field in Nimble and set which value counts as primary, without clicking through every record by hand.

  • Clean up duplicate and stale records

    Spot organizations and people that need merging or updating, fix names, domains and details, and remove records that should not be there, within the limits your admin has set.

Support

  • Give Support case context, not the pipeline

    Cases and contacts, and no opportunities. Support sees the customer and their history, and the pipeline stays where it belongs.

  • See every end user at an account

    Before replying to a ticket, ask who the end users are at that company in Planhat and which issues are already open for them.

  • Log a customer issue on their record

    When a customer writes in, the agent finds their Octapipe record, adds a note describing the problem, and attaches the file they sent.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the CRM account you connected.

  • List opportunities created in Affinity this week

    Affinity

  • Which Attio companies have no owner assigned?

    Attio

  • Search EveryAction people in Ohio added this week.

    EveryAction

  • Find contacts in Google Contacts with no email address.

    Google Contacts

  • List Highlevel contacts added to the London location this week.

    Highlevel

  • List HubSpot companies created this week with no owner.

    HubSpot

  • Which Jobber requests came in this week and from whom?

    Jobber

  • Which leads booked appointments this week?

    LeadPerfection

The tools

What an agent can call in CRM

Connectors
20+

in the CRM catalog

Tools
2,643

callable the moment you connect

Hosted sign-in
17

connect with nothing to register

Of those 2,643 tools, 11% delete something. Restricting an agent to reads is not a promise here, it is 1,187 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 45%
1,187 tools · list, get, search
Write 30%
781 tools · create, update, send
Delete 11%
303 tools · delete, remove, archive
Other 14%
372 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every CRM connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

CRM connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Virtuous 345 Hosted
Sellsy 327 Hosted
Highlevel 297 Your own app
HubSpot 283 Your own app
Zoho CRM 243 Hosted
Salesforce 154 Hosted
Pipedrive 117 Your own app
Zendesk Sell 101 Your own app
Wiwink 100 Hosted
Attio 97 Your own app
Planhat 97 Hosted
Nimble 85 Hosted
Affinity 61 Hosted
LeadPerfection 59 Hosted
Membes 58 Hosted
Wealthbox 50 Your own app
Octapipe 42 Hosted
LendingWise 32 Hosted
EveryAction 29 Hosted
Streak 24 Hosted
Jobber 15 Your own app
Method CRM 14 Hosted
Zoho Bigin 7 Hosted
Google Contacts 6 Hosted

FAQ

Frequently asked questions

How many CRM connectors does Elaichi have?

20+ CRM connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use CRM connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a CRM account once makes it reachable from every one of them.

Do CRM connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. CRM connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do CRM connectors need me to bring my own OAuth app?

Most do not. 17 of the CRM connectors use Elaichi's hosted sign-in, with nothing to register. The other 7 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.

Can I stop an agent from writing to CRM tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a CRM connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared CRM connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Put CRM connectors in front of your team

14 days on Gold, no credit card. Connect one 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.