How to Use the Builder MCP in Cursor

Q: How do I set up Builder in my Cursor project?

You create a .cursor/mcp.json file in your repository root and add the server configuration. Cursor reads this file on startup, enabling the tools in Agent mode using the MCP standard.

Q: Can I search for models within Cursor?

Yes, you can. The searchactivemodels tool lets your agent find models matching specific strings so you don't have to memorize exact naming conventions.

Q: How does Cursor handle Builder schema changes?

The agent calls getmodelschema on demand to fetch the latest field definitions. This ensures your code remains aligned with any schema updates made in the Builder web interface via the MCP protocol.

Generate code that works with real Builder.io schemas and content directly inside your Cursor editor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Builder MCP to Cursor

Create your Vinkius account to connect Builder to Cursor 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 with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Inspect live Builder schemas while writing code

The `list_builder_models` and `get_model_schema` tools inside this MCP server let your Cursor agent inspect live schemas before writing a single line of React. You don't have to guess if a field is a string or an object. The editor pulls the exact structure into its context window. This ensures your generated frontend components map perfectly to your headless CMS fields without runtime errors.

Query production content to generate mock-free tests

The `get_single_content` and `list_model_content` tools fetch actual CMS documents to populate your Cursor testing environment. You no longer have to write fake data stubs that might diverge from reality. Your AI agent reads the real JSON structure returned by the tools to write assertion suites. This makes your local integration tests match the actual API responses you get in production.

Sync UI blocks to Builder via Cursor MCP Server

The `create_visual_block` and `update_visual_block` tools allow your Cursor editor to push visual layout changes straight to your CMS. When you modify a component locally, the agent can update the corresponding block in Builder.io. If you need to clean up deprecated components, the `wipe_visual_block` tool handles the deletion. You manage your CMS content state directly alongside your codebase.

Setup guide

Set up Builder MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Builder MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Builder transactions." If the MCP tools are loaded correctly, Cursor will call the Builder tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "builder-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. 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 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 MCP in Cursor

You create a `.cursor/mcp.json` file in your repository root and add the server configuration. Cursor reads this file on startup, enabling the tools in Agent mode using the MCP standard.

Yes, you can. The `search_active_models` tool lets your agent find models matching specific strings so you don't have to memorize exact naming conventions.

Yes, this integration runs locally. Your Cursor agent calls the CMS tools to fetch production schemas while you work on your localhost frontend server.

The agent calls `get_model_schema` on demand to fetch the latest field definitions. This ensures your code remains aligned with any schema updates made in the Builder web interface via the MCP protocol.

Your Builder.io API keys, schemas, and content entries are handled locally within your editor's runtime environment. Cursor does not expose your CMS credentials or visual block data to external servers, keeping your headless workspace 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