Kustomer MCP servernew

The Kustomer MCP server is a hosted Model Context Protocol server. Connect an AI assistant to it, sign in with your Kustomer account, and the assistant can search and read your org's customers, conversations, messages, custom objects, teams and workflows, with your permissions. There's nothing to install or run on your machine.

sequenceDiagram
  autonumber
  participant You
  participant Agent as AI assistant (Claude, ChatGPT, Cursor, …)
  participant MCP as Kustomer MCP server
  participant K as Your Kustomer org
  You->>Agent: "Find the most recent conversations for john@example.com"
  Agent->>MCP: tools/call search-customers
  MCP->>K: Search as you
  K-->>MCP: Matching customer
  Agent->>MCP: tools/call search-conversations
  MCP->>K: Search as you
  K-->>MCP: Conversations
  MCP-->>Agent: Results
  Agent-->>You: Three conversations, the newest about order 4417

Before you start

1. Install the app in Kustomer

   An admin installs the Kustomer MCP server app once per org: open the Application Store from the left navigation, search for Kustomer MCP server, and select Install. Until it's installed, sign-in from any AI client fails with an error saying the app must be installed first.

2. Check your AI client

   The server completes sign-in only for approved clients. ChatGPT needs an Enterprise or admin-level workspace, and Claude an admin-level workspace, because a workspace admin adds the connector for everyone.

Connect a client

Every client follows the same pattern: add a server with the URL above and OAuth as the authorization type, sign in to Kustomer when prompted, pick the org, and grant the requested permissions.

@Kustomer MCP Find the most recent conversations for customer john@example.com.

claude mcp add --transport http kustomer https://server.mcp.kustomerapp.com/mcp

{
  "mcpServers": {
    "kustomer": {
      "url": "https://server.mcp.kustomerapp.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "kustomer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://server.mcp.kustomerapp.com/mcp"]
    }
  }
}

Approved clients

Local clients sign in through a localhost callback on your own machine, so any client that works that way is accepted. If a hosted platform you use isn't listed, contact Kustomer support before connecting it.

Connect more than one org

https://server.mcp.kustomerapp.com/mcp connects one org at a time, chosen on the sign-in screen. To stay signed in to several orgs at once, for example as an agency or with several brands, add one server per org with its own URL:

https://server.mcp.kustomerapp.com/orgs/<org-slug>/mcp

<org-slug> is the org's Kustomer subdomain, in lowercase. Each org needs the app installed, and the org you pick when signing in must match the slug in the URL. Name each server after its org so the assistant can tell them apart.

Tools

Every tool reads. Results are trimmed to the fields an assistant needs, and lists are paged.

The search-field tools tell the assistant which fields it can filter and sort on, including your org's custom attributes, so it can build a search instead of guessing field names. Your client always shows the current list, which can grow between releases.

The server also offers prompts, which clients that support them show as templates or slash commands: customer-support-workflow, conversation-analysis, escalation-recommendation, customer-health-analysis and sla-compliance-monitoring.

Permissions and safety

• It acts as you. Each person signs in with their own Kustomer account, and tools see only what that user can see. There are no shared keys to manage.
• It's read-only. No tool creates, updates or deletes anything in Kustomer.
• Orgs stay separate. A session is bound to the org it signed in to. A sign-in for one org is rejected on another org's URL.
• Admins decide. Nobody in an org can connect a client until an admin installs the app.

Troubleshooting

Related