terraexperty
Forum Replies Created
-
Hi Jameson,
Update after extensive troubleshooting on SiteGround:
Current status:
✅ Royal MCP v1.4.14 fresh install
✅ PHP 7.4.33
✅ /.well-known/oauth-authorization-server → HTTP/2 200
✅ /.well-known/oauth-protected-resource → HTTP/2 200
✅ /wp-json/royal-mcp/v1/mcp → HTTP/2 401 (correct)
✅ WpResidence theme updated to v5.6
❌ OAuth flow never completes — debug.log shows NO activity during authorization attempts
❌ Claude.ai returns: ‘Authorization with the MCP server failed’
Latest error ref: ofid_234d00cf310dabfb
The requests from Claude.ai never reach WordPress PHP during the OAuth handshake. We have been working on this for several days. Could you please provide the exact working configuration for SiteGround hosted sites?
Best regards,
René — Terra ExpertyHi Jameson,
We have identified the exact problem. When adding the connector with ONLY the MCP URL (no OAuth credentials), Claude.ai returns ‘Couldn’t reach the MCP server’ WITHOUT showing the authorization window.
The MCP endpoint returns HTTP/2 405 on GET requests:
curl -i https://terraexperty.com/wp-json/royal-mcp/v1/mcp → HTTP/2 405
We believe Claude.ai first sends a GET request to verify the server is reachable. Since it gets a 405, it considers the server unreachable and never starts the OAuth flow.
When we add OAuth Client ID and Secret manually, the authorization window DOES appear but fails with ‘Authorization with the MCP server failed’ — suggesting Claude.ai skips /register and sends an unknown client_id directly to /authorize.
Questions:
1. Should the MCP endpoint return 200 on GET requests?
2. Is there a way to pre-register Claude.ai’s client_id in Royal MCP?
Error ref: ofid_b8f0d40261cecb59
Best regards,
René — Terra ExpertyHi Jameson,
Complete technical findings after extensive testing:
✅ /.well-known/oauth-authorization-server → HTTP/2 200
✅ /.well-known/oauth-protected-resource → HTTP/2 200
✅ /register → HTTP/2 201 (dynamic registration works)
✅ /authorize → reaches WordPress (x-httpd: 1)
❌ /authorize → returns ‘Unknown client_id. The application has not been registered’
❌ Activity Log always empty
❌ Claude.ai never calls /register automatically before /authorize
❌ Result: ‘Authorization with the MCP server failed’
Root cause identified: Claude.ai attempts /authorize directly without first calling /register to obtain a valid client_id. Royal MCP rejects the unknown client_id.
Question: Should /register be called manually before connecting? Or should Royal MCP accept unknown client_ids and register them on the fly during /authorize?
Error ref: ofid_f0f889e086a13da4
Best regards,
René — Terra ExpertyHi Jameson, SiteGround confirmed the /.well-known/ files don’t exist on the server. Could you provide the exact content needed for these two static files so we can create them manually in the webroot?
– /.well-known/oauth-authorization-server
– /.well-known/oauth-protected-resourceBest regards, René — Terra Experty
Hi Jameson,
Here are the curl headers for the OAuth endpoint:
HTTP/2 404
server: nginx
x-cache-enabled: False
x-proxy-cache-info: DT:1
access-control-allow-methods: GET, POST, OPTIONS
access-control-allow-origin: *
Cache is disabled for this URL after adding the SG Optimizer exclusions. Activity Log is still empty after retrying the connection. What should we check next?
Best regards,
René — Technical Support, Terra ExpertyHello Royal MCP team, I hope you are doing well.
My name is René, technical support at Terra Experty, and I am reaching out because we are experiencing issues connecting our WordPress site (terraexperty.com) with Claude.ai using the Royal MCP plugin.
The specific problem is that the OAuth authorization fails right after clicking ‘Authorize’. The authorization window appears correctly and we can confirm that the MCP endpoint responds properly to HTTP POST requests, however Claude.ai always returns the error ‘Authorization with the MCP server failed’.
We have tried the following without success: regenerating OAuth credentials, removing Cloudflare from the domain, reconnecting the connector multiple times, and creating a custom connector with a Bearer Token.
Our site is hosted on SiteGround with self-hosted WordPress. Could this be a compatibility issue with SiteGround or with the OAuth callback URL?
We truly appreciate your help and look forward to any solution you can suggest.
Best regards,
René
Technical Support — Terra Experty
terraexperty.com