How to Use the Builder.io (Visual CMS) MCP in Claude Code

Q: How do I pipe Builder.io (Visual CMS) data into other CLI tools using the Claude Code MCP integration?

You can ask Claude Code to fetch data using the getcontent tool and output it as raw JSON. This lets you pipe the CMS response directly into tools like jq or redirect it to local files.

Q: Can I run raw GraphQL migrations using Claude Code?

Yes, Claude Code uses admingraphql to run administrative mutations directly from your terminal. This is ideal for schema migrations or bulk content restructuring during CI/CD runs.

Run terminal commands to query, update, and manage your Builder.io visual CMS content and assets instantly with Claude Code.

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 Claude Code

Create your Vinkius account to connect Builder.io (Visual CMS) to Claude Code 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 Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Execute Terminal CMS Queries with Claude Code

The `query_graphql` tool queries your Builder.io database directly from your command-line interface. Claude Code uses this to pull raw JSON payloads, letting you pipe the output directly into local configuration files or terminal tools. When you need to inspect full models, the agent runs `get_content` to dump the schema. It lets you quickly check field types and entry statuses without opening a browser tab.

Script Content Updates via MCP Server

The `update_content` tool modifies live visual entries using structured payloads sent from your terminal. This MCP Server lets Claude Code automate batch updates across dozens of landing pages during a deployment. If you need to spin up fresh marketing pages from a bash script, the agent executes `create_content` with your pre-defined JSON. It makes content generation a repeatable step in your local build pipelines.

Direct Asset Uploads in Claude Code

The `upload_asset` tool uploads images, videos, and documents directly to your Builder.io CDN bucket from your local directory. Claude Code handles the multi-part form upload behind the scenes, returning a clean URL for your scripts to use. To clean up obsolete files, the agent calls `delete_asset_by_url` to purge those media URLs from your CMS. This keeps your asset storage light and organized without manual dashboard hunting.

Setup guide

Set up Builder.io (Visual CMS) MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see builderio-visual-cms-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Builder.io (Visual CMS) transactions." It will automatically discover and invoke the available Builder.io (Visual CMS) tools.

Terminal

claude mcp add --transport http builderio-visual-cms-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Builder.io (Visual CMS) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "builderio-visual-cms-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Claude Code

You can ask Claude Code to fetch data using the `get_content` tool and output it as raw JSON. This lets you pipe the CMS response directly into tools like jq or redirect it to local files.

Yes, you can command Claude Code to run a loop that executes `delete_content` for a list of entry IDs. It processes the deletions sequentially and prints a summary of the deleted entries in your terminal.

You add the server to your Claude Code configuration file using the `claude mcp add` command with your Vinkius endpoint. This configures the secure transport so your automated terminal sessions can access the CMS tools.

Yes, Claude Code uses `admin_graphql` to run administrative mutations directly from your terminal. This is ideal for schema migrations or bulk content restructuring during CI/CD runs.

Your Private API Key is stored securely in your local environment variables or Vinkius vault. The terminal transport layer only passes authorized GraphQL operations and asset payloads, keeping your master credentials completely hidden.

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