What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI tools like Claude, Cursor, Codex, and Antigravity connect to outside systems and act on them directly, instead of just talking about them. UiChemy runs an MCP server, so once your AI tool is connected, it can build pages, edit sections, and update styles on your actual WordPress site.

The Client and Server

Every MCP connection has two sides:

• The client is your AI tool. It's what you talk to in plain English.
• The server is UiChemy. It exposes a fixed set of capabilities, like creating a page or reading a form's submissions, that the client is allowed to call.

Your AI tool never touches your site directly. It sends a request to the UiChemy MCP server, the server performs the action through Composer, and the result comes back to your AI tool as a normal editable page.

What Happens When You Ask for Something

1. You describe what you want, in your AI tool, like you would to a person.
2. Your AI tool reads UiChemy's built-in guide and the matching skill (for example, how to turn a brief or a Figma design into pages), then calls UiChemy's real capabilities over MCP.
3. UiChemy performs the action on your connected site and returns the outcome.
4. The result lands as a normal, editable Composer, the same as anything built through the Figma plugin.

You never need to know the exact capability name behind a request. See MCP Tools Reference if you want the full list of what's actually available.

What It Can and Can't Touch

MCP access is scoped to building and configuring with UiChemy: pages, templates, Global Style, dynamic content, forms, media, SEO, performance settings, custom post types and fields, and site setup. With UiChemy Pro it can also build a WooCommerce store and manage shared code files and custom fonts. It can't install other plugins, change unrelated WordPress settings, or reach anything outside UiChemy.

It builds into whichever page builder your site uses: Elementor or Gutenberg, with Bricks coming soon.