4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
Builder.io (Visual CMS) MCP Server

Bring Visual Cms
to VS Code Copilot

Learn how to connect Builder.io (Visual CMS) to VS Code Copilot and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Admin GraphqlCreate ContentDelete Asset By UrlDelete ContentGet ContentGet HtmlQuery GraphqlUpdate ContentUpload Asset

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Builder.io (Visual CMS)

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_content or retrieve pre-rendered HTML for components with get_html.
  • Write Operations — Create, update, or delete content entries programmatically using the Write API tools like create_content and update_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

  1. Subscribe to this server
  2. Enter your Builder.io Public Key (and Private Key for write access)
  3. 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)

admin_graphql

Requires Private API Key. Execute an Admin API GraphQL query/mutation

create_content

Requires Private API Key. Create a new content entry

delete_asset_by_url

Delete an asset by its URL

delete_content

Requires Private API Key. Delete a content entry

get_content

Get content from a Builder.io model

get_html

Get pre-rendered HTML for a Builder.io model

query_graphql

Query Builder.io content using GraphQL

update_content

Requires Private API Key. Update an existing content entry

upload_asset

Requires Private API Key. Upload an asset (image, video, document)

Why VS Code Copilot?

GitHub Copilot Agent mode brings Builder.io (Visual CMS) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Builder.io (Visual CMS) in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Builder.io (Visual CMS) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Builder.io (Visual CMS) to VS Code Copilot 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Builder.io (Visual CMS) in VS Code Copilot

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 VS Code Copilot 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.

Builder.io (Visual CMS)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Builder.io (Visual CMS) for VS Code Copilot

Every tool call from VS Code Copilot 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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →