An astronaut overseeing a futuristic data hub

Connect Builder to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your Builder.io content without leaving your editor.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Builder.

  1. 01

    List builder models

    This capability lists every data model and schema currently defined in your Builder space.

  2. 02

    Update visual block

    Use this to modify an existing Builder.io content block or document.

  3. 03

    Get model schema

    This capability retrieves the specific field structures and strict JSON definitions for a single model.

  4. 04

    Get single content

    This capability pulls a specific content document by matching your query strings.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Builder.

  1. 05

    List model content

    Use this to fetch a list of content entries belonging to a specific Builder.io model.

  2. 06

    Search active models

    This capability finds Builder models that match your specific criteria or substrings.

  3. 07

    Wipe visual block

    This capability permanently deletes a specific content entry from your Builder.io account.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Builder.

  1. 08

    Count model entities

    Use this to get a quick count of live items stored within a specific model.

  2. 09

    Create visual block

    This capability creates new content entries or visual blocks inside a designated Builder model.

  3. 10

    Get media file

    This capability retrieves metadata and details for uploaded media assets in Builder.io.

Real work

What teams actually run

01

Schema Validation

A developer asks the agent for a model's field requirements to ensure their code matches the CMS structure.

02

Bulk Content Updates

An editor uses the agent to push dozens of localized content blocks at once.

03

Environment Cleanup

A DevOps engineer instructs the agent to delete old test components from a specific model.

04

Content Auditing

A user asks the agent to count how many live items exist in a specific model to verify deployment status.

Automate a task

Put Builder to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Builder works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Builder to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

922ms average. Fast in production.

Builder is checked daily against the live service.

Daily averagePeak 1136ms
Oct 3Today
Fastest day
791ms
Slowest day
1136ms
14-day trend
Slowing+7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Builder, so you can see the experience inside your AI.

It does not authenticate your account with Builder. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Builder Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_BqALflagL8xNOmjaZGHvPIxPB3BCwZBh8bTcwCPe/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Builder capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "builder-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_BqALflagL8xNOmjaZGHvPIxPB3BCwZBh8bTcwCPe/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Builder in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Builder owners hand off.

This MCP is built for technical users who manage visual content through a headless architecture.

  • 01

    Frontend Developers

    They use the agent to pull strict data schemas before writing frontend fetch logic.

  • 02

    Content Editors

    They automate the deployment of large batches of translated content or landing page sections.

  • 03

    DevOps Engineers

    They use the agent to wipe orphaned elements or clean up test environments without using the UI.

FAQ

Questions Builder owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You subscribe to the MCP on Vinkius and then connect your client, such as Claude or Cursor, using the provided connection details. Vinkius handles the hosting and credentials for you.

  • 02

    Do I need to use the Builder.io web interface?

    No. While you can still use the UI, this MCP allows you to perform almost all management tasks, like updating blocks or checking schemas, directly through your AI agent.

  • 03

    What credentials do I need to provide?

    You will need to enter your Builder Public and Private API Key pair to authorize the connection to your specific workspace.

  • 04

    Can I delete content using this MCP?

    Yes. The wipe_visual_block capability allows you to permanently remove specific content entries from your Builder.io account.

  • 05

    Is this compatible with Cursor or VS Code?

    Yes, this MCP is compatible with any MCP-compatible client, including Cursor, Windsurf, and VS Code.

  • 06

    Can my AI read the strict structure of a custom model before creating a block?

    Yes! We highly recommend asking your agent to use get_model_schema first. By retrieving the exact JSON fields (Strings, Lists, Booleans), the AI naturally learns the shape of your Page or HeroContent model and formats its create_visual_block mutation flawlessly avoiding validation errors.

  • 07

    How can I count how many blogs or pages are in my Builder space?

    You can use the native count_model_entities capability. By querying a model like blog-post, the agent accesses the Builder backend with limit=1 exclusively to extract the metadata counts without downloading heavyweight content arrays—highly efficient for broad analytics.

  • 08

    Can the agent wipe an accidentally created page completely?

    Yes. If an error occurs or a staging draft needs removal, the agent can call wipe_visual_block. Supply the targeted entity ID, and the HTTP DELETE command is irreversibly broadcasted to the Builder environment. Always review IDs manually.

Connect Builder to Claude, Cursor, ChatGPT & more