4,000+ servers built on vurb.ts
Vinkius

Builder.io (Visual CMS) MCP Server for ClineGive Cline instant access to 9 tools to Admin Graphql, Create Content, Delete Asset By Url, and more

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Builder.io (Visual CMS) through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

The Builder.io (Visual CMS) MCP Server for Cline is a standout in the Developer Tools category — giving your AI agent 9 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "builderio-visual-cms": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Builder.io (Visual CMS) and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
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

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

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Builder.io (Visual CMS) tool calls without waiting for prompts between steps. Connect 9 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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.

The Builder.io (Visual CMS) MCP Server exposes 9 tools through the Vinkius. Connect it to Cline in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 9 Builder.io (Visual CMS) tools available for Cline

When Cline connects to Builder.io (Visual CMS) through Vinkius, your AI agent gets direct access to every tool listed below — spanning visual-cms, graphql, content-api, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

admin

Admin graphql on Builder.io (Visual CMS)

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

create

Create content on Builder.io (Visual CMS)

Requires Private API Key. Create a new content entry

delete

Delete asset by url on Builder.io (Visual CMS)

Delete an asset by its URL

delete

Delete content on Builder.io (Visual CMS)

Requires Private API Key. Delete a content entry

get

Get content on Builder.io (Visual CMS)

Get content from a Builder.io model

get

Get html on Builder.io (Visual CMS)

Get pre-rendered HTML for a Builder.io model

query

Query graphql on Builder.io (Visual CMS)

Query Builder.io content using GraphQL

update

Update content on Builder.io (Visual CMS)

Requires Private API Key. Update an existing content entry

upload

Upload asset on Builder.io (Visual CMS)

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

Connect Builder.io (Visual CMS) to Cline via MCP

Follow these steps to wire Builder.io (Visual CMS) into Cline. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using Builder.io (Visual CMS)

Ask Cline: "Using Builder.io (Visual CMS), help me...". 9 tools available

Why Use Cline with the Builder.io (Visual CMS) MCP Server

Cline provides unique advantages when paired with Builder.io (Visual CMS) through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Builder.io (Visual CMS) + Cline Use Cases

Practical scenarios where Cline combined with the Builder.io (Visual CMS) MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from Builder.io (Visual CMS) and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Builder.io (Visual CMS) tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Builder.io (Visual CMS) and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Builder.io (Visual CMS) for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for Builder.io (Visual CMS) in Cline

Ready-to-use prompts you can give your Cline agent to start working with Builder.io (Visual CMS) immediately.

01

"Fetch the latest 5 entries from the 'page' model in Builder.io."

02

"Update the 'announcement-bar' entry with ID 'entry-888' to change the text to 'Sale ends tonight!'."

03

"Upload this image URL to my Builder assets: https://example.com/hero.jpg"

Troubleshooting Builder.io (Visual CMS) MCP Server with Cline

Common issues when connecting Builder.io (Visual CMS) to Cline through Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Builder.io (Visual CMS) + Cline FAQ

Common questions about integrating Builder.io (Visual CMS) MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →