How to Use the Builder.io MCP in VS Code Copilot

Q: How do I share the Builder.io configuration with my VS Code Copilot team?

Save your setup in .vscode/mcp.json to enable the MCP Server for your team. Every team member with the VS Code Copilot extension will automatically get access to the CMS tools.

Q: Can VS Code Copilot create new pages in my Builder.io space?

Yes, the agent uses the createcontententry tool to generate fresh content drafts. You can describe the page layout in chat, and Copilot will handle the API payload.

Q: Can I query my Builder.io API usage inside VS Code Copilot?

Yes, you can run getapiusage directly in your chat. This helps your team track rate limits during large-scale content migrations.

Give your team's VS Code Copilot agents direct access to Builder.io models and content entries.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Builder.io MCP to VS Code Copilot

Create your Vinkius account to connect Builder.io to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Builder.io with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share Builder.io schemas across VS Code Copilot teams

The `list_models` tool exposes your entire visual CMS structure to VS Code Copilot across your whole engineering team. By committing this MCP configuration to your repo, every developer can instantly query models without manual setup. When writing layout code, Copilot uses `get_model` to verify field types on the fly. This prevents integration bugs before they reach your CI/CD pipeline.

Edit Builder.io content entries via VS Code Copilot

The `update_content_entry` tool lets your team modify layout payloads without leaving VS Code Copilot. Developers can fix broken localization strings or update metadata structures directly within their chat panel. If a layout breaks, `get_content_entry` pulls the exact JSON payload to let Copilot debug the rendering logic. You see exactly what the CMS is sending to your frontend.

Map visual components with this MCP Server

The `list_symbols` tool provides your global UI blocks directly to VS Code Copilot. This ensures your team reuses existing components rather than writing duplicate code for visual sections. To keep operations safe, `get_space` and `list_spaces` verify which environment Copilot is targeting. This prevents accidental changes to production spaces during local testing.

Setup guide

Set up Builder.io MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Builder.io MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Builder.io tools listed. Try asking: "List my recent Builder.io transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "builderio-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Builder.io now

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

Save your setup in `.vscode/mcp.json` to enable the MCP Server for your team. Every team member with the VS Code Copilot extension will automatically get access to the CMS tools.

Yes, the agent uses the `create_content_entry` tool to generate fresh content drafts. You can describe the page layout in chat, and Copilot will handle the API payload.

The server respects your local environment configurations. Copilot can only run tools like `update_content_entry` if the developer has the correct API key loaded in their local environment.

Yes, you can run `get_api_usage` directly in your chat. This helps your team track rate limits during large-scale content migrations.

This MCP Server runs in a zero-trust, ephemeral V8 isolate sandbox. Your Builder.io content entries, API keys, and model structures are processed locally and never stored on external databases, keeping your proprietary CMS data fully secure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript