Choose your appLesson 8 of 9 · 6 steps

Connect Hermes

Configure EMCP in Hermes and reload the connection.

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 Hermes; 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 Hermes, 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

Open the configuration

Open ~/.hermes/config.yaml and locate mcp_servers. Copy the Hermes block from EMCP Connection.

Hermes uses an indented configuration format. Keep the spacing from the generated example and preserve your other settings.

Step 03

Choose authentication

Use only the full endpoint for supported OAuth sign-in, or the generated Application Password Authorization header.

For browser sign-in, approve WordPress when Hermes connects. For a password connection, keep the generated header private.

Step 04

Reload and test

Run /reload-mcp after saving. In the test command replace YOUR_SERVER_NAME with the generated name from the wizard.

Reloading makes Hermes read the new settings. The test should identify the server and available actions.

Copy and adapt

                    hermes mcp test YOUR_SERVER_NAME

Step 05

Try the proxy only if needed

For a direct-connection handshake problem, switch to the Node proxy block in the Hermes docs. Set WP_URL to the bare site address.

The proxy handles the conversation with WordPress. Run it on the computer hosting Hermes, and keep the password in the private configuration.

Step 06

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.