What is the EMCP proxy?
The EMCP proxy is a Node.js stdio bridge. It runs on your machine, accepts MCP requests from your agent and forwards them to the MCP endpoint of a WordPress site running the EMCP Tools plugin. You supply the site URL, a username and an application password.
EMCP Tools is a WordPress plugin that exposes a site as MCP tools, covering Elementor and other page builders, content, media, plugins and more. The proxy is the small Node.js program that lets a stdio-only MCP client talk to that plugin on a remote site.
It runs locally, accepts JSON-RPC over stdio and forwards it to your site's MCP HTTP endpoint. It handles authentication, the session lifecycle and pretty or plain permalink detection, so you do not wire those up by hand.
What it changes in your workflow
- Your agent can build and edit Elementor pages on a live WordPress site through tools, not copy and paste.
- One connection can drive several WordPress installs, with tools to list sites and switch between them.
- Authentication uses a WordPress application password, so the agent acts as that user and no more.
- The proxy runs on your machine, not on the WordPress server.
Proxy or plugin connection
| Proxy (this page) | Direct connection | |
|---|---|---|
| Where it runs | Locally, started by your client with npx | Plugin Connection screen generates a config |
| Needs Node.js | Yes, version 18 or newer | Depends on the client |
| Best for | Clients that only speak stdio, and multi-site work | Quick setup from the plugin admin screen |
Who it is for
Best for
- Agencies and freelancers managing several Elementor sites from one agent session.
- Clients such as Claude Desktop that launch servers as local stdio subprocesses.
- Teams that want writes to stay behind WordPress capability checks.
Not for
- Sites without the EMCP Tools plugin. The proxy only bridges to that plugin's endpoint.
- Reading Figma frames. For design files see Figma MCP.
- Turning an AI-built page into editable Elementor. See Lovable to Elementor.
Use it with UiChemy
EMCP drives an existing Elementor site through tools. UiChemy covers the WordPress side. Composer is a visual editor for Elementor or Gutenberg, and AI to WordPress imports an existing AI build as an editable page. Click Get Started on uichemy.com.
Connect EMCP Proxy: Connect AI Agents to Elementor Sites to your AI client
npx -y @msrbuilds/emcp-proxy@latestInstall the plugin
Download the latest EMCP Tools zip from the GitHub releases page, then use Plugins, Add New, Upload Plugin in WordPress and activate it. It needs WordPress 6.9+ and PHP 8.1+.
Create an application password
In WordPress admin go to Users, Profile, Application Passwords and create one for the agent.
Add the proxy config
Put the config above in your client's MCP file, with your own site URL, username and application password.
Keep the secret out of git
Treat the application password as a secret and keep it out of any file you commit.
Restart and test
Restart the client, then ask the agent to list the tools it can use on your site.
Client configuration
{
"mcpServers": {
"emcp-tools": {
"command": "npx",
"args": ["-y", "@msrbuilds/emcp-proxy@latest"],
"env": {
"WP_URL": "https://your-site.com",
"WP_USERNAME": "your-username",
"WP_APP_PASSWORD": "your application password"
}
}
}
}Endpoints and ports
npx -y @msrbuilds/emcp-proxy@latestRuns the proxy on the same machine as your MCP client.WP_URL, WP_USERNAME, WP_APP_PASSWORDEnvironment variables for one WordPress site.EMCP_SITES or EMCP_SITES_FILEJSON registry of aliases to site credentials.EMCP_DEFAULT_SITEAlias to start on, defaults to the first entry.https://emcptools.com/docs/Plugin documentation and per-client guides.What you can do with it
- Local stdio bridgeThe proxy runs next to your client and forwards requests to the site, so stdio-only clients can reach a remote WordPress site.
- Handles sessions and permalinksIt manages the session lifecycle and detects pretty or plain permalinks for you.
- Multi-site modeA site registry lets one connection drive several installs, with a separate session per site initialized on first use.
- Application password authThe agent authenticates as a WordPress user, and the plugin runs a capability check before each tool.
- Safe by defaultPer the plugin README, writes, deletes and site-wide renders ship disabled and are opt-in. Destructive operations need confirm set to true.
- Debug log optionSet MCP_LOG_FILE to write a debug log when a connection misbehaves.
- Protocol overrideSet MCP_PROTOCOL_VERSION to 2024-11-05 if your client rejects the adapter's newer default.
Tools it exposes
emcp_list_sites
Lists the configured sites and shows which one is active. Appears only when more than one site is configured.
emcp_use_site
Switches the active site, so every later tool call targets it. Multi-site mode only.
Plugin tools
All other tools come from the EMCP Tools plugin on your site, so the list depends on the plugin version and which tool groups you enable.
Frequently asked questions
What is the EMCP proxy?
It is a Node.js stdio bridge published with the EMCP Tools WordPress plugin. It lets MCP clients that only speak stdio reach the plugin's HTTP MCP endpoint on a remote WordPress site, handling authentication and sessions along the way.
How do I set up the EMCP proxy?
Install and activate the EMCP Tools plugin, create an application password in WordPress, then add a server entry with command npx and args -y and @msrbuilds/emcp-proxy@latest. Set WP_URL, WP_USERNAME and WP_APP_PASSWORD in the env block and restart your client.
Does the proxy run on my WordPress server?
No. The README says it must run on the same machine as your MCP client, because the client launches it as a local subprocess. The WordPress server only needs the plugin and an application password.
Can one connection manage multiple sites?
Yes. Set EMCP_SITES to a JSON map of aliases to credentials, or point EMCP_SITES_FILE at a file. With more than one site, the emcp_list_sites and emcp_use_site tools appear so you can switch sites mid-session.
Is it safe to let an agent edit a live site?
The plugin runs a WordPress capability check on every tool, ships writes and deletes disabled until you enable them, and requires confirm true for destructive operations. Still, test on a staging copy first, because the agent acts as a real user.
Which AI coding agents work with it?
The proxy README names Claude Desktop, Claude Code and Cursor, and the plugin docs add guides for VS Code and others. Any client that can launch a stdio command should work, though only the named ones are documented.
Do I need Elementor installed?
No. The README says Elementor is optional and every WordPress domain works without it, but installing Elementor adds the page-building tools. Other page builders have their own integrations, and Pro adds more.
Does it work with the WordPress MCP Adapter?
The plugin builds on the WordPress MCP Adapter, which ships bundled, so you do not install it separately. The Abilities API needs no separate install either. For design direction before the agent builds pages, pair it with a skill such as frontend-design.