How to Use the Builder.io (Visual CMS) MCP in Mastra AI

Q: How do I register the Builder.io (Visual CMS) MCP Server in Mastra AI?

You initialize the MCPClient from @mastra/mcp and point it to your Vinkius server URL. Then, call mcpClient.listTools() and spread those tools directly into your Mastra agent configuration. This gives your workflows instant access to all nine Builder.io tools.

Q: Can Mastra AI handle conditional branching for Builder.io (Visual CMS) updates?

Yes, you can write workflows that use getcontent to inspect a page's status before deciding what to do. If the page is in draft, the workflow can run updatecontent; if it is published, the agent can branch to create a new revision instead.

Q: How do retries work when deleting Builder.io (Visual CMS) assets in Mastra AI using this MCP?

When using deleteassetbyurl, Mastra's workflow engine manages the execution lifecycle. If the Builder.io API returns a transient error, the engine uses exponential backoff to retry the deletion. This ensures your media library does not end up cluttered with orphaned files.

Q: Does this MCP Server support human-in-the-loop validation with Mastra AI?

Yes, you can use Mastra's requireToolApproval config on high-risk tools like admingraphql or deletecontent. The workflow will pause and generate a review request, executing the GraphQL mutation only after a human grants permission.

Build resilient, self-healing Mastra AI workflows that automatically update and govern your Builder.io (Visual CMS) models.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Builder.io (Visual CMS) MCP to Mastra AI

Create your Vinkius account to connect Builder.io (Visual CMS) to Mastra AI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Builder.io (Visual CMS) with Mastra AI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Resilient schema updates via MCP Server

The `update_content` tool modifies existing Builder.io content entries within your Mastra AI workflows. If a layout update fails due to a network hiccup, Mastra's built-in retry engine automatically backs off and retries the operation. This keeps your visual CMS in sync even during API rate limits. You can configure conditional steps that check the update status before proceeding. If the update succeeds, the workflow automatically triggers downstream notifications or publishes the changes.

Safe content deletion with human approval

The `delete_content` tool removes entries from your Builder.io models, but you can gate this behind Mastra's human-in-the-loop approval system. Your agent prepares the deletion payload, pauses the workflow, and waits for an admin to confirm the action. This prevents accidental data loss when cleaning up stale promotional pages. Once approved, the agent executes the deletion and cleans up associated media using `delete_asset_by_url`.

Automated visual layout generation

The `create_content` tool generates brand new visual layouts in Builder.io using JSON payloads built by your agents. Mastra AI organizes these creations into multi-step pipelines, ensuring that page metadata is generated and validated before the layout goes live. If the generated layout fails validation, the agent can branch to a correction step. This self-healing loop guarantees that only syntactically correct visual blocks make it into your production CMS.

Setup guide

Set up Builder.io (Visual CMS) MCP in Mastra AI

Prerequisites

Node.js 18+ and a TypeScript project
@mastra/mcp + @mastra/core packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run npm install @mastra/mcp @mastra/core plus your preferred model provider (e.g. @ai-sdk/openai).
2

Configure the MCPClient
Create an MCPClient with your Vinkius endpoint as a URL object. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and inject tools
Call mcpClient.listTools() and spread the result into your agent's tools object. All Builder.io (Visual CMS) tools become native Mastra tools.
4

Run with any model
Swap openai("gpt-4o") for any AI SDK-compatible provider. Call agent.generate() and the agent routes tool calls through MCP automatically.

agent.ts

import { MCPClient } from "@mastra/mcp";
import { Agent } from "@mastra/core/agent";
import { openai } from "@ai-sdk/openai";

const mcpClient = new MCPClient({
  id: "builderio-visual-cms-mcp-client",
  servers: {
    "builderio-visual-cms-mcp": {
      url: new URL(
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
      ),
    },
  },
});

const agent = new Agent({
  name: "Builder.io (Visual CMS) Agent",
  model: openai("gpt-4o"),
  instructions: "You have access to Builder.io (Visual CMS) tools.",
  tools: {
    ...(await mcpClient.listTools()),
  },
});

const result = await agent.generate(
  "List recent Builder.io (Visual CMS) transactions"
);
console.log(result.text);

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Builder.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Builder.io (Visual CMS) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Builder.io (Visual CMS) MCP in Mastra AI

You initialize the `MCPClient` from `@mastra/mcp` and point it to your Vinkius server URL. Then, call `mcpClient.listTools()` and spread those tools directly into your Mastra agent configuration. This gives your workflows instant access to all nine Builder.io tools.

Yes, you can write workflows that use `get_content` to inspect a page's status before deciding what to do. If the page is in draft, the workflow can run `update_content`; if it is published, the agent can branch to create a new revision instead.

When using `delete_asset_by_url`, Mastra's workflow engine manages the execution lifecycle. If the Builder.io API returns a transient error, the engine uses exponential backoff to retry the deletion. This ensures your media library does not end up cluttered with orphaned files.

Yes, you can use Mastra's `requireToolApproval` config on high-risk tools like `admin_graphql` or `delete_content`. The workflow will pause and generate a review request, executing the GraphQL mutation only after a human grants permission.

All data payloads, including visual JSON and asset URLs, pass through encrypted SSE or HTTP transports. The Vinkius runtime isolates your Builder.io credentials inside a zero-trust sandbox. Your Mastra agents never expose your private API keys to the LLM or third-party logging providers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript