When ChatGPT, Claude or another client says it cannot connect, the cause is usually on the server side and invisible to the client. PageForge checks it from inside WordPress.
Start with the diagnostics
Go to PageForge > Connections and scroll to Connection diagnostics. The badge reads All checks passed, Review recommended or Action required, and anything that needs attention is listed with a suggested fix. Open Advanced diagnostics to see every check and your discovery URLs.
| Check | What a problem means | Fix |
|---|---|---|
| PageForge MCP | MCP is disabled, so every request is refused | Tick the enable checkbox under MCP / AI Clients |
| HTTPS | The site address is not HTTPS | Install a certificate and update the WordPress Address and Site Address |
| REST endpoint reachable | Something blocks the WordPress REST API | Allow /wp-json/pageforge/v1/ in your security plugin, firewall or server rules |
| Authorization header | PHP may not receive the header that carries the token | Forward it (below) |
| Well-known discovery paths | WordPress is in a subdirectory | Current clients still work. Optionally proxy the two /.well-known/ paths to the URLs shown. |
| Permalinks | Plain permalinks are on | Choose any other option in Settings > Permalinks |
| Security plugins | A plugin known to block REST bearer tokens is active | Allow-list the MCP and OAuth endpoints in it, rather than turning it off |
| Client activity | No client has authenticated yet | Finish setup in the client |
| Recent rejected requests | Requests reached PageForge and were refused | Read the status code (below) |
Forward the Authorization header
Some hosts running PHP through CGI or FastCGI drop the Authorization header before WordPress sees it. Every token then looks invalid. On Apache, add this to .htaccess:
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
On nginx with PHP-FPM, pass the header in the PHP location block:
fastcgi_param HTTP_AUTHORIZATION $http_authorization;
Clients that use a personal access token can also send it in the X-PageForge-MCP-API-Key header, which hosts rarely strip. ChatGPT and Claude always use Authorization, so they need the fix above.
Important Never work around a stripped header by putting a token in the URL. URLs end up in server logs, browser history and analytics.
Read the rejected requests
| Code | Meaning |
|---|---|
| 401 | A credential was sent and rejected, for example an old token, or a request that sent both token headers. Reconnect the client or create a new token. Sign-in discovery requests without a credential are normal and not listed. |
| 403 | MCP is disabled, the browser origin was refused, or the connection lacks the scope for that tool |
| 400 | The request body or protocol details were invalid |
| 405 | The client probed with GET. This is expected and only a problem if the client then gives up. |
| 429 | A rate limit was reached. Wait for the time in the response, or reduce how often the client polls. |
Other things to check
- Account rights. By default only administrators can connect AI clients. If the approving account was downgraded, its connections stop working. Reconnect with an administrator account.
- Public reachability. Claude and ChatGPT connect from their own servers. A staging site behind a password, VPN or IP allow-list cannot be reached. Claude also requires the standard HTTPS port.
- Caching and CDN. Make sure
/wp-json/pageforge/v1/and/pageforge-oauth/authorizeare not cached or challenged by a bot filter. - Both headers. Send either
Authorization: BearerorX-PageForge-MCP-API-Key, not both. - Wrong credential type. ChatGPT and Claude never accept a pasted token. Cursor, VS Code and Claude Code need a token, not OAuth client credentials.
When the diagnostics pass and Client activity shows a recent request, the connection is working. Ask the client “Show my PageForge site status” to confirm.
Next: Connect ChatGPT and Connect Claude.
