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

Source: https://elaichi.ai/connectors/karbon/

## Facts

| | |
| --- | --- |
| Application | Karbon |
| Category | CRM |
| AI tools | 83 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Karbon is connected

- 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

## Connect Karbon in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Karbon.
2. Optionally set Share with, then press Connect.
3. Paste a Karbon API key. One person generates a token in Karbon and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Karbon tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Karbon MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Karbon MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Karbon tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Karbon through Elaichi

### Find a client's details before the call

Client services. 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.

### Set up a new client properly

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

### Catch the record up after a meeting

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

### See which folders and files are linked

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

### Keep custom fields consistent across clients

Practice management. List the custom fields in use across Karbon, find the client records with values missing, and update them from a short request.

### Read the latest comments before replying

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

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Karbon connection?

Yes. One person connects Karbon in Elaichi and shares the connection with a team, and nobody else ever handles the Karbon API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every lookup and update in Karbon.

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

## All 83 Karbon tools

Every tool below is callable through https://api.elaichi.ai/mcp once Karbon is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single Karbon business card by ID** (Get). Gets a single Business Card. Use the GET method on this endpoint to receive the details of a Business Card specified using the BusinessCardKey. Required: id.
- **Update a Karbon business card by ID** (Update). Updates a single Business Card. Use the PUT method on this endpoint to update the details of a Business Card specified using the BusinessCardKey. Required: id, BusinessCardKey.
- **Create a Karbon client group** (Create). Creates a new Client Group. Use the POST method on this endpoint to create a new Client Group in your tenant. Required: FullName.
- **Get single Karbon client group by ID** (Get). Gets a Client Group using ClientGroupkey. Use the GET method on this endpoint to receive the details of a Client Group specified using the ClientGroupKey. Using the query parameter available to this endpoint, you can also include the Business Card details of the Client Group in the response. Required: id.
- **List all Karbon client groups** (List). Gets a list of Client Groups. Use the GET method on this endpoint to receive a paginated list of Client Groups from your tenant. Using the query parameters available to this endpoint, you can also filter the list of Client Groups by their full name. Notes * This endpoint returns a maximum of 100 Client Groups at once. The connector pages with $skip / $top ($top = the caller's limit, max 100); records at value.
- **Karbon client groups partial update** (Update). Updates a Client Group (Partial). Use the PATCH method on this endpoint to update partial details of a Client Group specified using the ClientGroupkey. This method only supports editing the FullName property. PATCH beside the PUT update: the record key is a named query field (the connector passes {{id}} only to get / update / delete). Required: client_group_key.
- **Update a Karbon client group by ID** (Update). Updates a Client Group (Full). Use the PUT method on this endpoint to update full details of a Client Group specified using the ClientGroupkey. Using the query parameter available to this endpoint, you can also update the Business Card details of the Client Group. Required: id, FullName.
- **Get single Karbon client groups by user defined identifier by ID** (Get). Gets a Client Group using UserDefinedIdentifier. Use the GET method on this endpoint to receive the details of a Client Group specified using the UserDefinedIdentifier. Using the query parameter available to this endpoint, you can also include Business Card details of the Client Group in the response. The id is your UserDefinedIdentifier (a single quote in it is written twice, OData style). Required: id.
- **Get single Karbon comment by ID** (Get). Gets a Comment using CommentKey. This endpoint can be used to get the comment attached to any Karbon entity (e.g., Work Item, Timesheet, Notes, Contacts). To place a call using this endpoint, you will need the unique Commentkey that is used to identify a particular comment in Karbon. Required: id.
- **Create a Karbon contact** (Create). Creates a new Contact. Use the POST method on this endpoint to create a new Contact in your tenant. Required: FirstName, LastName.
- **Get single Karbon contact by ID** (Get). Gets a Contact using Contactkey. Use the GET method on this endpoint to receive the details of a Contact specified using the Contactkey. Using the query parameter available to this endpoint, you can also include the Business Card details of the Contacts in the response. Required: id.
- **List all Karbon contacts** (List). Gets a list of Contacts. Use the GET method on this endpoint to receive a paginated list of Contacts from your tenant. Using the query parameters available to this endpoint, you can also filter the list of Contacts by their full name, email address, or phone number. The connector pages with $skip / $top ($top = the caller's limit, max 100); records at value.
- **Karbon contacts partial update** (Update). Updates a Contact (Partial). Use the PATCH method on this endpoint to update partial details of a Contact specified using the Contactkey. This method only supports editing the FirstName, MiddleName, LastName, PreferredName, Salutation, Suffix and RestrictionLevel properties. PATCH beside the PUT update: the record key is a named query field (the connector passes {{id}} only to get / update / delete). Required: contact_key.
- **Update a Karbon contact by ID** (Update). Updates a Contact (Full). Use the PUT method on this endpoint to update full details of a Contact specified using the Contactkey. Using the query parameter $expand with this endpoint, you can also update the Business Card details of the Contact. Required: id, FirstName, LastName.
- **Get single Karbon contacts by user defined identifier by ID** (Get). Gets a Contact using UserDefinedIdentifier. Use the GET method on this endpoint to receive the details of a Contact specified using the UserDefinedIdentifier. Using the query parameter available to this endpoint, you can also include Business Card details of the Contact in the response. The id is your UserDefinedIdentifier (a single quote in it is written twice, OData style). Required: id.
- **Get single Karbon custom field value by ID** (Get). Gets custom field values for a specific entity. Retrieves the custom fields for a Contact or Organization. Required: id.
- **Update a Karbon custom field value by ID** (Update). Updates custom field values for a specific entity. Performs an update of the complete set of custom field values for a Contact or Organization. Required: id.
- **Create a Karbon custom field** (Create). Creates a new custom field definition. Defines a new custom field that can be assigned to a Contact and/or Organization - use the Karbon UI to create examples of how a new field with specific list options should be created.
- **Delete a Karbon custom field by ID** (Delete). Deletes a custom field definition by key. Delete a custom field defintion by key. Required: id.
- **List all Karbon custom fields** (List). Gets all custom field definitions for the current tenant. Retrieve a list of all of the custom fields that have been created for a Karbon account.
- **Delete a Karbon dms connected folder by ID** (Delete). Disconnect the DMS folder from a Karbon entity. Note: This endpoint is only enabled on request. Removes the Document Management System folder connection from a Karbon entity. The folder itself is not deleted from the provider. Required: id, entityKey.
- **Get single Karbon dms connected folder by ID** (Get). Get the DMS folder connected to a Karbon entity. Note: This endpoint is only enabled on request. Returns the Document Management System folder connected to a specific Karbon entity. The @odata.type of the response identifies the provider (SharePoint, OneDrive, Google Drive or Google Shared Drive) and which identifier fields are present. Required: id, entityKey.
- **Update a Karbon dms connected folder by ID** (Update). Connect a DMS folder to a Karbon entity. Note: This endpoint is only enabled on request. Connects a Document Management System folder to a Karbon entity. Required: id, odata_type, EntityKey, FolderId.
- **List all Karbon entity files** (List). Get a list of Files for a given entity. Use the GET method on this endpoint to list files associated with a specific Entity Type and Entity Key. The list supports $filter on IsArchived, IsShared, Source and MimeType (eq only, combined with and). Files are returned newest first when $orderby is omitted. Required: entity_type, EntityKey. The connector pages with $skip / $top ($top = the caller's limit, max 500); records at Attachments.
- **Get single Karbon estimate summary by ID** (Get). Gets a single Estimate Summary using WorkItemKey and EstimateSummaryKey. Use the GET method on this endpoint to receive a single estimate summary on a Work Item, specified using the WorkItemKey and EstimateSummaryKey. An EstimateSummaryKey starting with 0- represents time recorded against a task with no estimate assigned, rather than an actual estimate. Required: id, work_item_key.
- **List all Karbon estimate summaries** (List). Gets estimate summaries using WorkItemKey. Use the GET method on this endpoint to receive the estimate summaries of a Work Item specified using the WorkItemKey. Required: work_item_key.
- **Update a Karbon estimate summary by ID** (Update). Updates a single Estimate Summary. Use the PATCH method on this endpoint to update the estimated minutes or amount, and/or the hourly rate, for an estimate summary. Only EstimateMinutes, EstimateAmount and HourlyRate are accepted, and each is optional. Required: id, work_item_key.
- **Create a Karbon expense** (Create). Creates a new Expense. Use the POST method on this endpoint to create an Expense and associate it with a WorkItem, Contact or Organization in your tenant. Expenses cannot be listed, updated or deleted through the API. Required: Timeline, ExpenseDate, Value, BillableValue, Description.
- **Get single Karbon file detail by ID** (Get). Get the details of a single File. Use the GET method on this endpoint to retrieve the current details of a single file, using the FileContextKey returned by GET /v3/FileList/{EntityType}. Required: id.
- **Get single Karbon file download by ID** (Get). Redirect to download a single File. Use the GET method on this endpoint to be redirected to a freshly-tokened download URL for the file identified by key (the FileContextKey returned by GET /v3/FileList/{EntityType}). Required: id.
- **Create a Karbon file** (Create). Uploads and links a file. Use the POST method on this endpoint to upload and link a file to an entity in your tenant. Note that this endpoint only supports uploading files from the local network but not from the web. Required: file.
- **Get single Karbon file by ID** (Get). Get a File using it's token. Use the GET method on this endpoint with the token query string parameter to retrieve a file. Note: download tokens are only valid for 15 minutes from the moment of issue. Required: id.
- **Get single Karbon individual time entry by ID** (Get). Gets an individual time entry by key. Use the GET method on this endpoint to receive the details of a single individual time entry specified using the IndividualTimeEntryKey. Required: id.
- **List all Karbon individual time entries** (List). Gets a list of individual time entries. Use the GET method on this endpoint to receive a paginated list of individual (non-aggregated) time entries from your tenant. The connector pages with $skip / $top ($top = the caller's limit, max 100); records at value.
- **List all Karbon integration task definitions** (List). Get a list of integration task definitions. Use the GET method on this endpoint to receive a list of the integration task types that have been defined for your integration.
- **Get single Karbon integration task by ID** (Get). Get an integration task details. Use the GET method on this endpoint to retrieve the details of a single integration task. Required: id.
- **List all Karbon integration tasks** (List). Get a list of integration tasks. Use the GET method on this endpoint to receive a list of the integration tasks created in the Karbon account which has connected your integration.
- **Update a Karbon integration task by ID** (Update). Update an integration task. Use the PUT method on this endpoint to update the details of a single integration task. Required: id.
- **Get single Karbon invoice by ID** (Get). Gets a single Invoice. Use the GET method on this endpoint to receive the details of an Invoice specified using the InvoiceKey. The response includes InvoiceMagicLink, a link for the client to pay the invoice through Karbon Payments, and InvoicePdfUrl, a link to the rendered invoice PDF. Required: id.
- **List all Karbon invoices** (List). Gets a list of Invoices. Use the GET method on this endpoint to receive a list of Invoices. The connector pages with $skip / $top ($top = the caller's limit, max 100); records at value.
- **Create a Karbon manual payment** (Create). Create a manual payment against an Invoice. Use the POST method on this endpoint to create a Manual Payment. Required: InvoiceKey, PaymentMethod, PaymentDate, TotalAmount.
- **Delete a Karbon manual payment by ID** (Delete). Delete a manual payment. Use the DELETE method on this endpoint to delete a Manual Payment. Required: id.
- **Karbon manual payments reverse** (Action). Reverse a manual payment. Use the POST method on this endpoint to reverse a Manual Payment. Required: PaymentKey, ReversalDate.
- **Create a Karbon note** (Create). Creates a new Note. Use the POST method on this endpoint to create a new Note and associate it with a Karbon entity (e.g., WorkItem, Contact, Organization, or ClientGroup) in your tenant. Required: Subject, Body, AuthorEmailAddress.
- **Get single Karbon note by ID** (Get). Gets a Note using NoteID. Use the GET method on this endpoint to receive the Note specified using the NoteID. Required: id.
- **Create a Karbon organization** (Create). Creates a new Organization. Use the POST method on this endpoint to create a new Organization in your tenant. Required: FullName.
- **Get single Karbon organization by ID** (Get). Gets an Organization using Organizationkey. Use the GET method on this endpoint to receive the details of an Organization specified using the Organizationkey. Using the query parameter available to this endpoint, you can also include the Business Card details of the Organization in the response. Required: id.
- **List all Karbon organizations** (List). Gets a list of Organizations. Use the GET method on this endpoint to receive a paginated list of Organizations from your tenant. Using the query parameters available to this endpoint, you can also filter the list of Organizations by their full name, email address, or external key. The connector pages with $skip / $top ($top = the caller's limit, max 100); records at value.
- **Karbon organizations partial update** (Update). Updates an Organization (Partial). Use the PATCH method on this endpoint to update partial details of an Organization specified using the Organizationkey. This method only supports editing the FullName and RestrictionLevel properties. PATCH beside the PUT update: the record key is a named query field (the connector passes {{id}} only to get / update / delete). Required: organization_key.
- **Update a Karbon organization by ID** (Update). Updates an Organization (Full). Use the PUT method on this endpoint to update full details of an Organization specified using the Organizationkey. Using the query parameter $expand with this endpoint, you can also update the Business Card details of the Organization. Required: id, FullName.
- ...and 33 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
