Skip to content

Helpdesk

Kustomer MCP connector

The Kustomer connector brings your Kustomer customers, conversations, and agents into Claude, ChatGPT, Cursor, or any MCP client, so your team can look up, create, and update Kustomer records by asking in plain language, inside their own Kustomer 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 Kustomer to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Kustomer once

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

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

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

kustomer
Kustomer
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
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.

Connect Kustomer to 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.

Connect Kustomer to 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.

Connect Kustomer to 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 Kustomer 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 Kustomer through Elaichi

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

  • Support

    Find the customer before you answer

    Look up a Kustomer customer by email, phone number, or an ID from another system and see their open conversations before replying.

  • Support

    Open a conversation after a phone call

    Create a new Kustomer conversation for the customer you just spoke with and set its details while the call is still fresh.

  • Support leadership

    Reassign a backlog in one pass

    Pull the list of Kustomer conversations matching a filter and update them together, such as moving a stalled group to a different agent or status.

  • Operations

    Load customers from another system

    Create or update Kustomer customers in bulk from a list, matched on the external ID your billing or order system already uses.

  • Customer experience

    Review a customer's full history

    Ask for everything Kustomer holds on one customer, including their record and every conversation, and get it summarized in a few lines.

  • Account management

    Check for open issues before a renewal

    Before a renewal or upsell call, see whether the account has unresolved Kustomer conversations and what they are about.

Try asking

  • “Find the Kustomer customer with this email address.”
  • “Summarize open Kustomer conversations for the billing queue.”
  • “List Kustomer users added to the support team this month.”

See all 168 Kustomer tools below

AI tools

Kustomer tools for your AI agents

168 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kustomer, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Kustomer gets you

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

The agent

Ask in plain language, read live Kustomer records.

Start with a prompt and get answers from Kustomer customers and conversations.

  • customers
  • conversations
  • users
  • messages

Ask Elaichi to work across your apps.

Find the Kustomer customer with this email address.

Summarize open Kustomer conversations for the billing queue.

List Kustomer users added to the support team this month.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Kustomer here.

One org MCP endpoint over OAuth, no SDK and no shared API 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

168 Kustomer tools are ready to call.

Customers, users and conversations covered by name, with no custom code to write.

  • List all Kustomer me
  • List all Kustomer users
  • Get single Kustomer user by ID
  • Update a Kustomer user by ID
ElaichiTools
Tool Action Description
List all Kustomer me List Get information about the current user in Kustomer. Returns id, type, attributes, relationships, and links fields in the response.
List all Kustomer users List Get users in Kustomer. Returns user type, id, attributes, relationships, and links for each user.
Get single Kustomer user by ID Get Get user by id in Kustomer. Requires id. Returns user data including type, id, attributes, relationships, and links.
Update a Kustomer user by ID Update Update a specific user by id in Kustomer. Requires id and fields such as displayName, avatarUrl, name, email, mobile, emailSignature, deleted, password, currentPassword, userType, roleGroups, and roles. Returns updated user data including type, id, attributes, relationships, and links.
Create a Kustomer user Create Create a new user in Kustomer with required parameters name and email. Returns user id, type, attributes, relationships, and links in the response.

Toolboxes

Every team gets its own Kustomer toolbox.

Curate one toolbox per team so Support and Ops see different Kustomer tools.

  • Support
  • Customer Success
  • Escalations
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Kustomer · conversations and customers

Kustomer starter 18 Mar 4, 2026

Customer Success toolbox

Kustomer · customer records and history

9 Mar 2, 2026

Escalations toolbox

Kustomer · high priority conversations

24 Feb 27, 2026

Operations toolbox

Kustomer · users, teams and queues

Kustomer starter 6 Feb 19, 2026

Quality toolbox

Kustomer · conversation reviews and tags

31 Jan 30, 2026

Data toolbox

Kustomer · customer lookups and exports

12 Jan 22, 2026

Shared connections

Teammates use Kustomer without seeing a credential.

Each connection shows who connected it and how many teams and members share it.

  • Support EMEA
  • Support US
  • Customer Success
  • Escalations
ElaichiConnections
Connection Scope Status Access
KU

Kustomer (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
KU

Kustomer (Support US)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
KU

Kustomer (Customer Success)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
KU

Kustomer (Escalations)

Connected by Daniel Ortega

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

Kustomer (Billing Queue)

Connected by Clara Nowak

Personal • Active Not shared
KU

Kustomer (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Kustomer call is written down.

When, who, what happened, type and resource for each Kustomer request.

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

Kustomer Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Kustomer Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Kustomer Customers 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 fires, Kustomer work gets done.

Fetch conversations, group them, draft a digest, approve it, post back to Kustomer.

Kustomer digest

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch customers

    Kustomer

    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

    Kustomer

    Queued

Collections and dashboards

Kustomer health arrives before anyone asks.

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

Kustomer health

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

Live

Customers

1,284 ↓ 12%

Conversations

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support US 27%

Customer Success 21%

Escalations 18%

FAQ

Frequently asked questions

How do I connect Kustomer to Claude?

Connecting Kustomer to Claude takes two steps. First, connect Kustomer in Elaichi by pasting a Kustomer API key when prompted; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Kustomer is available in your conversations.

Does Kustomer work with ChatGPT and Cursor as well as Claude?

Yes. Once Kustomer 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 Kustomer once and every client picks it up.

What can an AI agent actually do with my Kustomer data?

An AI agent connected to Kustomer can look up a customer by email, phone number, or external ID, read their record and conversations, and create or update customers and conversations, including in bulk. It can also list the agents in your Kustomer organization and update their details. Because Kustomer offers many actions, short concrete asks such as "find the Kustomer customer with this phone number" work better than long paragraphs.

Does connecting Kustomer give the AI everything in my Kustomer organization?

No. The connection to Kustomer runs with the access of the API key that was connected, and each person using it signs in to Elaichi as themselves, so every request is tied to a named person. Elaichi can narrow what the AI is allowed to do with Kustomer, for example read only, and it can never widen access beyond what Kustomer itself permits.

Can my team share one Kustomer connection?

Yes. One person connects Kustomer in Elaichi and shares the connection with a team, and nobody else ever sees or handles the Kustomer API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who looked up or changed each Kustomer customer or conversation.

Can I stop an agent from deleting or changing things in Kustomer?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Kustomer customers and conversations while blocking deletion, bulk changes, or any update at all. A blocked action is never advertised to Claude, ChatGPT, or Cursor, so no prompt, however worded, can reach it.

What happens to a Kustomer connection when someone leaves?

When a person is offboarded in Elaichi, their access to Kustomer through every AI client ends at once. A Kustomer connection shared with a team keeps working for everyone else on that team. If you want to remove Kustomer entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.

Put Kustomer in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.