Skip to content
Custom Connectors

Full read-write Claude connector for Kustomer

Let Claude draft replies, set status, and assign conversations in Kustomer

Stop tab-switching to triage and follow up. Claude works on the timeline where the conversation already lives: drafting the reply, setting status and queue, adding an internal note, tagging, and assigning, with sends and closures held for your approval.

Kustomer is a CRM-style customer service platform that unifies conversations, customer timelines, and support across email, chat, and messaging. People want Claude to do more than read conversations: to draft and send replies, change status, add notes, and assign work without leaving the timeline.

What is a Kustomer MCP server?

A Kustomer MCP server is a small hosted service that exposes Kustomer's data and actions to Claude over the Model Context Protocol, so Claude can tickets and customer conversations inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Kustomer's current connector do today?

Today, Kustomer ships an official native Claude connector, but it is read-only. Claude can search and read conversations, customers, and timelines to analyze and summarize, yet it cannot act. It does not send replies, change status, add notes, tag, or assign inside the conversation where the work actually lives.

What does full read-write Kustomer access unlock?

A custom connector keeps that read access and adds the write actions the native tool set leaves out. Claude can draft a reply on the right conversation, set status and queue, add an internal note for the next agent, tag the conversation, and assign it to the correct person or team, all after you approve. Triage and follow-up happen where the conversation already lives.

  • Draft a reply on a conversation, preserving the customer and message history
  • Set a conversation's status to open, snoozed, or done as it moves
  • Add an internal note with context for the next agent
  • Apply tags and assign the conversation to the right team or queue
  • Update fields on a customer's timeline to keep records current
  • Search conversations matching a query and propose batched responses

Can Claude reply to Kustomer conversations, not just read them?

Yes. Claude can reply to Kustomer conversations through a write tool that drafts the response on the original conversation, keeping the customer and message history intact. The native connector only reads, so this comes from a purpose-built MCP server, and the reply is sent only after you approve it.

Can Claude triage and assign conversations in Kustomer?

Claude can triage Kustomer conversations by searching, setting status to open, snoozed, or done, adding an internal note for the next agent, applying tags, and assigning to the right person, team, or queue. It moves work along the timeline while gated sends and closures wait for your confirmation.

Does the Kustomer connector get more access than my account has?

No. The Kustomer connector authenticates with a scoped API key tied to your account and inherits your existing role and permissions. It never grants Claude more access than you already have, so it cannot touch conversations, customers, or fields that are off-limits to you, and an admin can revoke the key anytime.

How a Kustomer connector works

We build a small MCP server that authenticates to Kustomer with a scoped API key over your account's existing permissions. Read tools (search, read conversation) and write tools (reply, set status, note, tag, assign) are separated, and outbound or destructive actions like sending a reply or closing a conversation require your confirmation. Claude only ever has the access your own Kustomer account already has, and an admin can revoke the key at any time.

Frequently asked questions

Can Claude reply to Kustomer conversations, not just read them?
Yes. A custom Kustomer connector exposes a reply write tool, so Claude drafts the response on the original conversation with the customer and message history intact. The native connector is read-only, so this in-conversation reply capability comes from a purpose-built MCP server, and the reply is sent only after you approve it.
Will Claude send Kustomer replies or close conversations without my approval?
No. Sending a reply and closing a conversation are separate, gated write actions. Claude can prepare the reply, set the status, and stage the change, but it is only applied after you approve it. You decide which actions run automatically and which require a confirmation step before anything reaches a customer.
Does the Kustomer connector get more access than my account has?
No. The connector authenticates with a scoped API key tied to your account and inherits your existing role and permissions. It never grants Claude more access than you already have in Kustomer, so it cannot see conversations, customers, or fields that are off-limits to you, and the key can be revoked at any time.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.