Choose your appLesson 9 of 9 · 7 steps

Connect a local WordPress site

Choose between the local WP-CLI bridge and a local proxy for a remote site.

Video coming soon

Your next step is ready.

Follow the complete written guide below.
The video will join it here when it’s ready.

Start the written lesson

Before you start

Complete Install EMCP Free and Pro and Connect an AI agent.
Have the named app installed with MCP support available.

Let’s do this, step by step.

Step 01

Choose the right route

Use the WP-CLI bridge when WordPress and the AI client run on the same computer. Use the Node proxy for a remotely hosted WordPress site.

Local bridge and proxy sound similar, but they solve different jobs. A client cannot launch a file that exists only on your hosting server.

Step 02

Verify WP-CLI

For a local site, verify WP-CLI can list emcp-tools-server using the real WordPress root path.

The path should point to the folder containing wp-config.php. EMCP bundles the adapter, so first check that EMCP itself is active.

Copy and adapt

                    wp mcp-adapter list --path=/absolute/path/to/wordpress

Step 03

Generate the local configuration

On a local/development site, open Connection → MCP. Choose Claude Desktop, Claude Code, Cursor or Antigravity, then WP-CLI on this computer. Copy the generated Step 3 configuration, including EMCP_SETUP, into that app.

Choose one of the supported local apps, then WP-CLI on this computer. Copy its generated configuration. The setup marker lets the wizard recognize the first call; it is not a password.

Step 04

Set Windows paths before copying

If needed, set Connection → 3rd-party services → WP-CLI command to your local PHP and WP-CLI paths, then Save changes. Return to the wizard and copy the updated command.

Use paths from your own computer. Save the command before copying the setup. Keep the real WordPress folder and user in the generated configuration.

Step 05

Remote-site alternative

For a remote site, use the client-specific Node proxy configuration. Install Node on the client computer and supply a bare WP_URL plus an Application Password.

The proxy runs beside your AI app and talks to the remote site. The one-click Claude Desktop bundle is an easier alternative when you use that app.

Step 06

Check with a real request

Open a new conversation and send the prompt. Compare its answer with Pages in WordPress.

We are connected when the app can read actual records from this site. Check the site address and page titles. Leave editing for the next lesson.

Copy and adapt

                    Identify the WordPress site URL. List pages with titles, IDs and status. Do not make any changes.

Step 07

Confirm the local first call

Click I’ve added it, continue. Reload the local client and make a read-only call. Check Step 4 and Safety → MCP Log. The WP-CLI route has no Run a server test button.

Return to the wizard and test the local connection with a real request. Its calls also appear in MCP Log.

You’re done when…

The app reads real page records from the intended site without changing anything.

Keep the reference handy.

The docs cover tool details and requirements for this lesson.

You only need the guide for the app or builder you use. Ready to build? Try an Elementor draft or use Gutenberg.