Builder.io MCP integration for AI agents.

Connect AI agents to Builder.io through 5 structured actions, including get content, create content, and delete content. Review authentication, inputs, workf…

ACTION CONTRACTS
5
AUTHENTICATION
API key
SOURCE STATUS
Provider-backed

CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE

CAPABILITY PROFILE

What the Builder.io integration exposes

The Builder.io Agent App exposes 5 provider-backed actions for design & media and marketing work. Its current contract lets an authorized agent fetch a single builder.io content entry by model and content id, create a builder.io content entry for a model using the write api, and delete a builder.io content entry by model and content id using the write api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.

A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.

For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Builder.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real Builder.io capabilities.

Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

get_contentREAD

Fetch a single Builder.io content entry by model and content ID.

INPUTS: model / id / publicKey / userAttributes / options

create_contentWRITE

Create a Builder.io content entry for a model using the Write API.

INPUTS: model / name / data / published / query

delete_contentHIGH IMPACT

Delete a Builder.io content entry by model and content ID using the Write API.

INPUTS: model / id

list_contentREAD

List Builder.io content entries for a model using the Content API.

INPUTS: model / publicKey / query / userAttributes / options

update_contentWRITE

Update a Builder.io content entry by model and content ID using the Write API.

INPUTS: model / id / name / data / published

INPUT CONTRACTS

Know what the action needs before it runs.

get_content

modelREQUIRED
The Builder.io model name, such as `page` or `announcement-bar`.
idREQUIRED
The Builder.io content ID.
publicKeyOPTIONAL
The Builder.io public API key for Content API reads. If omitted, the connected private key is used.
userAttributesOPTIONAL
User attributes used by Builder.io targeting when resolving content.
optionsOPTIONAL
Additional Builder.io Content API options.

create_content

modelREQUIRED
The Builder.io model name to create content under.
nameREQUIRED
The human-readable Builder.io content name.
dataREQUIRED
The Builder.io content data object.
publishedOPTIONAL
The Builder.io published state to set on the content.
queryOPTIONAL
A MongoDB-style Builder.io query object. Use Builder.io field names and operators.

delete_content

modelREQUIRED
The Builder.io model name that owns the content entry.
idREQUIRED
The Builder.io content ID to delete.

list_content

modelREQUIRED
The Builder.io model name, such as `page` or `announcement-bar`.
publicKeyOPTIONAL
The Builder.io public API key for Content API reads. If omitted, the connected private key is used.
queryOPTIONAL
A MongoDB-style Builder.io query object. Use Builder.io field names and operators.
userAttributesOPTIONAL
User attributes used by Builder.io targeting when resolving content.
optionsOPTIONAL
Additional Builder.io Content API options.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Get Content

Fetch a single Builder.io content entry by model and content ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

get_content

Control Create Content

Create a Builder.io content entry for a model using the Write API. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.

create_content

Verify with List Content

List Builder.io content entries for a model using the Content API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

list_content

SAFETY BOUNDARY

Operate Builder.io with explicit limits

  • Authorize Builder.io with API key and grant only the provider access required by the selected actions.
  • 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
  • Treat `delete_content` as high-impact operations and require an explicit approval boundary.
  • No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Builder.io rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the Builder.io task completed successfully.

CONNECTION MODEL

API key

Builder.io private API key used with the Authorization Bearer header for Write API requests. Find private and public keys in your Builder.io organization settings: https://builder.io/account/organization.

Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.

READ SIGNALS
2
WRITE SIGNALS
2
HIGH IMPACT
1
REVIEW SIGNALS
0

EVIDENCE AND AVAILABILITY

Provider reference

Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Builder.io.

Official Builder.io website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS