An MCP client cannot connect

Test the site endpoint before debugging individual tools.

Endpoint check

Use the MCP URL displayed under Settings → POM AI → MCP server. Its path ends in:

/wp-json/pom-ai-mcp/v1/mcp

An authenticated or readiness GET should reach POM AI. Confirm:

• the MCP server setting is enabled;
• the URL belongs to the intended multisite subsite;
• WordPress REST requests work;
• HTTPS and the certificate are accepted by the client;
• no firewall or security plugin blocks the route;
• the client sends a supported protocol version.

Discovery and OAuth 404

The MCP endpoint can answer while discovery or OAuth URLs return 404. Check the status field permalinks_enabled and configure Settings → Permalinks. Hosting rewrite rules may also need attention.

Browser-origin clients

If the client runs from a browser origin, that exact origin must be in the configured MCP allowed-origin list. Do not add * to work around a failed preflight.

Once initialize succeeds, refresh tools/list, resources/list, and prompts/list. A later tool error is an authorization or schema issue, not a connection failure.

Related guides: MCP transport, permalink boundary, and authentication fails.