Integration

Kustomer integration

Kustomer API v1, the customer service CRM built around a single customer timeline. Create, read, update and search customers (including lookup by email address), open and update conversations, read a conversation's messages and record new ones on its timeline, add and read internal notes, walk a customer's conversation history, and read the user and team directories. Recording a message never delivers it to the customer, and no operation here can: this is a read, write and reporting surface, not a sending one. Responses follow a JSON:API style envelope where every row carries its fields under an attributes object.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Kustomer.Built from the 17 Kustomer tools below, on the connection you add once.

Common Kustomer use cases

  • exporting the customer base
  • routing a conversation to the billing team
  • finding every open conversation tagged as billing
  • walking the conversation stream to build a report
  • summarising a conversation before drafting a reply
  • pushing a new signup from your product into Kustomer
  • marking a conversation done and tagging it for reporting
  • reading what the previous agent wrote before taking over
  • turning an inbound email address into a customer identifier
  • writing a subscription tier onto a customer after an upgrade

What you can do with Kustomer

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Customer, 6 operations

  • create_customerCreate customerPOSTCreates a customer with its emails, phones and custom attributes.
  • get_customerGet customerGETReturns a single customer, optionally with its company embedded.
  • get_customer_by_emailGet customer by emailGETResolves an email address to a customer without searching.
  • list_customersList customersGETLists customers with paging and a sort on creation or update time.
  • search_customersSearch customersPOSTRuns a structured and or not query over any Kustomer resource type.
  • update_customerUpdate customerPUTUpdates a customer's fields, merging into the existing record, except company which is unlinked when omitted.

Conversation, 5 operations

  • create_conversationCreate conversationPOSTOpens a conversation attached to an existing customer.
  • get_conversationGet conversationGETReturns a single conversation with its counters and assignment.
  • list_conversationsList conversationsGETLists conversations across the organisation with paging.
  • list_customer_conversationsList customer conversationsGETLists every conversation belonging to a customer.
  • update_conversationUpdate conversationPUTChanges a conversation's status, priority, tags or assignment.

Message, 2 operations

  • create_conversation_messageCreate conversation messagePOSTRecords a message on a conversation timeline, it never delivers anything to the customer.
  • list_conversation_messagesList conversation messagesGETReads a conversation's messages, filterable by channel.

Note, 2 operations

  • create_conversation_noteCreate conversation notePOSTWrites an internal note on a conversation, invisible to the customer.
  • list_conversation_notesList conversation notesGETReads the internal notes attached to a conversation.

Team, 1 operation

  • list_teamsList teamsGETLists teams and the users that belong to them.

User, 1 operation

  • list_usersList usersGETLists users with their roles, filterable by type and email.

Use Kustomer from Claude Code, Cursor or Codex

Connect Kustomer in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Kustomer operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Kustomer

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Kustomer once

    Add your Kustomer connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Kustomer integration FAQ

What can you do with the Kustomer integration?

LiveContext exposes 17 operations on Kustomer, covering customer, conversation, message and note. Common uses include exporting the customer base, routing a conversation to the billing team and finding every open conversation tagged as billing.

Popular integrations

Browse the whole catalog