Kommunicate for AI agents
Kommunicate is a customer support platform that manages live chat conversations and routes them between human agents and AI bots across a company's support channels. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Kommunicate.
Reply to an open conversation
Send a message into an active support conversation on a customer's behalf.
Approve before reassigning a conversation
Require approval before moving a conversation to a specialist, since reassignment changes who is responsible for the customer.
Check a customer's conversation status
Look up a conversation's current status before deciding whether to escalate it.
6 Kommunicate actions, graded by risk.
Every Kommunicate action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- kommunicate.get_user_detailsGet User Details
write
5Create and change things. Allow, or ask the user first.
- kommunicate.send_messageSend Message
- kommunicate.create_conversationCreate Conversation
- kommunicate.update_user_detailsUpdate User Details
- kommunicate.change_conversation_statusChange Conversation Status
- kommunicate.change_conversation_assigneeChange Conversation Assignee
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Kommunicate in three steps.
- 01Your users connect KommunicateThey add their Kommunicate api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Conversation” can wait for the user to approve.
- 03Any agent can actYour agent calls Kommunicate through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('kommunicate', { read: 'allow', write: 'ask', // create_conversation destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Kommunicate connects.
Users add their Kommunicate api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Kommunicate connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Kommunicate from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Kommunicate and Arc0, answered.
Can I use Kommunicate with Claude, ChatGPT or Cursor?
Yes. Connect Kommunicate to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Kommunicate actions you allow.
How do users connect Kommunicate?
Users add their Kommunicate api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Kommunicate actions can my agent take?
6 in total: 1 read, 5 write and 0 destructive, such as “create Conversation”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Kommunicate?
Yes. Allow read actions and deny writes in the Kommunicate policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Kommunicate too?
Yes. The same Kommunicate connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Kommunicate into your agent.
Your users connect Kommunicate once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan