Can I update a content entry using the agent?

Yes! Use the `update_content_entry` tool with the Model name and Entry ID. You can provide a new `data` JSON string to modify the content fields directly from your workspace.

How do I list all the models defined in my space?

Simply ask the agent to `list_models`. It will retrieve all the content models (like 'page', 'header', 'announcement-bar') configured in your Builder.io account.

Does the integration allow checking API usage limits?

Yes. Use the `get_api_usage` tool. It will retrieve real-time statistics about your API requests, helping you monitor your performance and limits.

Builder.io MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Builder.io
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Builder.io and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

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

About Builder.io MCP Server

Connect your Builder.io account to any AI agent and orchestrate your visual CMS, content management, and digital experience workflows through natural conversation.

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

What you can do

Content Oversight — List and retrieve detailed metadata for all your content entries across different models (Pages, Blog Posts, etc.).
Model Management — List all content models in your space and retrieve detailed schema metadata.
Visual Automation — Create and update content entries programmatically using the Write API directly from your workspace.
Infrastructure Coordination — Access and monitor your spaces, organization settings, and reusable symbols.
Performance Tracking — Retrieve real-time API usage statistics to monitor your CMS performance.
Entry Deep Dives — Get detailed data for specific content or model IDs straight from your workspace.

The Builder.io MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Builder.io to VS Code Copilot via MCP

Follow these steps to integrate the Builder.io MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Builder.io

Ask Copilot: "Using Builder.io, help me...". 10 tools available

Why Use VS Code Copilot with the Builder.io MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Builder.io through the Model Context Protocol.

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

Builder.io + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Builder.io MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Builder.io MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Builder.io to VS Code Copilot via MCP:

create_content_entry

Create a new content entry

get_api_usage

Retrieve API usage statistics

get_content_entry

Get a specific content entry

get_model

Get details of a specific content model

get_space

Get details of a specific space

list_content

List content entries for a specific model

list_models

List all content models in the space

list_spaces

List all spaces in your organization

list_symbols

List all reusable symbols

update_content_entry

Update an existing content entry

Example Prompts for Builder.io in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Builder.io immediately.

"List all content entries for the 'page' model."

"Show the schema details for the 'blog-post' model."

"Create a new entry in 'announcement-bar' with name 'Promo Banner'."

Troubleshooting Builder.io MCP Server with VS Code Copilot

Common issues when connecting Builder.io to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

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

Builder.io + VS Code Copilot FAQ

Common questions about integrating Builder.io MCP Server with VS Code Copilot.

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.

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.

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.

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.