Builder MCP. Write code to manage your CMS data.

Builder MCP Server: Direct Control Over Your CMS Content.

You're tired of switching between your code editor and the Builder UI just to manage content? This server gives your AI agent direct, programmatic control over every piece of content in your headless CMS. You don't need any manual steps; your agent handles listing models, checking schemas, counting records, and generating or modifying visual blocks—all right within your natural conversation flow.

Managing Your Models and Schemas

You can start by having the agent list every single data model defined in your Builder workspace using list_builder_models. If you know a part of the name, you don't have to read everything; the system lets you narrow it down with search_active_models, finding models that match specific names or substrings.

Once you pick a model, you can use get_model_schema to pull the exact field structure and JSON definition required for that content type. This tells your agent precisely what data format you need before it writes anything.

Reading and Fetching Content Data

When you need content, you've got options. To get a full picture of everything in one model, use list_model_content to pull a complete list of entries for that entire model—perfect for bulk operations or auditing. If you only need one specific document, the agent can fetch it using get_single_content, which requires targeted query matching (like finding the 'Home' page).

You can also quickly check how many active content entries exist in any given model by calling count_model_entities. For handling media attachments, you just use get_media_file to retrieve metadata, including URLs and details, for any uploaded asset attached to a block or model.

Creating and Updating Blocks

The agent can build content from scratch. You can generate and insert new visual content blocks or full records into a specified Builder model using create_visual_block. Need to tweak an existing piece? The system lets you modify the data fields of any current block or visual document within its model structure via update_visual_block.

This means your agent doesn't just read; it makes changes, keeping your content fresh without ever opening the dashboard.

Auditing and Cleaning Up

When a page or component is deprecated, you need to get rid of it. The server lets you permanently delete a specific, targeted content entry from Builder.io using wipe_visual_block. This gives you full control over cleaning out old or orphaned components in your system.