kustomer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUSTOMER_TOKEN | Yes | The access token for the Kustomer Suite API. | |
| KUSTOMER_API_URL | Yes | The base URL of the Kustomer Suite API. | |
| KUSTOMER_STORE_ID | Yes | The ID of the store the token is bound to. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_conversationsA | List the store's customer conversations, newest activity first. Use handover_status=pending to find customers waiting for a human. Returns a preview of the last message; call get_conversation for the full thread. |
| get_conversationA | Read one conversation with its messages, oldest first. Bot replies carry how they were produced: response_source (rag, function_calling, template, tool_error, handover...), the knowledge base titles used, and the bot's confidence score. The server asks the API not to mark the conversation as read (mark_read=false). Known limitation: the Kustomer Suite API does not honor that yet, so reading marks the messages as read for the store's agents. |
| search_knowledgeA | Search the store's knowledge base the way the bot does before answering, and return the closest passages with their similarity (0-1). Use it to find out why the bot answered something, or whether the knowledge base covers a question at all. |
| get_tool_callsA | Read the calls the bot made to the store's own tools (room availability, order status, checkout...): which tool, with which arguments, whether it failed and how. Use conversation_id to see every call behind one conversation. Request and response bodies are never returned, because they can hold credentials. |
| get_usageA | Read the store's usage for the current billing period: conversations and messages per channel against the plan's limits, and AI tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource: conversations (list vs. single-thread read), knowledge base search, bot tool-call logs, and billing usage. The list/get conversation pair is clearly delineated in the descriptions (preview vs. full thread), and no two tools could be reasonably confused.
All five tools follow a strict verb_noun snake_case pattern: get_conversation, list_conversations, search_knowledge, get_tool_calls, get_usage. The verb choice also matches the operation semantics (list for collections, get for single resources).
Five tools is a tight, well-scoped surface for a read-only observability/debugging server; every tool maps to a distinct investigative question (what was said, what was retrieved, what tools fired, what it cost). Nothing feels padded or missing at the count level.
The surface covers the core diagnostic loop: find a conversation, read it, verify what knowledge was used, inspect bot tool calls, and check usage. Gaps are minor for a read-only server—no ability to reply, change handover status, or filter conversations by customer/date—but agents can work around these by escalating elsewhere.