Choose your appLesson 7 of 9 · 7 steps

Connect OpenClaw

Add EMCP, complete sign-in, and handle the Windows connection options.

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

Start the four-step wizard

Open EMCP Tools → Setup → Connection → MCP. Check Server status. In Step 1 select OpenClaw; in Step 2 choose the sign-in method used below. OAuth needs HTTPS and OAuth sign-in enabled under Advanced settings, then Save.

Start on the intended WordPress site. In Connection, choose OpenClaw, then choose how to sign in. The following instructions are shown in Step 3. Keep the wizard open so we can verify the first call in Step 4.

Step 02

Add the server

Open ~/.openclaw/openclaw.json. Merge the generated mcp.servers configuration from EMCP Connection without replacing other settings.

Choose the OAuth configuration for an HTTPS site. It uses the complete endpoint, streamable-http, and auth set to oauth.

Step 03

Start the generated sign-in

Run the OpenClaw login command shown in Step 3, using the generated server name. Open its link and approve WordPress.

Use the exact connection name shown by your setup. Keep this attempt open while you approve it. Starting a second login can invalidate the first.

Step 04

Finish the same login

If OpenClaw asks for a code, copy only the code value and follow its completion command within five minutes.

Copy the part after code equals, ending before the next ampersand. Do not paste the entire callback URL into a terminal.

Step 05

Check or choose the proxy fallback

Run the probe below after replacing YOUR_SERVER_NAME with the name generated in Step 3. If direct HTTP cannot maintain the connection, use the generated password-based Node proxy fallback with the bare site URL in WP_URL.

A probe timeout alone is not proof the server is broken. Try a normal read-only session too. A password error and an HTML homepage response need different fixes.

Copy and adapt

                    openclaw mcp probe YOUR_SERVER_NAME

Step 06

Handle Windows command launching

If the proxy reports spawn npx ENOENT on Windows, use command cmd with args /c, npx, -y, @msrbuilds/emcp-proxy@latest.

Windows may need the command wrapper shown in the docs. Keep the username, Application Password, and protocol setting from the generated configuration.

Step 07

Confirm Step 4 with a real request

After adding the connection, click I’ve added it, continue in WordPress. Reload the app and send the read-only prompt. Check the wizard’s successful first call and compare records with Pages. On failure or No call yet, inspect the reason and Run a server test.

Return to WordPress and continue to Test the connection. Reload your app, then ask it to list pages. Check the wizard’s result and the actual page titles. A server test is a useful diagnosis if the call fails, but it does not prove the app completed its request.

Copy and adapt

                    Identify the connected WordPress site URL. List accessible pages with titles, IDs and status. Do not create, edit or delete anything.

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.