X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Builder.io to Claude

Connect Claude Web, Desktop and Cowork to Builder.io MCP. List draft builder.io page entries, update homepage hero content block, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Builder.io logoBuilder.io
Api Key

Builder.io is a visual development platform for managing content, models, assets, and Space configuration. Use it to ship editable digital experiences faster without waiting on every code change.

10 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Builder.io account to Claude via Composio Connect, enabling it to list draft Builder.io page entries, update homepage hero content block, find assets unused in Builder.io, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Builder.io with

ChatGPTHermesAtomic Agent

Connecting Builder.io to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Builder.io account

Back in Claude, ask it to connect to Builder.io or give it any Builder.io-related task.

For example, ask Claude to:

  • "List draft Builder.io page entries"
  • "Update homepage hero content block"
  • "Find assets unused in Builder.io"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Builder.io account is ready to use.

What is the Builder.io Claude Connector, and what's possible with it?

The Builder.io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Builder.io account. It provides structured and secure access so your agent can perform Builder.io operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Builder.io?

The connector can show as connected, but Claude must use it in each Builder.io conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Builder.io again.

2. Why does Claude show an MCP server error before Builder.io connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Builder.io.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Builder.io.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Builder.io authorization link not work?

The Composio connector is one server. Your Builder.io account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Builder.io connection.
  • Composio creates a fresh Builder.io authorization link.
  • Open that link in your browser and finish the Builder.io sign-in.

4. Why do Builder.io actions fail after they worked before?

The Builder.io connection can expire or lose permission.

  • Ask Claude to inspect the Builder.io connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Builder.io account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Builder.io.
  • If the action still fails with a permission error, check that the connected account has that permission in Builder.io itself.

5. How do I switch to a different Builder.io account?

Claude can manage the Builder.io connection for you.

  • Ask Claude to disconnect or delete the current Builder.io account.
  • Ask Claude to connect Builder.io again.
  • Open the new Composio authorization link for Builder.io.
  • Sign in with the other Builder.io account in the browser.
  • After the account connects, ask Claude to retry the Builder.io task.

6. Why is my Builder.io connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Builder.io connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Builder.io tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Builder.io.
TOOLS

Supported Tools

Every Builder.io action and event your agent gets out of the box.

Create Content Entry

Create a draft, published, or archived entry in an existing Builder.

Delete Content Entry

Delete one Builder.

Get Content Entry

Retrieve one content entry by model name and entry ID from the connected Builder.

Get Space Details

Return the authenticated Builder.

List Assets

List, filter, and sort assets in the connected Builder.

List Content Entries

List and filter content entries from any model in the connected Builder.

List Content Folders

List the content folders configured in the connected Builder.

List Models

List the content models in the connected Builder.

List Space Users

List users and roles with access to the connected Builder.

Update Content Entry

Partially update an existing Builder.

FRAMEWORKS

How to build Builder.io MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Builder.io MCP with ChatGPT

Hermes logo

Hermes

Use Builder.io MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Builder.io MCP with Atomic Agent

FAQ

Frequently asked questions

With a standalone Builder.io MCP server, the agents and LLMs can only access a fixed set of Builder.io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Builder.io and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Builder.io tools.

Yes, absolutely. You can configure which Builder.io scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Builder.io data and credentials are handled as safely as possible.

Start with Builder.io.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Builder.io tool your agent needs.Free to start.

Start building