Kommunicate
Kommunicate is a customer support platform for managing conversations, users, messages, and agent assignments across human and AI support workflows.
Verdict
Common use cases
- Escalate urgent chats to senior agents
- Close resolved tickets in bulk
- Send follow-up messages after hours
- Update customer profiles from CRM data
- Reassign bot conversations to humans
Integration
- Vendor
- Kommunicate
- Category
- communication
- Auth
- API_KEY
- Tools
- 6
- Composio slug
kommunicate
Tools
- Change Conversation Assignee
Assign one Kommunicate conversation to a human agent, changing live routing. By default, this sends a user-visible notification that cannot be undone; it can also remove all AI agents when take_over_from_bot=true.
- Change Conversation Status
Change one Kommunicate conversation to open, closed, or spam. By default, this also sends a user-visible notification message, which cannot be undone; set send_notification=false to suppress it.
- Create Conversation
Create a persistent Kommunicate conversation with the specified members. This can create missing users, add account-default bots or assignees, and cannot be undone through this toolkit; provider business errors are treated as failures even
- Get User Details
Return details for one or more specified Kommunicate user IDs. Requires a non-empty user list and fails on provider business errors even when the HTTP response is successful.
- Send Message
Immediately send one plain-text message to a Kommunicate conversation as a specified user. This is a user-visible, irreversible side effect. Rich messages and attachments are not supported.
- Update User Details
Update selected profile fields for one explicitly identified non-agent Kommunicate user. This mutates persistent user data and fails on provider business errors even when the HTTP response is successful.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and click 'Add MCP'. 2. Select Kommunicate from the list. 3. Log in to your Kommunicate dashboard, navigate to Settings → API, and copy your API key. 4. Paste the key into Switchy's auth prompt and click Connect. 5. Switchy will verify the key and show a green checkmark when the connection succeeds. 6. Open any Project, type '@Kommunicate get user details for user ID <test_user_id>' (replace with a real user ID from your account), and confirm the MCP returns profile data. 7. If the test fails, double-check the API key has read and write permissions in Kommunicate's dashboard. 8. Once verified, you can invoke any of the six tools by @mentioning Kommunicate in a Project prompt.
What teammates see: by default, memories from Kommunicate are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Triage Open Conversations
@Kommunicate list all open conversations, then scan each for words like 'urgent', 'billing', or 'bug'. For any flagged conversation, suggest the best agent to assign based on the topic.
Bulk Close Resolved Tickets
@Kommunicate find all conversations where the last message contains 'resolved' or 'fixed', then change their status to closed without sending a notification. Report how many you closed.
Send After-Hours Update
@Kommunicate send a message to conversation ID <conv_id> as user <user_id> saying 'Thanks for reaching out. Our team will respond first thing tomorrow morning.'
Sync CRM to Chat Profiles
@Kommunicate for user IDs <id1>, <id2>, <id3>, update their display name and email to match the records in our CRM spreadsheet (attached). Confirm each update.
Handoff Bot to Human
@Kommunicate change the assignee for conversation ID <conv_id> to agent <agent_id>, enable take_over_from_bot, and notify the customer that a human is joining the chat.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Kommunicate show me the profile details for users user_12345 and user_67890 so I can see their conversation history and contact info.
Retrieved details for 2 users. User user_12345 (Emma Chen, emma@example.com) joined 14 days ago, has participated in 8 conversations, and is currently active. User user_67890 (Marcus Liu, marcus@example.com) joined 3 months ago with 42 conversations and was last seen 2 hours ago. Both users have default notification preferences enabled and no custom metadata fields set.
This read-only query requires valid Kommunicate user IDs and an API key with user-read scope. The MCP returns structured profile data but will fail silently if the provider returns a business error (invalid ID, deleted user) even when the HTTP call succeeds—always verify IDs exist before querying.
@Kommunicate assign conversation conv_abc123 to agent sarah@company.com and mark it as high priority so our support team can handle this escalation immediately.
Conversation conv_abc123 has been reassigned to sarah@company.com. A system notification was sent to the customer stating 'Your conversation has been assigned to a support agent.' All AI agents were removed from the conversation thread. Note: This action is irreversible through the MCP—the customer has been notified and the routing change is now live in your Kommunicate dashboard.
This write operation immediately changes live conversation routing and sends a user-visible notification that cannot be recalled. The take_over flag defaults to true, removing all bots. Use this for genuine escalations only—accidental reassignments require manual cleanup in the Kommunicate console and may confuse customers who see the notification.
@Kommunicate review all open conversations assigned to bot_support_v2, summarize the top 3 customer pain points, then send a message to conv_priority_001 acknowledging the issue.
I cannot directly list conversations by assignee through this MCP's available tools. However, if you provide specific conversation IDs, I can send messages to them. For conv_priority_001, I can send: 'Thank you for your patience. Our team is investigating the login timeout issue you reported and will follow up within 2 hours.' This message will be irreversible and appear immediately in the customer's chat as the specified sender.
This example reveals a key limitation: the MCP provides message-sending and user-lookup tools but lacks conversation-search or list-by-assignee capabilities. You must obtain conversation IDs from Kommunicate's dashboard or webhooks first. The send-message action is instant and permanent—typos or wrong conversation IDs cannot be undone, so verify targeting before prompting.
Use-case deep-dives
When your bot hits its limit and needs a human
A 6-person support team runs Kommunicate with a bot handling tier-1 questions. When the bot can't resolve a refund dispute, the Kommunicate MCP lets an AI workspace agent reassign the conversation to a human and send a handoff message—all from the same thread where the team is discussing the case. The MCP's "Change Conversation Assignee" and "Send Message" tools make this a two-step operation instead of tab-switching into the Kommunicate dashboard. The trade-off: every reassignment sends a user-visible notification you can't retract, so your team needs a clear escalation protocol before you automate this. If your support flow requires silent triage or bulk reassignments, the MCP's notification defaults will create noise. For small teams doing one-off escalations in Slack or a shared workspace, this is the fastest path from 'bot stuck' to 'human owns it.'
Proactive outreach without leaving your workspace
A 4-person customer success team tracks new signups in a spreadsheet and wants to send personalized check-in messages on day 3 and day 7. The Kommunicate MCP's "Create Conversation" and "Send Message" tools let an AI agent draft and send those messages directly from the team's shared workspace, pulling user IDs from the spreadsheet and posting the outreach without opening the Kommunicate UI. The constraint: messages are plain text only, so if your onboarding flow needs rich cards, GIFs, or attachments, you'll still need the dashboard. The MCP also can't schedule sends—your team will trigger them manually or build a separate reminder system. For teams doing low-volume, text-based outreach where the copy lives in a shared doc and the send happens in real time, this cuts the friction from 'draft in Notion, copy to Kommunicate' to 'send from the workspace.'
Update user records when deals close
A 3-person sales team closes a deal in HubSpot and needs to update the buyer's Kommunicate profile with their new account tier and CSM assignment before the first support conversation. The Kommunicate MCP's "Update User Details" tool lets an AI agent pull the HubSpot data and write it to Kommunicate in one step, so the support team sees the right context when the customer messages in. The MCP requires an explicit user ID—no fuzzy email lookup—so your workspace needs a reliable way to match HubSpot contacts to Kommunicate users, usually via a shared spreadsheet or CRM export. If your sales and support systems don't share a common identifier, you'll spend more time wrangling IDs than the MCP saves. For teams with clean user-ID hygiene and a shared workspace where sales and support collaborate, this is a 30-second profile update instead of a manual dashboard task.
Frequently asked
What does the Kommunicate MCP do in Switchy?
It lets your AI agents read and write Kommunicate conversations, send messages, reassign chats to human agents, and update user profiles. You can automate triage, route support tickets based on intent, or have an agent reply directly to customers. All actions are live and irreversible, so test in a sandbox workspace first.
Do I need admin access to connect Kommunicate?
You need an API key from your Kommunicate dashboard, which typically requires admin or developer permissions. The key grants full read-write access to conversations and users, so only connect it in workspaces where your team should have that level of control. Kommunicate does not support scoped or read-only API keys.
Can the MCP send rich messages or attachments in Kommunicate?
No. The Send Message tool only supports plain text. If you need buttons, carousels, images, or file uploads, you'll have to call Kommunicate's REST API directly or use their native SDKs. The MCP is designed for simple text replies and conversation routing, not rich media workflows.
How is this different from using Kommunicate's API directly?
The MCP wraps six common operations into natural-language tools your AI agents can call without writing code. If you need advanced features like analytics queries, webhook management, or custom bot integrations, you still need the full REST API. The MCP trades flexibility for speed on the 80% use case.
Who on my team should connect this integration?
Whoever owns your Kommunicate account and understands your support routing rules. Because the MCP can reassign conversations and send customer-facing messages, the person connecting it should know which agents or bots should handle which topics. Treat the API key like a support-admin credential, not a read-only dashboard login.