PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free

Most MCP connection failures come from HTTPS, a blocked REST API or a host that strips the Authorization header. The Connections screen shows which one.

Updated November 18, 20263 min read

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.

CheckWhat a problem meansFix
PageForge MCPMCP is disabled, so every request is refusedTick the enable checkbox under MCP / AI Clients
HTTPSThe site address is not HTTPSInstall a certificate and update the WordPress Address and Site Address
REST endpoint reachableSomething blocks the WordPress REST APIAllow /wp-json/pageforge/v1/ in your security plugin, firewall or server rules
Authorization headerPHP may not receive the header that carries the tokenForward it (below)
Well-known discovery pathsWordPress is in a subdirectoryCurrent clients still work. Optionally proxy the two /.well-known/ paths to the URLs shown.
PermalinksPlain permalinks are onChoose any other option in Settings > Permalinks
Security pluginsA plugin known to block REST bearer tokens is activeAllow-list the MCP and OAuth endpoints in it, rather than turning it off
Client activityNo client has authenticated yetFinish setup in the client
Recent rejected requestsRequests reached PageForge and were refusedRead 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

CodeMeaning
401A 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.
403MCP is disabled, the browser origin was refused, or the connection lacks the scope for that tool
400The request body or protocol details were invalid
405The client probed with GET. This is expected and only a problem if the client then gives up.
429A 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/authorize are not cached or challenged by a bot filter.
  • Both headers. Send either Authorization: Bearer or X-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.

Was this page helpful?

↑↓ to move↵ to open