The missing Authorization header on shared hosting
Why some hosts drop it, how to tell, and the three-line fix.
Claude signs every request to your site with a key in the Authorization header. On many shared hosts, PHP runs behind Apache through CGI or FastCGI, and that header is quietly removed before WordPress gets the request. WordPress then sees an anonymous visitor, and every tool call fails as if the key were wrong.
How to tell
- Sign-in finishes, but the first tool call returns 401 Unauthorized.
- Revoking and reconnecting changes nothing.
- Claude Connection → Setup → Run server check reports that the Authorization header did not arrive.
The fix
Tell Apache to pass the header on to PHP. These lines go near the top of .htaccess, above the WordPress block:
<IfModule mod_rewrite.c>
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
</IfModule>
You do not have to edit the file by hand: the server check offers to add the fix for you, saves a backup copy of .htaccess first, and runs the test again so you can see it worked.
If it still fails
- On Nginx there is no
.htaccess; ask your host to pass the header to PHP-FPM. - A security plugin or firewall may block the REST API for unknown clients. Allow
/wp-json/fbsa/v1/. - Check that the connector address is the full endpoint, ending in
/wp-json/fbsa/v1/mcp.
