Karbon MCP connector
The Karbon connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent look up and update Karbon contacts, client groups, business cards and files, with every call running as the signed-in person and logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Find the business card for Harbor Dental and check the address
Working in Karbon with Elaichi
-
Get single Karbon business card by ID
-
Get single Karbon client group by ID
-
List all Karbon client groups
How to connect Karbon to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Karbon 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.
Karbon 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.
Karbon 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.
Karbon 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.
Karbon 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 Karbon 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 Karbon through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Karbon is logged.
-
Client services
Find a client's details before the call
Ask for a client's contact record and business card and get the phone number, address and which client group they belong to, without opening Karbon.
-
Onboarding
Set up a new client properly
Create the contact in Karbon, add it to the right client group and fill in the custom fields the firm uses, all from one plain request.
-
Tax
Catch the record up after a meeting
After a client meeting, update the business card in Karbon with a new address, trading name or phone number while the details are still fresh.
-
Bookkeeping
See which folders and files are linked
Check which document folders are connected to a client entity in Karbon and list the files sitting in them before chasing a client for paperwork.
-
Practice management
Keep custom fields consistent across clients
List the custom fields in use across Karbon, find the client records with values missing, and update them from a short request.
-
Partners
Read the latest comments before replying
Pull up a client group in Karbon, see which contacts and entities sit inside it, and read the most recent comment before answering the client.
Try asking
- “Find the business card for Harbor Dental and check the address”
- “Which contacts in the Patel family client group have no email?”
- “Update the trading name on the Oakridge Holdings business card”
What connecting Karbon gets you
6 screens from Elaichi, each doing one job for your Karbon account.
Ask Elaichi to work across your apps.
Find the business card for Harbor Dental and check the address
Which contacts in the Patel family client group have no email?
Update the trading name on the Oakridge Holdings business card
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any Karbon client in plain language.
Get answers from live Karbon contacts, client groups and business cards, not a stale export.
Copy the endpoint
AI apps
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach Karbon through one governed endpoint over OAuth, no SDK required.
Tool catalog
83 Karbon tools, ready without writing code.
Contacts, client groups, business cards, custom fields and files, covered with no custom code.
Toolboxes
Every team gets its own Karbon toolbox.
Tax, bookkeeping and client services each work from a toolbox scoped to their job.
Shared connections
Share a Karbon connection, never a credential.
One person connects Karbon and teammates work through it without ever seeing the API key.
Audit log
Know who changed which Karbon record.
Every call lands in an append-only log with who, when, what happened and which resource.
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.
Karbon digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
Karbon
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
Karbon
Queued
Workflows
A schedule starts the work, a person approves.
New Karbon contacts are fetched, grouped, drafted into a digest, approved, then posted back to Karbon.
Karbon health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Client groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Tax 34%
Bookkeeping 27%
Advisory 21%
Client services 18%
Collections and dashboards
Karbon numbers, computed on a schedule, no model.
Four metrics, fourteen days of contacts created and a split by team, refreshed without asking.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Karbon
All three can connect Karbon 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 Karbon tools | Allow or restrict single Karbon 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 Karbon 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.
Karbon tools for your AI agents
83 tools are ready to call through Elaichi's MCP endpoint the moment you connect Karbon, 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 Karbon to Claude?
Connect Karbon in Elaichi by pasting a Karbon API key, which you copy from your Karbon settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Karbon is ready to use.
Does Karbon work with ChatGPT and Cursor as well as Claude?
Yes. Once Karbon is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Karbon once and every client picks it up.
What can an AI agent actually do with my Karbon data?
An agent can look up Karbon contacts, client groups and business cards, create new contacts and client groups, and update a business card with a new address or trading name. It can also read comments, list the custom fields your firm uses and update their values, and show which document folders and files are connected to a client. Short, concrete asks such as "find the business card for Harbor Dental" work better than long sentences.
Does connecting Karbon give the AI access to every client in the practice?
No. Every call to Karbon runs as the person who signed in, so an agent sees only the contacts, client groups and files that person can already see in Karbon. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Karbon itself allows.
Can I stop an agent from deleting or changing things in Karbon?
Yes. Restrictions in Elaichi work per action, so you can allow reading Karbon contacts while restricting updates to business cards or deleting custom fields, and you can set them on a role or on one person. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Karbon connection when someone leaves?
Offboarding a person in Elaichi ends their access to Karbon through every client at once. If they connected a shared Karbon connection, it keeps working for everyone else on the team. Disconnecting Karbon once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Karbon MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Karbon 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 Karbon?
Yes. Both let Claude, ChatGPT or Cursor use Karbon. 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 Karbon call.
How is Elaichi different from Composio for Karbon?
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 Karbon: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Karbon 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