How to integrate Builder.io MCP with Codex

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Builder.io MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

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

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Builder.io MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Builder.io with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Builder.io MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Builder.io MCP server, 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 to your content, models, assets, folders, Space settings, and users, so your agent can discover models, manage content entries, browse assets, review folders, and inspect Space access on your behalf.

  • Content creation and publishing: Have your agent create new content entries in existing models and save them as drafts, publish them, or archive them.
  • Content discovery and review: Instruct your agent to find content entries within any model, apply useful filters, and retrieve a specific entry for review.
  • Content updates and cleanup: Direct your agent to revise existing content entries or delete content that is no longer needed.
  • Model, asset, and folder exploration: Let the agent list your content models and their fields, browse and sort assets, and review how content folders are organized.
  • Space settings and access visibility: Have your agent review read-only Space settings and list the users and roles that have access.

Conclusion

You've successfully integrated Builder.io with Codex using Composio's MCP server. Now you can interact with Builder.io directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Builder.io operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Builder.io operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities
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.

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. Codex 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