superchat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPERCHAT_API_KEY | No | Your Superchat API key; required for API calls. | |
| SUPERCHAT_TIMEOUT_MS | No | Total request deadline, including retries/body reading; valid range 1–300000 ms. | 30000 |
| SUPERCHAT_MAX_RETRIES | No | Maximum GET retries after the first attempt; valid range 0–5. | 2 |
| SUPERCHAT_ENABLE_WRITES | No | Register the write tools. Accepts only 'true' or 'false'. | false |
| SUPERCHAT_ENABLE_DELETES | No | Register delete tools; requires writes to be enabled. Accepts only 'true' or 'false'. | false |
| SUPERCHAT_ENABLE_ENTERPRISE_TOOLS | No | Register the Enterprise message-history tool. Accepts only 'true' or 'false'. | 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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| superchat_get_meA | Identify the Superchat user associated with this API key. Use this to confirm which account the server is connected to. |
| superchat_list_channelsA | List one page of connected channels in this workspace, such as WhatsApp, Instagram Direct, Facebook Messenger, SMS, email, Telegram, Live Chat or phone. Use a returned channel_id when sending. Use after or before to continue from a previous page; each call returns only one page. |
| superchat_get_channelA | Read one connected channel's configuration by ID, for example before choosing a channel for a message. |
| superchat_list_inboxesA | List one page of inboxes that organize conversations in this workspace. Use inbox IDs when routing a conversation. Use after or before to continue from a previous page; each call returns only one page. |
| superchat_get_inboxA | Read one inbox's details by ID. |
| superchat_list_usersA | List one page of workspace users. Use their IDs when assigning conversations. Use after or before to continue from a previous page; each call returns only one page. |
| superchat_get_userA | Read one workspace user's details by ID. |
| superchat_list_labelsA | List one page of labels used to organize conversations. Labels belong to conversations, not contacts. Use after or before to continue from a previous page; each call returns only one page. |
| superchat_get_labelA | Read one conversation label by ID. Labels apply to conversations, not contacts. |
| superchat_list_contact_listsA | List one page of contact lists used to group contacts for segmentation and campaigns. Results contain list metadata (ID, name and URL), not participants; use list_contact_lists_for_contact to find a contact's memberships. Use after or before to continue from a previous page; each call returns only one page. |
| superchat_get_contact_listA | Read a contact list's metadata (ID, name and URL) by ID. This endpoint does not return participants; use list_contact_lists_for_contact for a contact's memberships. |
| superchat_list_filesA | List one page of metadata for files already uploaded to Superchat. Use file IDs for message attachments; this does not download file contents. Use after or before to continue from a previous page; each call returns only one page. |
| superchat_get_fileA | Read metadata for one uploaded file by ID. This does not download its contents. |
| superchat_list_custom_attributesA | List one page of custom contact attributes with their IDs, types and allowed values. Look up an attribute ID here before searching by or updating that attribute. |
| superchat_list_templatesA | List one page of message templates. Filter by channel_id or template type, then inspect approval status and positional variables before sending a template. |
| superchat_get_templateA | Read one template's content, approval status and positional variables before sending it. Use this instead of list_templates when you already have the template ID. |
| superchat_list_contactsA | List one page of contacts, newest first. For an exact email, phone, Instagram or custom-attribute match, use search_contacts instead of scanning pages. |
| superchat_get_contactA | Read one contact's details, handles and custom attributes by ID. Use this before update_contact because supplied handle and attribute arrays replace their full lists. |
| superchat_search_contactsA | Find contacts with one exact equality match on email, phone, Instagram ID or a custom attribute. This is a read-only POST; it does not support fuzzy name search or combining conditions. Use list_contacts to browse instead. |
| superchat_list_contact_conversationsA | List one page of conversation threads for a contact across its channels. Results are conversation records, not message history; use list_conversation_messages for messages when Enterprise access is enabled. |
| superchat_list_contact_lists_for_contactA | List one page of contact lists that contain this contact. Use this to inspect membership; list_contact_lists and get_contact_list return only list metadata, not participants. |
| superchat_list_conversationsA | List one page of conversation threads across the workspace. Results contain conversation metadata, not messages, and the public endpoint has no status, inbox or text filter. Use list_contact_conversations to scope the list to one contact. |
| superchat_get_conversationA | Read one conversation thread's contact, channel, inbox, status and channel-specific messaging time window. Use list_conversation_messages for its message history when Enterprise access is enabled. Conversation status (such as open) does not determine whether a channel's messaging window is open. |
| superchat_list_conversation_notesA | List one page of internal notes attached to a conversation. These notes are visible to the team, not customer messages; use list_conversation_messages for message history when Enterprise access is enabled. |
| superchat_get_conversation_noteA | Read one internal note from a conversation by note ID. This does not retrieve a customer message. |
| superchat_get_conversation_exportA | Check the status of an asynchronous conversation export job and retrieve its download link. Use after create_conversation_export; this tool returns the URL but does not fetch or parse the file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| superchat_guide | Workflow, pagination, permissions and messaging semantics. |
TDQS
Scored across 26 tools
Each tool targets a distinct resource or granularity (list vs get vs search), and potentially confusable pairs like list_contact_lists vs list_contact_lists_for_contact are explicitly disambiguated in the descriptions. No two tools appear to do the same thing.
Every tool follows the same superchat_<verb>_<noun> pattern with snake_case throughout, using get_ for single-item reads, list_ for paginated reads, and search_ for the one query operation. The naming is predictable and consistent.
26 tools is above the threshold where a tool set becomes too large for easy navigation, and most are simple one-resource list/get pairs that could be consolidated into parameterized read operations. The count adds cognitive load without a matching increase in capability.
The set is entirely read-only: there are no tools to send messages, update contacts, manage conversations, or create/update/delete any resource. The export-status tool even references create_conversation_export, which is not present, creating a dead end and leaving core Superchat workflows unusable.