Connect Claude Desktop
Choose the one-click bundle or browser sign-in, then test your 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.
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 Desktop; 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 Desktop, 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
Create a desktop bundle
In Step 2 choose Application password. Select Administrator, click Create password, then Download .mcpb bundle in Step 3.
Choose Application password and create a separate password for the intended administrator. Download the desktop bundle. It contains a live credential, so keep it private.
Step 03
Install the bundle
Double-click the downloaded .mcpb file and finish Claude Desktop's installation flow.
Claude Desktop opens the bundle and installs the connection. This route includes its own runtime; you do not need to install Node separately.
Step 04
Or use a custom connector
For the browser route, open Claude Desktop → Settings → Connectors → Add custom connector. Enter a name and the complete server URL.
Use this instead of the bundle if custom connectors are available in your app. Leave the advanced client ID and secret empty, then approve the WordPress sign-in.
Step 05
Check tools and clean up
Check Available tools near the chat input. After a successful bundle import, delete the downloaded credential-bearing bundle.
Look for your EMCP connection in the tool list. If it is missing, restart the app and inspect the connection error. Do not send the bundle to support.
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.