Choose your appLesson 2 of 9 · 6 steps

Connect Claude Code

Add the WordPress server from the terminal and complete browser approval.

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 Claude Code; 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 Claude Code, 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 generated server

For OAuth, copy the Claude Code command from Step 3 and run it in your project terminal. Use its generated site-specific server name and complete endpoint.

Copy the command from this site’s setup screen. It supplies the correct address and connection name. Run it in your project, then finish the browser sign-in.

Step 03

Approve sign-in

Start Claude Code and complete the browser approval when the connection requests it.

Check the site address and account on the approval screen. Approve once, then return to Claude Code.

Step 04

Check the connection

Run claude mcp list. If sign-in is needed, open /mcp inside Claude Code and finish authentication.

The connection list should show EMCP available. The Claude Code extension can reuse this configuration. A separate local WordPress route is covered in the local connection lesson.

Copy and adapt

                    claude mcp list

Step 05

Use the password fallback if needed

For a password connection, copy the Claude Code configuration from EMCP Connection into the project's .mcp.json, preserving other servers. Restart.

Use a separately generated Application Password. The generated configuration handles its header for you. Keep the file private if it contains credentials.

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.