A brief becomes a real page.Fix sign-in and permission errors
Work through browser approval, Application Password, and access failures.
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
- Access to the affected site and AI connection.
- A redacted copy of the exact error.
Let’s do this, step by step.
Step 01
Read the actual error
Record the error code and whether the response came from WordPress or a hosting/security page.
An unauthorized response often points to credentials. A forbidden response can come from permissions or a firewall, so inspect the message before changing accounts.
Step 02
Check the password route
For Application Passwords, verify the username and a current password from Users → Profile. Regenerate the client configuration in EMCP.
Use a connection-specific password, not your normal login password. Avoid manual encoding mistakes by copying the generated configuration.
Step 03
Check browser sign-in settings
Open Connection → MCP → Advanced settings. Check OAuth sign-in and Save. HTTPS is required for ordinary hosted sites. In the wizard choose the correct client and OAuth.
Check the OAuth sign-in switch and your secure site address. Then restart the setup for the correct client and approve the intended WordPress account.
Step 04
Use the matching server test
On Step 4, after No call yet or a failed call, click Run a server test. OAuth checks discovery; Application password tests the real MCP handshake. Inspect Errors in Safety → MCP Log.
Use the test that matches your sign-in method. A password working on an ordinary WordPress address does not prove the MCP connection works. Read the specific failure and ask your host about the affected path if it is blocked.
Step 05
Handle an old registration
Update an affected old EMCP version. If the app still reports an invalid client or return address, remove that connector and add it again.
Start a fresh registration after the update. Repeatedly clicking Approve on a stale connection may not fix it.
Step 06
Check the denied operation
If listing works but a particular action fails, inspect that tool's enabled setting and the connected user's permissions.
A working sign-in does not give every user access to every action. Reconnect and verify the same read-only task after the fix.
You’re done when…
The same identity can complete sign-in and run the intended permitted read.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.