Browser connector, Hosted, public HTTPS
Connect Claude to WordPress. claude.ai, Desktop or Code, one site policy.
To connect Claude to WordPress, add a custom connector that points at your own site's MCP endpoint. You sign in with OAuth 2.1 in the browser, the connection runs from Anthropic's cloud straight to your domain with no GoBuildWP relay in between, and the site decides what Claude may do.
Checked against Claude on the web's documentation on 29 September 2026, entries from GoBuildWP Free 1.18.6
Name gobuildwp-your-site-com
Remote MCP server URL https://your-site.com/wp-json/mcp/wppilot-oauth
OAuth Client ID (leave empty)
OAuth Client Secret (leave empty)- Add in
- Customize, Connectors, Add custom connector
- Calls from
- Anthropic's cloud, IPv4, 160.79.104.0/21
- Plans
- Free (one custom connector) and up
Setup
Add WordPress as a Claude connector
Everything below happens in the browser. The site must answer on public HTTPS, because Anthropic's servers make every call.
Free, Pro or Max: open Connectors
Customize, then Connectors, then Add custom connector. The Free plan allows one custom connector, so remove an unused one first if the button is greyed out.
Team or Enterprise: an Owner adds it
Organization settings, Connectors, Add, Custom, then Web. Members afterwards find it under Customize, Connectors and press Connect to sign in as themselves.
Enter the name and URL
Paste the values from GoBuildWP's Connect screen. Leave the OAuth client ID and secret empty so Claude uses its own published identity. Authentication settings cannot be edited later; a change means removing and re-adding the connector.
Sign in on your WordPress site
The login and consent screen are served by your own site. Approve as a dedicated WordPress user; the connection inherits that user's capabilities and nothing more.
Enable it in a conversation
Use the + button in the chat, open Connectors and switch the site on. The same menu turns it off.
Verify the connection before allowing changes
Select Read Only explicitly; the default is Production Safe. Use a dedicated identity with manage_options on a single site, or superadmin on multisite. Match the named tool call, site URL and returned record ID against WordPress.
Use the gobuildwp-your-site-com MCP server in Claude on the web. Do not change anything.
1. Report the active GoBuildWP safety profile.
2. List the abilities this connection can see.
3. Call wppilot/get-site-settings and report the site URL and locale.
4. Call wppilot/list-content for the five newest pages,
then wppilot/get-content on one of them.
5. Name every ability you called and each WordPress ID you read.These setup instructions are not a recorded live-client test. Keep credentials out of repositories, logs and shared files.
Inside Claude on the web
Which Claude, which sign-in, and what to do when it will not connect
Claude reaches WordPress from three places, and the route differs. Claude on the web adds your site as a custom connector and signs in with OAuth 2.1 from Anthropic's cloud, so the site must answer over public HTTPS. Claude Desktop uses the same connector screen and can also install a .mcpb bundle. Claude Code adds the server with one terminal command and runs OAuth from /mcp, or sends an access token when no browser is available.
Connector traffic comes from Anthropic's published range, 160.79.104.0/21, over IPv4 only. A firewall or security plugin that blocks that range, a site that resolves only to IPv6, or a redirect to another host all fail. A cross-host redirect is the subtle one: the Authorization header is dropped, and Claude reports that authorization with the MCP server failed.
When the connector fails, run the Connection Doctor from GoBuildWP's Diagnostics screen, or ask Claude to call wppilot/connection-doctor over a working route. It looks for a firewall or Cloudflare rule, ModSecurity, a stripped Authorization header, Application Passwords switched off, OAuth clock skew or a URL mismatch, and gives the fix for the server it runs on.
WordPress.com also has its own Claude connector for sites hosted there or connected through Jetpack. If your site already lives on WordPress.com, compare that route first; GoBuildWP is for self-hosted sites that want the rules, the change log and undo on their own server.
Signs it worked
- The connector URL is your site's public HTTPS MCP endpoint
- The OAuth sign-in happens on your own WordPress site
- The first answer reports the Read Only profile
- A write attempt is refused until you change the profile on the site
Troubleshooting
Claude on the web errors and their causes
| Symptom | Cause and fix |
|---|---|
| Couldn't reach the MCP server | Anthropic's cloud cannot open the URL. Check public DNS, a trusted certificate, IPv4 reachability and that 160.79.104.0/21 is not blocked by a firewall, Cloudflare rule or security plugin. |
| Authorization with the MCP server failed | A redirect is one common cause: apex to www, HTTP to HTTPS, or a changed site URL can drop the Authorization header. Open the URL you entered and check whether it redirects; if it does, enter the exact URL the site answers on. If it does not, read the error the app returns and the site's OAuth discovery at /.well-known/oauth-authorization-server. |
| Sign-in loops back to the login screen | Confirm /.well-known/oauth-authorization-server returns JSON and the server clock is correct. Clock skew makes freshly issued codes look expired. |
| The connector exists but Claude ignores it | It is off in this conversation. Enable it from the + menu, Connectors. |
| The Request headers section is missing | Header authentication is a beta limited to some organizations and set by an Owner. Use OAuth instead. |
Connect screen
The Claude on the web entries GoBuildWP writes
GoBuildWP gives claude.ai a connector walkthrough: a server name, the OAuth URL, and the instruction to leave the OAuth client fields empty. Claude then identifies itself with its published client metadata, because GoBuildWP's discovery document says it accepts Client ID Metadata Documents and public clients. The access-token route exists too, but it depends on a request-headers beta that only some organizations have.
| OAuth 2.1 | The recommended route. Claude uses its published identity (CIMD) against GoBuildWP; access tokens last an hour and refresh tokens fourteen days. |
|---|---|
| Access token | Request headers on the connector, set by an organization Owner where the beta is enabled. Type the value in full, Bearer and all; Claude sends it exactly as entered. |
Endpoints on your site: /wp-json/mcp/wppilot-oauth for OAuth, /wp-json/mcp/wppilot for tokens and passwords. Through the optional GoBuildWP Cloud instead, every client uses https://app.gobuildwp.com/mcp with the server name gobuildwp, and a personal Cloud token is read from GOBUILDWP_TOKEN where the client supports environment variables.
Remote MCP server URL https://your-site.com/wp-json/mcp/wppilot
Authorization Bearer wpp_YOUR-ACCESS-TOKENFirst task
A first chat that proves the whole path
Paste this into a new conversation with the connector enabled. It touches discovery, sign-in, schema lookup and WordPress permissions, and writes nothing.
Use my WordPress connector. Do not change anything.
1. Report the active GoBuildWP safety profile.
2. Call wppilot/get-site-settings: site URL and locale.
3. Call wppilot/list-content for the five newest pages,
then wppilot/get-content on one of them.
4. Name every ability you called and each WordPress ID
you read.Plans, teams and more than one site
One custom connector per site, or one Cloud link
Each custom connector points at one MCP URL, and a direct GoBuildWP URL belongs to one WordPress site. On the Free plan, where Claude allows a single custom connector, that means one site at a time. On paid plans you can add a connector per site, and each one has its own sign-in, its own entry in that site's Connected Apps screen and its own switch in the conversation menu, which keeps it obvious which site a chat is touching.
The alternative is the optional GoBuildWP Cloud link. It is added as a single connector, you sign in to Cloud rather than to each site, and inside Cloud you choose which connected sites Claude may reach and whether that access is read-only. The trade-off is one extra party in the path; a direct connector has no relay at all.
Team and Enterprise: map each member to their own WordPress user
When an Owner adds the connector for the organisation, every member still presses Connect and signs in as themselves. Give each person a WordPress account of their own rather than sharing one login (GoBuildWP only accepts administrator accounts, so each needs manage_options), so that the change ledger, Connected Apps and any later revocation all point at a person. wppilot/list-changes records the actor and the client behind every write, and wppilot/list-sessions groups a member's work into sessions whose supported changes can be undone together.
Agree on the profile before rollout: an organisation that only wants Claude to report on content can leave the site on Read Only, and a member's attempt to write is refused on the server whatever the chat says.
FAQ
Claude connector questions
Does claude.ai connect to WordPress directly?
Yes. The connector calls your site's MCP endpoint from Anthropic's infrastructure, with no GoBuildWP relay in between. That is why the site must be publicly reachable over HTTPS.
Is a connector added on claude.ai available in Claude Desktop?
Yes. Custom connectors belong to your Claude account, so one added in the browser appears in Desktop too, and either way the calls come from Anthropic's cloud.
Can I use an Application Password with claude.ai?
No. The connector offers OAuth, and request headers only where the beta is enabled for your organization. Keep Application Passwords for Claude Code or a Desktop bundle.
Is there a Claude WordPress plugin?
Not from Anthropic for self-hosted sites. Claude connects to any site that serves an MCP endpoint; GoBuildWP is a WordPress plugin that provides one, with the permissions, change log and undo kept on your server.
Does Claude Code work with WordPress?
Yes, and it reaches sites the web connector cannot, such as localhost, because it connects from your own machine. The Claude Code guide covers claude mcp add and its scopes.
Which IP addresses should my firewall allow for Claude?
Anthropic publishes 160.79.104.0/21 as the source range for connector traffic, and connectors use IPv4 only. Allow that range to the MCP endpoint and the /.well-known OAuth paths.
Related
Other Claude surfaces
- Claude Desktop setup: the same connectors, plus a local bundle
- Claude Code setup: one terminal command, no cloud hop
- WordPress.com MCP vs GoBuildWP: hosted versus self-hosted
- Mistral Le Chat: another browser assistant with custom connectors, set up by an administrator
- Connection troubleshooting: layer-by-layer checks
- Fix WordPress SEO with Claude: worked example
Claude on the web documentation read on 29 September 2026
Connect Claude with OAuth and keep the rules on your site.
Add the connector, sign in as a dedicated user, and let the first chat prove a read before anything is allowed to write.