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 Cursor?
Cursor's Agent mode turns Builder.io (Visual CMS) into an in-editor superpower. Ask Cursor to generate code using live data from Builder.io (Visual CMS) and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Builder.io (Visual CMS) in Cursor
Builder.io (Visual CMS) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Builder.io (Visual CMS) to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
TalkingData
10 toolsLeading big data and product analytics platform in China — manage event tracking and user growth via AI.

BEA (Bureau of Economic Analysis)
4 toolsAccess official US economic statistics including GDP, personal income, and industry data directly from the Bureau of Economic Analysis.

HyperTrack
10 toolsManage location tracking, trips, and geofences via HyperTrack API.

Meilisearch
44 toolsManage your Meilisearch instance — handle indexes, documents, and search configurations directly from your AI agent.
