Inspect available tool groups and learn to test or resolve connection issues with your self-hosted ChatbotX MCP server.
ChatbotX MCP tools are generated dynamically from the system OpenAPI spec. When new APIs are added and the MCP Server is restarted, new tools appear automatically.
| Group | Common Tools |
|---|
| Workspace | get_workspace |
| Channels, Members, Teams | list_channels, list_members, get_member, list_teams |
| Tags | list_tags, create_tag, get_tag, update_tag, delete_tag |
| Custom Fields | list_custom_fields, create_custom_field, get_custom_field, update_custom_field, delete_custom_field |
| Bot Fields | list_bot_fields, create_bot_field, set_bot_fields, bulk_update_bot_fields, get_bot_field, set_bot_field, delete_bot_fields |
| Contacts | list_contacts, create_contact, get_contact, upsert_contact, update_contact, delete_contact, filter_contacts, import_contacts |
| Contact Tags | list_contact_tags, add_contact_tags, remove_contact_tags |
| Contact Custom Fields | list_contact_custom_fields, set_contact_custom_fields, clear_contact_custom_fields, get_contact_custom_field, set_contact_custom_field, clear_contact_custom_field |
| Contact Actions | block_contact, unblock_contact, list_contact_messages, get_contact_message, send_message, send_contact_flow, trigger_auto_reply |
| Conversations and Broadcasts | list_conversations, list_broadcasts, get_broadcast, get_broadcast_audience |
| Automation | list_flows, list_sequences, get_sequence, list_keywords, list_triggers, list_webhooks |
| Other | list_saved_replies, list_template_messages, list_aiagents, list_integrations, list_error_logs |
Testing Connection
Use curl to check whether your ChatbotX MCP Server is reachable:
# For Cloud instances:
curl.exe -i -N --max-time 12 `
-H "x-workspace-token: YOUR_WORKSPACE_TOKEN" `
-H "Accept: text/event-stream" `
"https://app.chatbotx.io/mcp/sse"
# For Self-hosted instances:
# curl.exe -i -N --max-time 12 -H "x-workspace-token: YOUR_WORKSPACE_TOKEN" -H "Accept: text/event-stream" "https://app.yourdomain.com/mcp/sse"
HTTP/1.1 200 OK
Content-Type: text/event-stream
event: endpoint
data: /mcp/messages?sessionId=...
SSE connections stay open. It is normal for the command to stop after the timeout, as long as you see 200 OK and event: endpoint.
Common Issues
| Issue | Common Cause | Fix |
|---|
| Not connected | Token is incorrect or header name is wrong. | Check the token and verify the header is x-workspace-token. See Introduction for details. |
401 or 403 | Token is expired, revoked, or lacks access. | Create a new Workspace token and update client settings. See Introduction for details. |
| AI assistant cannot find tools | Client was not restarted or config syntax is invalid. | Check JSON/TOML configuration syntax and restart your MCP client. |
| ChatGPT cannot see tools | Developer Mode is not enabled or URL token is missing. | Enable Developer Mode and use the ?token=... URL format. |
References
