otherapi_key

Builder.io

Builder.io is a visual development platform for delivering, managing, and programmatically updating content, models, assets, and Space configuration.

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 Entry
    destructive

    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

  1. Create or open a Switchy Project.
  2. Open Integrations and connect Builder.io.
  3. Authorise through api_key. Switchy stores the connection against your org.
  4. Everyone in the Project can now @-mention the Builder.io tools in chat.

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

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Starter prompts for this model will land here soon.

More other MCPs

See all other MCPs

Data last verified 7 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.