2,500+ MCP servers ready to use
Vinkius

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

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.

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 and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "builder": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Builder
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 MCP Server

Connect your Builder.io space to any AI agent and take full programmatic control over your headless CMS architecture and visual pages through natural conversation.

GitHub Copilot Agent mode brings Builder 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 Automation — Create, update, or wipe specific content entries across any data model dynamically
  • Schema Navigation — List your active Builder models and analyze exact field definitions and strict JSON bounds
  • Search & Retrieval — Use query strings to pull matched content documents or count entities effortlessly
  • Media Fetching — Inspect metadata and URLs of uploaded assets living on the Builder platform
  • Headless Maintenance — Delete deprecated components or page sections instantly using targeted endpoints

The Builder 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 to VS Code Copilot via MCP

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Builder

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

Why Use VS Code Copilot with the Builder MCP Server

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

01

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

02

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

03

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

04

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

Builder + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Builder MCP Tools for VS Code Copilot (10)

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

01

count_model_entities

Quickly count the number of live items stored within a specific model

02

create_visual_block

Create new content entries or visual blocks inside a Builder model

03

get_media_file

Retrieve details about an uploaded media asset within Builder.io

04

get_model_schema

Get the exact field structure and schema definitions for a single model

05

get_single_content

g. `query.data.title=Home`). Retrieve a specific content document by query matching from Builder.io

06

list_builder_models

List all defined data models and schemas in the Builder space

07

list_model_content

Useful for fetching dynamic content blocks or pages. Retrieve a list of content entries for a specific Builder.io model

08

search_active_models

Find Builder models matching a specific criteria or substring

09

update_visual_block

Update an existing Builder.io content block or document

10

wipe_visual_block

Permanently delete a specific content entry from Builder.io

Example Prompts for Builder in VS Code Copilot

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

01

"List all active Builder models in my workspace."

02

"Fetch the schema for the 'custom-hero' model."

03

"Find a page with the title "Home" on the 'page' model."

Troubleshooting Builder MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Builder + VS Code Copilot FAQ

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

01

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.
02

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.
03

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.
04

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.

Connect Builder to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.