chateapro-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATEAPRO_DRY_RUN | No | When true, every write tool returns the request it would send and makes no call. | false |
| CHATEAPRO_BASE_URL | No | API base. | https://chateapro.app/api |
| CHATEAPRO_API_TOKEN | Yes | Required. Bearer token for the Chatea Pro API. | |
| CHATEAPRO_MAX_RETRIES | No | Retries on HTTP 429/5xx (exponential backoff). | 3 |
| CHATEAPRO_REQUEST_TIMEOUT | No | Per-request timeout (seconds). | 30 |
| CHATEAPRO_ENABLE_BROADCAST | No | Register broadcast_whatsapp_template_by_tag. | false |
| CHATEAPRO_ENABLE_ORDER_WRITE | No | Register update_order_status. | false |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_contactA | Resolve a Pass exactly one of |
| get_contactA | Return the full profile for one contact. |
| list_contactsB | Search contacts by phone / name / email / |
| list_contact_fieldsA | List the custom contact-field definitions (optionally filtered by name).
Use to get exact |
| list_tagsA | List the account's tags (optionally filtered by name). Provides |
| set_contact_fieldA | Set a custom field on one contact. |
| add_contact_tagA | Add a tag to one contact. |
| remove_contact_tagA | Remove a tag from one contact. |
| move_chatA | Move a contact's chat to |
| assign_agentA | Assign a contact's chat to a human agent. |
| assign_agent_groupA | Assign a contact's chat to an agent group. |
| unassign_agentA | Clear the human-agent assignment on a contact's chat. |
| pause_botA | Pause the bot for one contact for |
| resume_botA | Resume the bot for one contact after |
| list_flowsA | List published sub-flows (optionally filtered by name). Provides the exact
|
| list_whatsapp_templatesA | List approved WhatsApp message templates (optionally filtered by name).
Provides |
| trigger_flowA | Send a contact into a sub-flow. |
| send_textA | Send a free-text message to one contact. |
| send_whatsapp_templateA | Send an approved WhatsApp template to one contact. |
| list_ordersA | List shop orders, paginated; pass |
| get_orderA | Return full detail for one order. |
| list_agentsA | List team agents (optionally filtered by name/role). Provides |
| list_agent_groupsA | List agent groups (optionally filtered by name). Provides |
| list_ticket_listsA | List ticket lists / boards (optionally filtered by name). Provides
|
| get_ticket_list_itemsA | List items in one ticket list, paginated; optionally filter by |
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 25 tools
Most tools target distinct resources and actions, and the reference tools (list_*, find_contact) are clearly meant to supply user_ns/IDs for downstream tools. A few retrieval tools could still be confused, especially find_contact versus list_contacts and get_contact, since they all involve searching or resolving contact data.
Every tool follows a consistent verb_noun snake_case pattern: list_*, get_*, set_*, add_*, remove_*, send_*, assign_*, pause_*, resume_*, trigger_*. The verbs map predictably to read/write/action semantics, and plural/singular usage is conventional.
At 25 tools, the surface is at the heavy end and an LLM faces a large action space, even though most lookup tools are necessary ID resolvers. The count is defensible for the multi-domain scope, but it is not as lean as a well-scoped 3-15 tool server.
Core operational flows are covered: resolving contacts, modifying tags/fields, routing chats, pausing/resuming the bot, and sending WhatsApp messages/templates. However, there are notable gaps such as chat history/conversation listing, contact creation/updating beyond custom fields, and any write operations for tickets or orders.