Connect Cursor
Add EMCP to the right Cursor project and verify which WordPress site it reaches.

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
- 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 Cursor; 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 Cursor, 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
Choose the scope
Use .cursor/mcp.json in your project for a project connection, or your home .cursor/mcp.json for a connection shared across projects.
A project connection is easier to keep associated with a client project. Name staging and production clearly. The name itself does not prove which site is connected.
Step 03
Add EMCP
In Step 3 use One-click install and inspect the proposed server, or merge the generated block into the chosen .cursor/mcp.json file.
Click One-click install and check the site address before accepting. If you use the configuration file instead, keep any other servers already in it.
Step 04
Sign in
Open Cursor's MCP management screen and complete browser sign-in as the intended WordPress administrator.
Cursor may place its MCP screen under different settings labels as it changes. Find the server, start authentication, and approve the correct WordPress site.
Step 05
If browser sign-in is unavailable
Generate a Cursor Application Password configuration in EMCP Connection. Replace the connection's configuration and reconnect.
This alternative uses a separate password. Do not paste it into the chat or commit it with your project. Revoke it from WordPress when you no longer need it.
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.
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.
A brief becomes a real page.