Read tools work with a read token. The two marked write need a write token.
list_conversationsOpen, pending, unread or assigned to you, newest firstget_conversationThe contact, channel, status and labels of one conversationlist_messagesRead a conversation, both sidesadd_internal_notewriteLeave a note the customer never seessearch_contactsFind people by name or email, or by scoreget_contactFields, tags, segments and channels of one contactlist_tagsThe tags of the workspacetag_contactwriteAdd or remove a tag, which can start an automationlist_automationsEvery automation with its trigger and statusget_impact_summaryConversations, replies, leads and recorded sales, no estimatesget_workspaceThe workspace the server is connected toIn Settings > Developers, create a personal access token. Read only reads; write also leaves notes and tags.
The same page shows your workspace's MCP address, ready to copy.
Paste the URL and the token into Claude Code, Cursor or VS Code. The tools appear in the assistant right away.
claude mcp add --transport http chatinflow https://api.chatinflow.com/api/v1/workspaces/your-workspace/mcp --header "Authorization: Bearer YOUR_TOKEN"Settings > Developers fills in your workspace's address. Replace YOUR_TOKEN with your personal access token.
A read token can only read. Contacts or inbox tokens see only those. You can revoke a token at any time.
Roles, inbox visibility, plan limits and rate limits apply to every tool call, exactly as they do in the API.
No tool sends a DM. The assistant can draft a reply; a person on your team sends it.
Short answers about what the MCP server can reach, which assistants work and what it costs.
ศูนย์ช่วยเหลือMCP server
Create a token, copy your server URL and your assistant can read your DMs, contacts and automations in a minute.