# Builder MCP for AI Agents MCP > Builder MCP gives your AI client full programmatic control over any headless CMS workflow. It lets you generate, update, and manage structured content blocks, inspect data schemas, and orchestrate visual components directly from natural conversation. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Tags:** visual-editor, digital-experience, content-automation, schema-management, web-development, no-code ## Description Managing a complex website's content usually means jumping between the CMS UI, running local schema checks, and manually updating component models. This MCP changes that. You connect your Builder space to any AI agent and treat your entire headless CMS architecture like an API call—you talk to it, and it acts. You can ask your agent to list every available data model or check the exact JSON structure needed for a new content block. Need to update 50 product descriptions? Just tell your agent to do it. Want to delete old, unused page components? It handles that too. This isn't just another API wrapper; it’s an operational layer that lets you treat content creation and maintenance as conversational tasks. Connecting this MCP via Vinkius means you get the full Builder catalog accessible from any compatible AI client, keeping your coding focused on logic, not repetitive CMS administration. ## Tools ### count_model_entities Quickly counts how many live items are stored within a specified data model. ### create_visual_block Generates new content entries or visual blocks inside any designated Builder model. ### wipe_visual_block Permanently deletes a specific piece of content from your Builder.io workspace. ### get_single_content Retrieves one specific content document by matching it against a query string on the model. ### get_media_file Gathers details, including URLs and metadata, about an uploaded media asset in Builder.io. ### get_model_schema Retrieves the exact field structure and schema definitions for a single content model. ### list_model_content Fetches a list of all dynamic content blocks or pages associated with a specific Builder.io model. ### list_builder_models Lists every defined data model and schema available within the entire Builder space. ### search_active_models Finds specific Builder models by matching a given criteria or substring name. ### update_visual_block Modifies an existing content block or document within the Builder.io CMS. ## Prompt Examples **Prompt:** ``` I need a list of all content models in my workspace. ``` **Response:** ``` **Builder Model Inventory** We've got four primary data types configured: * 📚 `page`: Used for full landing pages. * 📰 `blog-post`: Standard article format with author and date fields. * ✨ `section`: Reusable visual blocks like testimonials or CTAs. * 👤 `author`: Stores biographies for contributors. Which of these do you want me to check the specific field rules for? ``` **Prompt:** ``` What's the structure for the 'custom-hero' model? ``` **Response:** ``` **Schema for `custom-hero`** The Builder.io CMS requires these fields for a valid component: | Field Name | Data Type | Required? | | :--- | :--- | :---: | | `title` | Text String | Yes | | `subtitle` | Text String | No | | `cta_link` | URL | Yes | | `bg_image` | Media Asset | No | Looks like you'll need those four to build a new hero component. ``` **Prompt:** ``` Can you find the home page and check its structure? ``` **Response:** ``` I queried for content titled 'Home' on the `page` model. Found one match (ID: d9e72a4...). It is published and contains a complex array of visual blocks. Do you want me to retrieve the full JSON output? That dump will show every nested element, including data from models like `section` and `custom-hero`, so you can see exactly how it's built. ``` ## Capabilities ### List available data models Retrieve a list of all defined content models and schemas within your builder space. ### Inspect model structure Get the precise field definitions and JSON boundaries for any specific content model you name. ### Find content records Search the CMS to pull specific content documents or count how many items exist in a given model. ### Create and modify content blocks Generate entirely new visual components, or update existing content entries using precise data inputs. ### Manage media assets Check metadata and URLs for uploaded images and files stored on the Builder platform. ### Remove deprecated elements Permanently delete specific content entries or old components from your live CMS models. ## Use Cases ### A developer needs to validate a new component's data structure Instead of guessing the required fields, the developer asks their agent to 'get_model_schema' for the target model. The agent immediately returns the strict JSON definitions, allowing them to write type-safe code instantly. ### A marketing team needs to refresh multiple page sections The editor asks their agent to 'update_visual_block' across several specific content entries. The agent executes the update and confirms all 15 required fields were changed, saving hours of manual API calls. ### A site administrator needs to clean up old test data The admin tells their agent to 'wipe_visual_block' for components tagged as deprecated. The agent executes the deletion and reports back on the number of elements removed, keeping the CMS clean. ### A team wants to check content volume before a launch The lead asks their agent to 'count_model_entities' for the product catalog model. The agent quickly confirms there are 4,201 active items ready for review. ## Benefits - You instantly get the full schema structure of a model using 'get_model_schema,' eliminating guesswork before writing frontend code. - Never manually update content again. You can push 50 translated copies of a page section or landing block automatically using 'create_visual_block' and 'update_visual_block'. - Need to find a specific piece of content? Use 'get_single_content' with query strings instead of clicking through endless pages. - 'list_builder_models' gives you an immediate, comprehensive map of every data structure in your CMS, saving discovery time. - DevOps can use 'wipe_visual_block' to clean up orphaned components and test elements without risking the live UI. - The system tracks media assets through 'get_media_file,' giving you all necessary URLs and metadata in one place. ## How It Works The bottom line is that you use natural language prompts to perform complex, multi-step CMS operations without writing a single function call. 1. Subscribe to this MCP and input your Builder Public and Private API Key pair. 2. Your AI client fetches the available schemas, allowing you to read the data structure right inside your chat environment. 3. You prompt the agent with a content request—like 'List all blog post models' or 'Update the hero section title on page X.'—and get instant action. ## Frequently Asked Questions **How does using the Builder MCP help me automate content updates?** It lets your AI client perform repetitive CMS tasks without you ever opening the dashboard. You can ask it to update 50 pieces of content across multiple models, and it handles the data input and publishing process for you. **Do I need to write code every time I change a model structure?** No. With this MCP, your agent can first run 'get_model_schema' to tell you the exact field definitions. This means you get the necessary data blueprint before writing any front-end logic. **Is this only for creating new content?** No. It handles the full lifecycle. You can list all existing content blocks using 'list_model_content,' update them using 'update_visual_block,' or permanently remove them with targeted deletion. **Does this MCP handle media assets and URLs?** Yes, it does. You can use the built-in tools to inspect metadata and fetch specific URLs for images and other files used in your CMS content. **If I want to know what models exist, how do I start with Builder MCP?** You simply tell your agent to list all available builder models. It will return a comprehensive inventory of every data structure configured in your workspace immediately.