Landbot

npx add-mcp 'https://mcp.landbot.io/mcp'

MCP server

Connect Claude, Codex and other AI assistants to your Landbot account, so they can build, edit, test and publish your bots for you.

Beta The Landbot MCP server is in beta. Tools and their behaviour may still change.

The Landbot MCP server lets an AI assistant work with your bots through the Model Context Protocol. You describe the bot you want in plain words, and the assistant reads the block catalog, creates the bot, wires its blocks, and deploys it to test or publishes it once you say so.

https://mcp.landbot.io/mcp

It uses the Streamable HTTP transport and OAuth: there is no token to copy. The first time you connect, your client opens Landbot's login (password or Google) and a consent screen. From then on the assistant acts with your account's permissions, on your brand. If you don't have a Landbot account yet, you can sign up from that same screen.

Note This is not the docs MCP at https://dev.landbot.io/mcp described in For AI agents, which only searches and reads these docs.

Supported clients

Client	How to connect
claude.ai	Custom connector
Claude Code	claude mcp add
Codex	codex mcp add

claude.ai

1. Go to Settings → Connectors → Add custom connector.
2. Name it Landbot and paste https://mcp.landbot.io/mcp.
3. Click Connect, log in with your Landbot account and approve.

On Team and Enterprise plans, an Owner adds the connector once for the whole organization. Each member then finds Landbot under Settings → Connectors and clicks Connect.

Claude Code

claude mcp add --transport http landbot https://mcp.landbot.io/mcp

Then run /mcp in Claude Code, pick landbot and log in.

Codex

codex mcp add landbot --url https://mcp.landbot.io/mcp
codex mcp login landbot

Permissions

The consent screen asks for these scopes:

Scope	Allows
bots:read	List and read your bots, their drafts and the block catalog
bots:write	Create and edit bots, deploy them to test and publish them
agents:read	Read the AI agents your bots run
agents:write	Create, edit and publish the AI agents your bots run
integrations:read	List the accounts connected to your integrations, the spreadsheets, tabs and columns a Google account reaches, and a Calendly account's event types
integrations:write	Ask for another account to be connected, through a link you open in your browser
channels:read	Read how your web chats look
channels:write	Change how your web chats look

What it can do

Group	Tools
Read	list_bots, get_bot, get_bot_draft, list_blocks, get_block_definition
Build	create_bot, update_bot, add_draft_blocks, update_draft_block, delete_draft_block, apply_draft_changes, replace_draft
AI agents	get_ai_agent_schema, get_ai_agent, create_ai_agent, save_ai_agent_draft
Integrations	list_connected_accounts, start_account_connection, get_account_connection, list_spreadsheets, list_sheets, list_sheet_columns, list_calendly_event_types
Web chat look	get_web_chat, update_web_chat
Test and publish	deploy_draft_to_test, publish_bot, publish_ai_agent

Tools that change something ask for your approval in the client, and the assistant only deploys a bot to test or publishes it after you say yes.

Google Sheets, SendGrid and Calendly blocks go through an account connected to your brand. When none will do, the assistant gives you a link: open it in your browser, signed in to Landbot, and consent at Google or Calendly, or enter the SendGrid sender and API key there. Your passwords and keys never pass through the conversation.

Example prompts

List my Landbot bots.

Build a Landbot bot that greets the visitor, asks for their email and says goodbye.

Add a rating question at the end of my bot "Support", then deploy it to test.

Build a bot that asks for a name and an email and saves them as a new row in my Google Sheet.