A brief becomes a real page.Connect an AI agent: the complete setup path
Prepare WordPress, choose your app, sign in, and verify the first request.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP installed and active.
- An AI app with MCP support.
- Administrator access for browser sign-in.
Let’s do this, step by step.
Step 01
Open the connection wizard
Open EMCP Tools → Setup → Connection → MCP. In the right-hand Advanced settings, enable Abilities API if needed and click Save. Check Server status.
Open EMCP Tools, then Connection under Setup. Choose MCP. If the server is off, open Advanced settings, switch on Abilities API, and click Save.
Step 02
Choose your AI client
Under Choose your AI client, select the app you use. Open its matching academy lesson for the app-side steps.
Choose your app first. The next steps change to match it. Follow one app route from start to finish.
Step 03
Pick how it signs in
Choose OAuth for browser approval, or Application password. OAuth needs HTTPS and OAuth sign-in enabled in Advanced settings. WP-CLI on this computer appears only for supported clients on local/development sites.
Browser sign-in is the recommended route on a secure website. A connection password is an alternative. The local computer option is for supported apps running beside your local WordPress installation.
Step 04
Create a password only for that route
For Application password, select the intended Administrator and click Create password. Or choose Use a password I already have, select Which password and enter Its password. Keep credentials private.
This password is separate from your normal WordPress password. Create it for the chosen administrator and keep it private. You can also supply an existing application password.
Step 05
Add EMCP to the app
Follow Add EMCP to your client. Copy the generated name and configuration, or use the offered install button. For OAuth choose A new app, or Reconnect an app that is already connected when appropriate.
Use the name and settings generated for this site. The name may include your site address. Complete the app instructions and browser approval, then return to WordPress.
Step 06
Test the connection
Click I’ve added it, continue. Reload the client and send the read-only prompt. Wait for the client-specific connected result and first call time. Compare returned records with WordPress.
Click I have added it, continue. Reload your app and ask it to list the site’s pages. The wizard confirms the first successful call from this setup. Check the site address and page titles too.
Identify the connected WordPress site URL. List pages I can access with titles, IDs and status. Do not create, edit or delete anything.
Step 07
If the first call does not arrive
On No call yet or a failed call, read the reason and use Run a server test for OAuth or Application password. OAuth tests discovery; the password route tests the MCP handshake. An expired setup offers Start again after 30 minutes.
A server test helps check the WordPress side, but it does not replace a successful request from your app. Read the result, fix the stated problem, and try the same read again. If setup has expired, choose Start again.
Step 08
Know how to end access
In Connected apps, Sign out revokes OAuth tokens; Remove also deletes the app registration. Application Passwords can be revoked under Users → Profile.
Sign out ends the app’s current access, though it can sign in again. Remove also removes its registration. For a password connection, revoke its application password in WordPress.
You’re done when…
The app returns real records from the intended site, and you know where to revoke its access.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.