Builder.io
Builder.io is a visual development platform for delivering, managing, and programmatically updating content, models, assets, and Space configuration.
Verdict
Common use cases
- Draft landing pages from campaign briefs
- Bulk-update product announcements across models
- Audit published content for broken links
- Generate A/B test variations of hero sections
- Export content entries for compliance review
Integration
- Vendor
- Builder.io
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
builder_io
Tools
- Create Content Entry
Create a draft, published, or archived entry in an existing Builder.io model. New entries default to draft and trigger configured webhooks unless trigger_webhooks is false.
- Delete Content Entrydestructive
Delete one Builder.io content entry by model name and entry ID. Builder's Content API is CDN-cached, so reads may briefly return stale content after a successful deletion. Configured webhooks run unless trigger_webhooks is false.
- Get Content Entry
Retrieve one content entry by model name and entry ID from the connected Builder.io Space. Set cachebust only for a one-off freshness check because normal Content API reads use Builder's CDN cache.
- Get Space Details
Return the authenticated Builder.io Space ID and its read-only settings.
- List Assets
List, filter, and sort assets in the connected Builder.io Space without modifying the Asset Library. Returns one offset-controlled page at a time.
- List Content Entries
List and filter content entries from any model in the connected Builder.io Space, one offset-controlled page at a time.
- List Content Folders
List the content folders configured in the connected Builder.io Space.
- List Models
List the content models in the connected Builder.io Space, optionally including each model's field schema for content discovery.
- List Space Users
List users and roles with access to the connected Builder.io Space.
- Update Content Entry
Partially update an existing Builder.io content entry. Omitted top-level fields remain unchanged, but a supplied data object replaces the existing data object rather than recursively merging with it. Configured webhooks run unless trigger_w
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration,' search for Builder.io, and select it. 3. In a new browser tab, log into your Builder.io account, open Space Settings, and copy your Private API Key from the API Keys section. 4. Paste the key into Switchy's auth prompt and click Connect. 5. Switchy will confirm the connection by fetching your Space ID and model list. 6. Open any Project, type '@Builder.io list models' in the chat, and verify the assistant returns your content models. 7. To create or update entries, ensure your API key has write permissions in Builder.io's key settings.
What teammates see: by default, memories from Builder.io are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Models
@Builder.io list all models in my Space and include the field schema for each one
Create Landing Page Draft
@Builder.io create a draft page entry in the 'landing-page' model with the title 'Spring Sale 2025' and a hero headline 'Save 30% on All Plans'
Find Unpublished Entries
@Builder.io list all entries in the 'blog-post' model where the published state is 'draft' and sort by last modified date
Update Entry Field
@Builder.io update the entry with ID 'abc123' in the 'announcement' model and change the 'expiresAt' field to '2025-06-30'
Delete Archived Content
@Builder.io delete the content entry with ID 'xyz789' from the 'promo-banner' model and do not trigger webhooks
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@builder list all published blog posts from the last 30 days and show me their titles, authors, and view counts
Found 12 published blog posts in your Builder.io space from the past month. The top performers include 'Migrating to Headless CMS' (Sarah Chen, 4,200 views), 'Visual Editing Best Practices' (Mike Torres, 3,800 views), and 'A/B Testing Landing Pages' (Jordan Lee, 2,900 views). The remaining nine posts averaged 1,400 views each. All entries use the 'blog-post' model and include featured images stored in your asset library.
This example demonstrates read-only content discovery across a date range. The MCP queries Builder's Content API, which is CDN-cached—expect up to 60 seconds of staleness unless you explicitly request a cache-bust. Requires a valid API key with read permissions on the target model.
@builder create a new landing page entry called 'Spring Sale 2025' in draft mode with a hero section and CTA button pointing to /products/sale
Created draft content entry 'Spring Sale 2025' in your 'landing-page' model (ID: a3f8c2d1). The entry includes a hero block with placeholder text and a CTA button configured to link to /products/sale. Because this is a draft, it won't appear on your live site until you publish it through Builder's visual editor or update its status via the API. No webhooks were triggered during creation.
This write operation shows how the MCP can scaffold new content entries. The entry starts in draft state by default, giving your team time to refine layout and copy in Builder's visual editor before publishing. If your space has webhook automations configured, be aware they'll fire on publish unless you disable trigger_webhooks.
@builder review all unpublished product pages, summarize their completion status, and recommend which three are ready to publish based on required fields
Scanned 18 unpublished entries in your 'product-page' model. Three are publish-ready: 'Wireless Headphones Pro' (all fields complete, images optimized), 'Ergonomic Desk Chair' (SEO metadata present, A/B test configured), and 'Standing Desk Converter' (full product specs, customer reviews embedded). The remaining 15 entries are missing required fields—most commonly product descriptions (9 entries) and pricing data (6 entries). I recommend publishing the three complete pages first, then prioritizing the description backlog.
This synthesis example pairs Builder's list-and-filter capabilities with AI reasoning to triage content. The MCP fetches entry metadata and field values, then the AI evaluates completeness against your model schema. Useful for editorial workflows, but remember the AI can't validate business rules (pricing accuracy, legal copy) that live outside Builder's data model.
Use-case deep-dives
When Builder.io MCP beats manual CMS logins for content teams
A 3-person marketing team ships landing pages weekly and needs to update hero copy, CTAs, and feature blocks without waiting on engineering. The Builder.io MCP is the right call here because it exposes Create Content Entry and List Content Entries—your AI can draft new page variants or update existing entries in seconds, then publish them directly to the model. The trade-off: if your content workflow requires visual layout changes or drag-and-drop component edits, the MCP won't help—those still need Builder's visual editor. But for text-heavy updates across dozens of pages (pricing tiers, product descriptions, blog intros), the MCP turns a 20-minute login-and-click ritual into a 30-second prompt. Connect it if your team touches Builder content daily and the bottleneck is typing, not designing.
How the Builder.io MCP handles multi-language content at scale
A 6-person product team ships a SaaS app in 8 languages and stores localized strings as Builder entries (one model per locale). The MCP wins when you need to bulk-create or update entries across models—List Models and Create Content Entry let your AI loop through locales and push translated copy in one session. The boundary: if your translation workflow lives in a separate TMS (Phrase, Lokalise), the MCP doesn't bridge that gap—you'll still export/import CSVs. But if your translations land in Slack or a shared doc and you want to push them to Builder without opening 8 browser tabs, the MCP cuts the publish step from 40 minutes to under 5. It's overkill for teams with fewer than 4 locales or infrequent releases; it's a must-have once you're shipping weekly in double-digit languages.
When to use the Builder.io MCP for media governance
A 2-person design ops team manages 1,200+ images and videos in Builder's Asset Library and needs to identify orphaned files before a storage-tier upgrade. The List Assets tool returns paginated metadata (tags, upload dates, URLs), so your AI can flag assets unused in any content entry by cross-referencing List Content Entries. The catch: the MCP doesn't expose asset deletion or bulk tagging—you'll still log into Builder to act on the audit results. This scenario makes sense if your asset count is over 500 and you run quarterly cleanups; below that threshold, a manual skim is faster. The MCP turns a 3-hour spreadsheet exercise into a 10-minute prompt, but only if you're comfortable scripting the cross-reference logic or letting the AI do it. Connect it when asset sprawl is a recurring ops tax, not a one-time spring cleaning.
Frequently asked
What does the Builder.io MCP let me do in Switchy?
It connects your Builder.io Space so AI agents can create, read, update, and delete content entries across your models, browse the Asset Library, and inspect model schemas. Agents can draft new pages, publish updates, or archive old content without opening the Builder dashboard. All operations respect your Space's existing webhooks and CDN cache.
Do I need a specific Builder.io plan or role to connect it?
You need an API key with write access to your Builder.io Space. Builder issues private keys under your Space settings; any admin can generate one. The MCP doesn't use OAuth, so you paste the key once during setup. If your team restricts API key creation, ask whoever manages your Builder account to provision one for Switchy.
Can the MCP edit visual layouts or just content fields?
It manipulates content entries—the structured data inside your models—not the drag-and-drop visual editor. If your model has a rich-text field or JSON blocks, the agent can update those values, but it won't rearrange components in Builder's canvas. For layout changes, you still open the Builder UI or use the Visual Editor API separately.
Why use this instead of Builder's Content API directly?
The MCP wraps Builder's Content API in natural-language tools, so your team describes what they want—"archive all blog posts tagged 'deprecated'"—and the agent translates that into the correct API calls, pagination, and error handling. You skip writing scripts or remembering endpoint syntax. The trade-off is you're limited to the ten tools the MCP exposes.
Who on the team should connect the Builder.io MCP?
Whoever owns your content operations or has admin access to your Builder Space. They'll generate the API key and paste it into Switchy. After that, any Switchy user with MCP permissions can invoke the tools. If multiple people manage Builder, one connection is enough—Switchy doesn't create per-user API keys for this integration.