# Plasmic MCP for AI Agents AI Agent Connect

> Plasmic lets you manage your visual headless page builder projects, pages, and CMS data through your AI client. Instead of clicking through the Studio UI, you can list projects, audit page structures, and trigger production publishes directly from a chat interface. It bridges the gap between your visual design workflow and your AI agent.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_3sKdf5JGlcT8ZlPYWT5zfXjfJKOMYRYhuIjG3Rng/ai-agent-connect
- **Tags:** visual-builder, low-code, react, nextjs, web-development

## Description

Imagine you're in the middle of a build and need to know exactly how many items are in a specific CMS table or you need to check the structure of a complex page. Usually, that means tab-switching, hunting for the right project ID, and navigating the visual editor. This Connector changes that. It turns your AI client into a direct bridge to your Plasmic projects. You can ask your agent to pull up a project's metadata, fetch the list of pages for a specific site, or even handle the tedious stuff like updating CMS entries or pushing a project live. It's about staying in your flow. Whether you're a developer who wants to automate deployment triggers or a content manager who needs to verify data without opening the full Studio, this connection keeps your hands on the keyboard and off the browser tabs. You'll find this works great because it's hosted on Vinkius, which makes it easy to hook into your existing setup and get started without the usual friction of manual configuration.

## Tools

### get_model
Pull the JSON representation of your project's element tree. It gives your AI a clear map of your page structure.

### publish_cms_item
Push a draft CMS record to live. This allows for quick content updates without manual clicks.

### query_cms_items
Fetch specific records from your CMS database. Use this to retrieve data for your AI to analyze or summarize.

### count_cms_items
Check the number of entries in a specific CMS table. This helps you quickly audit your data volume without opening the dashboard.

### create_cms_item
Add a new record to your CMS database. You can do this via chat to quickly populate content.

### delete_cms_item
Remove a specific entry from your CMS. This makes cleaning up old data much faster.

### render_html
Get the generated HTML for a specific component. This is useful for checking how a component will actually look.

### update_cms_item
Modify an existing record in your CMS. You can update content fields through a simple chat command.

### update_project
Change project settings or configurations programmatically. This lets you manage project-level data at scale.

## Prompt Examples

**Prompt:** 
```
List all my Plasmic projects.
```

**Response:** 
```
I've found 3 projects in your account: 'Marketing Site' (ID: 8vK...), 'E-commerce Store' (ID: 2mP...), and 'Documentation' (ID: 9qL...). Which one would you like to inspect?
```

**Prompt:** 
```
Show me the pages for project ID 8vK...
```

**Response:** 
```
Fetching pages for 'Marketing Site'... I found 4 pages: 'Home' (/), 'About Us' (/about), 'Pricing' (/pricing), and 'Contact' (/contact).
```

**Prompt:** 
```
Publish the latest changes for project 8vK...
```

**Response:** 
```
Publishing 'Marketing Site' (ID: 8vK...) now... The project has been successfully published to production.
```

## Capabilities

### List all active projects
Get a full list of your Plasmic projects with their metadata and IDs.

### Fetch page structures
Retrieve the organization of pages within a specific project.

### Trigger production publishes
Push your projects live or update your storefront from the chat.

### Create new CMS entries
Add new records to your CMS database using natural language.

### Update existing CMS data
Modify content fields in your CMS without opening the dashboard.

### Delete CMS records
Remove specific entries from your database to keep content clean.

### Count database items
Check the number of entries in a specific CMS table instantly.

## Use Cases

### Auditing page routes
A developer needs to know the page routes for a new site and asks the agent to fetch the page list for a specific project ID.

### Verifying content status
A content manager wants to check if a blog post is live and asks the agent to check the status of a specific CMS item.

### Inspecting component output
A designer wants to see the HTML output of a complex component and asks the agent to render the HTML for that specific part.

### Bulk updating project metadata
A project lead needs to update a project's configuration and asks the agent to update the project settings using the update_project tool.

## Benefits

- Stop tab-switching between your code editor and the Plasmic Studio. You can pull project IDs and page lists directly into your AI client.
- Automate your deployment workflow by using publish_cms_item and update_project to push changes to production without manual intervention.
- Quickly audit your CMS data by using count_cms_items and query_cms_items to see exactly what's live or pending.
- Get instant visibility into your site structure with get_model, which lets your agent understand your page hierarchy immediately.
- Update content records in bulk or individually using update_cms_item and create_cms_item to keep your site fresh with fewer clicks.

## How It Works

The bottom line is you get a direct command line for your visual page builder without leaving your AI chat.

1. Subscribe to the Connector and provide your Plasmic Project ID and API Token.
2. Open your AI client and ask it to list your projects or inspect a specific page.
3. Receive real-time project data or confirm a successful publish instantly.

## Frequently Asked Questions

**Can I use the Plasmic MCP to manage my headless CMS?**
Yes, you can use it to create, update, delete, and count items in your CMS tables. It makes managing content much faster by letting you use natural language instead of clicking through a dashboard.

**Does this Connector work with the Plasmic visual builder?**
It connects directly to your Plasmic projects, allowing your AI client to see your page structures and project configurations.

**How do I trigger a project publish using the AI?**
You can simply ask your agent to publish a specific project or a draft CMS item. The Connector handles the connection to the Plasmic API to make it happen instantly.

**Can my AI agent see my site's page structure?**
Yes, by using the project model tool, your agent can pull a JSON representation of your element tree to understand how your pages are organized.

**Is this Connector good for developers?**
It's great for devs who want to automate repetitive tasks like checking page lists or updating project metadata without leaving their code editor.

**Will this help me manage multiple Plasmic projects?**
Absolutely. You can list all your projects at once and then tell your AI which one you want to inspect or update.

**Can I list all my Plasmic projects to find a specific Project ID?**
Yes! Use the `list_projects` tool. Your agent will return a list of all projects associated with your credentials, including their names and unique IDs.

**How do I see which pages are currently built inside a project?**
Simply ask the agent to run `get_project_pages` with the target Project ID. It will list all pages, their paths, and basic metadata.

**Is it possible to publish my changes to production using the AI?**
Yes. By using the `publish_project` tool, you can trigger a new publish for a specific project ID, making your visual changes live immediately.