Landbot for AI agents
Landbot is a no-code chatbot builder businesses use to run conversational flows for lead capture and support over chat and WhatsApp. 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 Landbot.
Send a message to a customer
Send a message through a bot's channel to follow up with a customer.
Check a bot's customer list
List customers who have interacted with a bot to review recent conversations.
Approve before deleting a bot
Require approval before deleting a bot, since it removes its flows and channel connections.
13 Landbot actions, graded by risk.
Every Landbot action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- landbot.get_brandGet Brand
- landbot.list_botsList Bots
- landbot.list_agentsList Agents
- landbot.list_channelsList Channels
- landbot.list_customersList Customers
- landbot.list_whatsapp_templatesList WhatsApp Templates
write
6Create and change things. Allow, or ask the user first.
- landbot.send_messageSend Message
- landbot.update_agentUpdate Agent
- landbot.update_brandUpdate Brand
- landbot.replace_agentReplace Agent
- landbot.replace_brandReplace Brand
- landbot.set_agent_statusSet Agent Status
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- landbot.delete_botDelete Bot
Landbot in three steps.
- 01Your users connect LandbotThey add their Landbot api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “send Message” can wait for the user, and “delete Bot” can be denied outright.
- 03Any agent can actYour agent calls Landbot through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('landbot', { read: 'allow', write: 'ask', // send_message destructive: 'deny', // delete_bot }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Landbot connects.
Users add their Landbot 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 Landbot 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 Landbot from any agent.
Landbot and Arc0, answered.
Can I use Landbot with Claude, ChatGPT or Cursor?
Yes. Connect Landbot 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 Landbot actions you allow.
How do users connect Landbot?
Users add their Landbot 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 Landbot actions can my agent take?
13 in total: 6 read, 6 write and 1 destructive, such as “send Message”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Landbot?
Yes. Actions like “delete Bot” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Landbot too?
Yes. The same Landbot connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Landbot into your agent.
Your users connect Landbot once, under your brand. Your agent gets 13 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan