Connect an MCP Client
Connect Claude, Cursor, or another MCP client to your site.
An MCP client is just your AI tool, Claude, Cursor, Codex, or Antigravity, once it's been told how to reach UiChemy's MCP server. This page covers what that connection actually is and how to confirm it's working. For the click-by-click setup, see Set Up AI to WordPress.
Do this after you've generated your config on the UiChemy dashboard. Every MCP client needs three things: a server URL, an Application Password, and a config file in the right place. UiChemy's dashboard generates the first two and shows you the exact file path for the third, per tool.
Where Each Tool Keeps Its MCP Settings
Every MCP client reads its server connections from its own config, in its own location, not from UiChemy. That's why picking a tool on UiChemy → Home → AI Agent (MCP) changes the config and save path shown, instead of giving you one universal config.
- Claude Desktop reads from
claude_desktop_config.json. - Cursor, Codex, and Antigravity each read from their own MCP config location.
Whichever tool you pick, use the Prompt / Config switch: Config gives you the raw config to copy and paste into the exact path UiChemy shows for that tool yourself, Prompt gives you a ready-made prompt that has your AI tool edit that same file for you.
Always use the exact file path UiChemy's dashboard shows for your tool at the time you connect. Tool vendors can move where this file lives between versions, the dashboard is kept current, this page isn't the source of truth for exact paths.
Confirming the Connection Worked
Once the config is saved and the tool is restarted, don't look for a UiChemy-specific indicator, ask the tool itself:
Example prompt: "What tools do you have from UiChemy?" or "List the pages on my site."
If the connection is live, your AI tool responds with real data from your site, actual page titles, not a generic or made-up answer.
If It Doesn't Work
- Your AI tool says it has no such capability, or can't answer. The config likely didn't save to the path your tool actually reads from. Reopen UiChemy → Home → AI Agent (MCP), re-pick your tool, and re-check the exact path shown, then paste again.
- You pasted the config but nothing changed. Restart the tool. Most MCP clients only read their config file on startup, a running session won't pick up a new connection.
- The tool responds, but with generic or made-up answers instead of your real site data. That's not a working connection, the tool is guessing rather than calling UiChemy. Re-check the config was saved to the right file and restart again.
- Still stuck. Go back to Set Up AI to WordPress and confirm Node.js 18+ is installed, you're signed in as an Administrator, and the Application Password in your config is current, an old, rotated one will silently fail. The Figma plugin path always works without MCP.
Other MCP Clients and Endpoints
Most people never need this section, the dashboard config already points at the right place. It helps if you're wiring UiChemy into a custom setup.
| Endpoint | What it's for |
|---|---|
/wp-json/uichemy/v2/mcp | The main endpoint, and the one the dashboard gives you. Your AI tool gets UiChemy's built-in guide, its skills, and every ability through three simple tools: discover-abilities, get-ability-info, and execute-ability. |
/wp-json/uichemy/v1/mcp | The older endpoint with a flat list of the original tools. It stays for the Figma plugin and older setups. Use v2 for AI tools. |
On sites with plain permalinks, the same endpoints use ?rest_route=, for example https://yoursite.com/index.php?rest_route=/uichemy/v2/mcp. The dashboard always shows the right form for your site.
- Already run another WordPress MCP server? UiChemy registers its abilities as public WordPress abilities, so another MCP server on your site that serves WordPress abilities (such as the WordPress MCP Adapter) can offer them too. Each ability carries its own instructions, so your AI tool can use it there as well.
- Site with more than one page builder? Add
?builder=elementoror?builder=gutenbergto the v2 URL to pin one (use&builder=instead when the URL already has?rest_route=). Without it, new pages go to the builder you chose during setup, and existing pages always stay in their own builder. - MCP switched off? Every call is refused while the MCP server switch in UiChemy → Settings → Integrations is off.
What's Available Once Connected
See MCP Tools Reference for the full list of what your AI tool can build, edit, and read once it's connected.