Builder.io MCP. Control CMS data and assets from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Builder.io (Visual CMS) MCP lets your AI agent manage everything in your headless content system. Fetch full content entries, query complex data structures using GraphQL, and handle assets—all from natural conversation.
Control your digital experience without opening a single dashboard.
What your AI agents can do
Admin graphql
Runs high-level, administrative API commands that require the private key.
Create content
Adds a brand new content record to any specified model.
Delete asset by url
Removes an asset file from your library using its direct URL.
Run complex queries against your content schema using GraphQL to pull specific, structured data points.
Fetch complete content entries or retrieve the ready-to-use HTML for components directly.
Write new content records to any defined model, or update existing content with specific fields.
Upload new images, videos, or documents, or delete old assets using just a URL.
Execute high-level administrative GraphQL queries for deep system control.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Builder.io (Visual CMS) with 9 Tools
Use these tools in your agent to fetch, modify, query, or delete content entries and digital assets within Builder.io.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Builder.io (Visual CMS) on Vinkius019e3871admin graphql
Runs high-level, administrative API commands that require the private key.
019e3871create content
Adds a brand new content record to any specified model.
019e3871delete asset by url
Removes an asset file from your library using its direct URL.
019e3871delete content
Permanently removes an existing content entry record.
019e3871get content
Pulls the full data payload for a specific content model entry.
019e3871get html
Retrieves the final, ready-to-use HTML code for a component.
019e3871query graphql
Executes arbitrary GraphQL queries to fetch complex relationships across content types.
019e3871update content
Modifies the data fields of an existing content entry record.
019e3871upload asset
Adds a new media file (like an image or video) to your asset library.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Builder.io (Visual CMS), then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
The pain of manual content updates today
Right now, if you want to update a piece of content or change an asset, you have to open the CMS dashboard. You navigate models, click through pages, copy text from one field into another, and upload images manually. It's slow, it’s prone to human error, and you spend half your time just clicking buttons instead of making changes.
With this MCP, that process vanishes. You tell your agent what needs changing—say, 'Update the hero image on the homepage model.' The agent handles fetching the old data, uploading the new asset, modifying the content entry, and updating everything in one go. It’s hands-free.
Getting structured data with query_graphql
The hard part about CMS tools is that they treat every piece of data like a separate silo. If you need to know what the content from 'Model A' was referencing in 'Model B', you usually have to run three different reports and cross-reference the IDs yourself.
Now, `query_graphql` lets your agent see the whole picture at once. You ask for the relationship, and it returns the structured data payload instantly. It’s the difference between running ten separate queries and asking one smart question.
What you can do with this MCP connector
Managing structured content used across multiple websites is usually a nightmare of switching tabs and copy-pasting fields. This MCP lets you talk to your visual CMS directly through your AI client. You can ask your agent to fetch specific data entries, update entire models, or even pull the pre-rendered HTML for a component—all based on natural language instructions.
For instance, if you need to check which content variants are targeting a specific user group, your agent handles that complex query instantly. Need new media? It can upload and delete assets by URL. You're not limited to just fetching data; you can execute full CRUD operations across your entire content model.
This is especially useful when combining this CMS MCP with other services—you could have one workflow chain a billing system update with a content change, for example. The power comes from running these tools through Vinkius, which manages all the connections in a zero-trust proxy, so your keys are used only in transit and never stored on disk.
You get full control over both data models and media assets without ever touching an admin dashboard.
019e3871-ac1a-719e-b0e3-13e31f3a6d86 
How Builder.io MCP Works
- 1 Subscribe to this MCP and provide your Builder.io Public Key, plus a Private API Key if you plan on writing or deleting content.
- 2 Connect the MCP to any compatible client like Cursor or Claude; the agent handles all credential routing through Vinkius's zero-trust proxy.
- 3 Tell your agent what you need—for example, 'Find all blog posts from last month and update their featured image.' The agent then calls the necessary tools in sequence.
The bottom line is: your AI client talks to Builder.io like it's a natural API endpoint, letting you manage content structures and media through conversation.
Who Is Builder.io MCP For?
Anyone whose job involves managing structured digital experiences—from developers pushing CMS changes directly from their IDE, to marketing managers who need bulk data updates without leaving a chat window.
Needs to query the latest content models or pull pre-rendered HTML for components right inside their IDE before committing code.
Wants to automate bulk data updates across multiple models, like changing all 'out of stock' product descriptions at once.
Needs to check content targeting rules or perform complex GraphQL queries to validate SEO parameters before a campaign launch.
What Changes When You Connect
- Skip the dashboard switch: Use
get_contentto pull full entries orget_htmlto grab pre-rendered code, all without leaving your IDE. - Handle complex queries easily. Instead of guesswork, you can use
query_graphqlto ask for exactly the data relationships you need from any model. - Write content changes safely: Use
update_contentorcreate_contentto programmatically modify entries, perfect for running bulk data migrations. - Clean up your media library: You can upload new assets via
upload_assetor remove unused files usingdelete_asset_by_url. - Build multi-step automations. Because Vinkius supports chaining multiple MCPs together, you can combine this content update with a messaging service to notify users after a change.
- Deep control for developers: The
admin_graphqltool lets you execute advanced administrative queries when standard functions aren't enough.
Real-World Use Cases
Content Audit Before Launch
A marketing specialist needs to verify that every page model contains a specific CTA badge and has the correct metadata. They ask their agent, which runs query_graphql across all relevant models to pull the exact data points needed for a compliance check.
Bulk Content Migration
A content manager gets paid last minute and needs to change the primary color link across 50 product pages. They instruct their agent, which uses get_content to fetch the existing data, then executes update_content on all 50 entries with the new value.
Asset Cleanup
A developer notices old logos are clogging up the asset library. They ask their agent to identify and remove them using delete_asset_by_url, keeping the content model clean and efficient.
Deep Data Inspection
You need to see how a piece of dynamic content will actually look in the browser. You ask your agent, which uses get_html on a specific component ID, giving you immediate, raw HTML code for review.
The Tradeoffs
Treating everything like simple key/value data
Thinking you just need to update one field and calling update_content without realizing the content is linked through complex models.
→
Before updating, run query_graphql. This forces your agent to map out all the related fields. Then, use a targeted tool like get_content to ensure you pull the entire structure before making changes.
Manually deleting content records
A developer manually deletes a record via an external dashboard and forgets that this action breaks the live site's data flow.
→
Always use delete_content through your agent. This ensures that any necessary cleanup or logging is triggered, keeping your process auditable.
Assuming direct file access works
Trying to reference an asset path that only worked on the old CMS dashboard.
→
Don't guess. Use upload_asset first to get a clean, new CDN URL, then use that specific URL when updating content via update_content.
When It Fits, When It Doesn't
Use this MCP if your digital experience relies on structured data models (CMS) and complex relationships between different types of information. You absolutely need it if you're dealing with assets, multiple content entry points, or require full GraphQL querying power. Don't use it if all you need is a simple database lookup—if that’s the case, a basic key-value data store MCP will do better and be simpler to manage. If your process involves both updating structured text and managing media files, this combination of tools is what you need.
Common Questions About Builder.io MCP
How do I update content using the update_content tool? +
You tell your agent which model, what ID, and exactly which fields you want to change. The agent makes sure the data payload is structured correctly before calling the tool.
Is query_graphql better than get_content for checking content? +
It depends. Use get_content when you know exactly which single model entry you need. Use query_graphql when you need to pull related data from multiple models or check complex relationships.
Can I use the delete_asset_by_url tool for cleanup? +
Yes, it removes assets based on a direct URL. This is crucial for cleaning up old media that isn't referenced anywhere else in your site.
How do I make sure my content changes are fully auditable? +
Every tool call generates a cryptographically signed audit trail, meaning you get a tamper-proof record of exactly who changed what data and when. You never lose track of history.
What keys do I need before running `create_content`? +
You must provide your Private API Key for any write operations. This key grants the agent permission to modify content entries within Builder.io. The Public Key is enough just for reading data and executing queries.
Should I use `admin_graphql` for advanced system tasks? +
Yes, use admin_graphql when you need to run mutations or perform administrative actions beyond standard content creation. This tool lets your agent interact with the entire CMS backend via direct GraphQL execution.
How do I use `get_html` for SEO checks? +
get_html fetches the pre-rendered HTML output of a component or model entry. This is crucial because it shows you exactly how your content will look in a browser, which is necessary when checking for proper SEO structure.
What happens if I try to `delete_content` using an ID that doesn't exist? +
The tool handles non-existent IDs gracefully by returning a specific error code rather than failing the entire process. This prevents your agent from getting stuck in infinite failure loops.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.