Agent connection problems
Check where the connection stopped before changing access or repeating setup. Adding MoraWP's address, approving OAuth, and enabling the service in a chat are separate steps.
No browser sign-in opens
Confirm the server address is exactly:
https://api.morawp.com/mcp
Use your app's guide to start OAuth. The app must support a remote HTTP MCP server with browser authorization; a static token field cannot replace that flow.
If the app prints an authorization link instead of opening the browser, follow its instructions to open the link and finish sign-in. Treat the link and its callback as private; do not post them in support messages.
Approval expired, was cancelled, or cannot continue
Start authentication again from the AI app to create a fresh request. Reloading an expired approval page does not create another request.
On the new MoraWP page, check the app and Workspace, select the intended websites, and review the required data-access acknowledgment. Approve connection stays unavailable until that acknowledgment is checked. If MoraWP asks you to choose at least one website, review the selected list.
Authorization succeeded, but the app has no tools
- Check Agents in the Workspace you approved.
- Confirm that the AI app uses the same server configuration you authorized. A project-specific CLI entry may not appear in another project.
- Enable MoraWP in the current conversation or MCP session, as shown in your app's guide.
- If the app keeps an old tool list, refresh it or start a new conversation.
Ask for a list of allowed websites without making changes. If the connection works but a website or Ability is absent, continue with Missing Abilities.
The wrong Workspace or website appears
Compare the approved Workspace with the one open in the Dashboard. Each Agent connection belongs to one Workspace; connecting the same AI app does not merge their access.
Review the connection's website access. To authorize a different Workspace, start a new sign-in and review the new request. Disconnect a mistaken connection if it should not remain authorized.
Prepare useful error details
Keep the app name and version, time and timezone, the step that failed, and the error message or request identifier if provided. Do not include tokens, authorization or callback URLs, cookies, or private website content.
A successful sign-in verifies authorization, not the outcome of a WordPress action. For an execution failure, use WordPress tool failed.