> For the complete documentation index, see [llms.txt](https://docs.uichemy.com/llms.txt).
> Use it to discover all available pages before exploring further.

# AI to WordPress

Which MCP clients work with UiChemy, and what each one can do.


UiChemy MCP works with any AI tool that supports the Model Context Protocol. These are the tools UiChemy's dashboard generates ready-to-paste config for:

| Tool | Config format | Save path |
|---|---|---|
| **Claude Desktop** | JSON | `claude_desktop_config.json` |
| **Cursor** | JSON | `.cursor/mcp.json` (or a project-level `.cursor/mcp.json`) |
| **Codex** | TOML | `.codex/config.toml` |
| **Antigravity** | JSON | `.gemini/config/mcp_config.json` |

Every tool gets the same underlying access, the same MCP server, the same capabilities, and the same **Prompt / Config** switch on the dashboard, one tab gives you a ready-made prompt that tells your AI tool to edit its own config file, the other gives you the raw config to paste in yourself. See [MCP Tools Reference](/uichemy-composer/uichemy-widget/mcp-tools-reference) for the full list of what's available. What differs between tools is only the config format and where it saves, not what you can build once connected.

### Building with Another AI Tool First

These tools generate a site or page outside WordPress, they don't speak MCP themselves, so UiChemy can't connect to them directly. Build there first, then bring the result into WordPress through one of the four MCP clients above:

| Tool | Status |
|---|---|
| [Lovable](/ai-to-wordpress/lovable) | Supported |
| [Bolt](/ai-to-wordpress/bolt) | Supported |
| [v0](/ai-to-wordpress/v0) | Supported |
| [Clone Site](/ai-to-wordpress/clone-site) | Supported |
| [Google Stitch](/ai-to-wordpress/google-stitch) | Supported |
| [Framer](/ai-to-wordpress/framer) | Supported |
| [Wix](/ai-to-wordpress/wix) | Supported |
| [HTML](/ai-to-wordpress/html) | Supported |

<Callout kind="info">
Lovable, Bolt, v0, Clone Site, Google Stitch, Framer, Wix, and HTML each have their own page above with the exact steps: build (or clone) there, download or export the project, then hand it to Claude Desktop, Cursor, Codex, or Antigravity to bring into WordPress.
</Callout>

<Callout kind="info">
Not seeing your tool listed? If it supports MCP and can read a client config file, pick **Other** on the dashboard's tool cards, it gives you a ready-made prompt your tool can use to edit its own config file, even without a dedicated card.
</Callout>

### Frequently Asked Questions

<ExpandableGroup>
  <Expandable title="What if my AI tool isn't listed?" default-open="false">
    Any AI tool that supports MCP works. Pick **Other** on **UiChemy → Home → AI Agent (MCP)**, copy the prompt it gives you, and paste it into your tool. It detects which app it's running in and edits that app's MCP config file for you.
  </Expandable>

  <Expandable title="Why can't UiChemy connect to Lovable, Bolt, or Framer directly?" default-open="false">
    Those tools build sites outside WordPress and don't have their own MCP, so there's nothing for UiChemy to connect to. Build there first, export or download the project, then hand it to Claude Desktop, Cursor, Codex, or Antigravity to bring it into WordPress.
  </Expandable>

  <Expandable title="Do all four MCP clients get the same features?" default-open="false">
    Yes. Claude Desktop, Cursor, Codex, and Antigravity all connect to the same UiChemy MCP server with the same capabilities. Only the config format and save path differ.
  </Expandable>
</ExpandableGroup>

<Callout kind="tip">
Ready to connect? Follow [Set Up AI to WordPress](/ai-to-wordpress/set-up), then [Connect an MCP Client](/ai-to-wordpress/connect-mcp-client) to confirm it's working.
</Callout>