Compatible with every major AI agent and IDE
What is the Builder.io (Visual CMS) MCP Server?
Connect your Builder.io space to any AI agent and take full control of your visual CMS and headless content through natural conversation.
What you can do
- Content Management — Fetch entries from any model using
get_contentor retrieve pre-rendered HTML for components withget_html. - Write Operations — Create, update, or delete content entries programmatically using the Write API tools like
create_contentandupdate_content. - Advanced Querying — Execute complex GraphQL queries against the Content API or perform administrative tasks using
admin_graphql. - Asset Handling — Upload new media assets or remove existing ones by URL to maintain your digital asset library.
- Targeting & Personalization — Use user attributes and MongoDB-style queries to fetch specific content variants.
How it works
- Subscribe to this server
- Enter your Builder.io Public Key (and Private Key for write access)
- Start managing your digital experience from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — query and update CMS content directly from your IDE without switching to the Builder dashboard
- Content Managers — automate bulk updates or content migrations using natural language instructions
- Marketing Teams — quickly inspect content targeting and pre-rendered HTML outputs for SEO checks
Built-in capabilities (9)
Requires Private API Key. Execute an Admin API GraphQL query/mutation
Requires Private API Key. Create a new content entry
Delete an asset by its URL
Requires Private API Key. Delete a content entry
Get content from a Builder.io model
Get pre-rendered HTML for a Builder.io model
Query Builder.io content using GraphQL
Requires Private API Key. Update an existing content entry
Requires Private API Key. Upload an asset (image, video, document)
Why Claude Desktop?
Claude Desktop is the definitive way to connect Builder.io (Visual CMS) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Builder.io (Visual CMS) in Claude Desktop
Builder.io (Visual CMS) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Builder.io (Visual CMS) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Builder.io (Visual CMS) in Claude Desktop
The Builder.io (Visual CMS) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Builder.io (Visual CMS) for Claude Desktop
Every tool call from Claude Desktop to the Builder.io (Visual CMS) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I fetch pre-rendered HTML for my components instead of raw JSON?
Yes! Use the get_html tool. It returns pre-rendered HTML for a specific model and URL, which is perfect for quick inspections or server-side integrations.
Do I need a Private API Key to use this server?
A Public Key is required for all read operations (get_content, query_graphql). However, a Private Key is mandatory for write operations like create_content, update_content, or admin_graphql.
Can I perform administrative tasks like managing Spaces or Models?
Yes, the admin_graphql tool allows you to execute administrative queries and mutations against the Builder Admin API, provided you have supplied a Private API Key.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Shimo Docs
10 toolsCollaborative office suite and document management platform — manage Word, Excel, and PPT via AI.

WhatsApp Business Alternative
8 toolsAutomate your customer communication — send templates and manage profiles via AI.

HotDocs
14 toolsAutomate document assembly via HotDocs Advance — list templates, create work items, conduct interviews, and generate documents directly from any AI agent.

Genius Alternative
14 toolsAccess the world's largest collection of song lyrics and musical knowledge. Search songs, artists, and annotations directly from your AI agent.
