How to Use the Builder.io MCP in Claude
Edit your Builder.io visual CMS pages and spaces directly from Claude Desktop without leaving your chat window.
Works with every AI agent you already use
…and any MCP-compatible client
Connect Builder.io MCP to Claude Desktop
Create your Vinkius account to connect Builder.io to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Manage Builder.io content inside Claude Desktop
The `get_content_entry` tool lets your agent pull your actual Builder.io JSON structures straight into your local Claude Desktop app. You don't have to bounce back and forth between browser tabs just to see what field values are currently live. When you need to push updates, `update_content_entry` handles the payload delivery directly from your chat prompt. This local MCP Server connection keeps your visual CMS updates fast and securely tied to your desktop environment.
Map your visual CMS models using this MCP Server
Your agent calls `list_models` and `get_model` to map out your Builder.io data schemas in real-time. This means Claude Desktop understands your exact content structures before you write a single line of layout code. If you manage multiple environments, `list_spaces` and `get_space` let you switch context instantly without hunting for API keys. Your agent keeps track of which space is active so you never push a staging schema into production.
Query reusable Builder.io symbols in Claude Desktop
The `list_symbols` tool exposes your global visual blocks so Claude Desktop can reuse them across different pages. You avoid duplicating components because your agent checks what already exists in your library. Tracking performance is just as straightforward since `get_api_usage` monitors your rate limits as you build. This keeps your local development flow inside Claude Desktop safe from sudden API throttling.
Set up Builder.io MCP in Claude Web or Desktop
- 1
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
- 2
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcpReplace[YOUR_TOKEN_HERE]with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials. - 3
Start a conversation
Open a new chat. The Builder.io MCP tools are available immediately — no restart needed.
Endpoint URL
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp No configuration file needed — paste the URL directly in the Claude web interface.
Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
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 MCP in Claude Desktop
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the Builder.io MCP today
We host it, we monitor it, we maintain it. You just paste one token.