By Fahad Murtaza · Published
Claude custom connectors: add WordPress as one
“Connectors” is Claude’s name for the way it reaches tools outside the chat window. Some connectors are in a directory and install with a click. A custom connector is the other kind: you give Claude the web address of any remote MCP server, and it can use that server’s tools in your conversations.
That makes a WordPress site a valid connector, as long as the site runs an MCP server and is reachable from the internet. This guide covers how connectors work, how to add your site as one, what trips people up, and how to keep the access safe. The site side uses WP MCP, a WordPress plugin that turns a site into an MCP server.
How do I add a custom connector to Claude? On Pro and Max, open Customize, go to Connectors, click Add and choose Add custom connector, then enter the server’s URL. On Team and Enterprise plans an owner adds it under Organization settings, Connectors, and members then connect it. If the server asks for sign-in, you approve access in a browser window. After that, the connector’s tools are available in your chats.
What a custom connector is
An MCP server is a program that lists tools and runs them when asked. If the term is new, read what an MCP server is first. A client such as Claude connects, asks for the list, and lets the model decide which tool to call.
There are two ways a client can reach a server:
- Locally, by starting a program on your machine and talking over standard input and output. This is called stdio.
- Remotely, over HTTPS to a URL. This is what a custom connector uses.
A custom connector is the remote kind, added from Claude’s settings rather than from a config file. That has two practical consequences. First, the server must be reachable from the internet, because the connection is made from Anthropic’s infrastructure and not from your laptop. Second, the sign-in happens in the connector dialog rather than in a config file. Claude’s help describes OAuth as the usual way, with an option to supply fixed request headers for servers that use an API key or bearer token. WP MCP’s documented connector route is OAuth, so that is what this guide uses.
The remote MCP server article explains the difference between local and remote in more detail.
Connector, config file or Claude Code: which route
You have three ways to connect Claude to a WordPress site. They differ in who makes the request, how you sign in and where the credential lives.
| Route | Sign-in | Needs | Good for |
|---|---|---|---|
| Custom connector (claude.ai or Claude Desktop settings) | OAuth, approved in the browser | A public site URL and OAuth switched on | Using Claude in the browser or on a phone without touching files |
| Claude Desktop config file or desktop bundle | Application password | Claude Desktop, and Node.js for the config route | A site that is not public, or a setup you want to script |
| Claude Code | Application password in a header | One command or a .mcp.json entry |
Developers working in a terminal |
The Claude clients are the most tested path for WP MCP. If you only want it working in the next two minutes on a default install, an application password in Claude Code or the desktop bundle is shorter. Choose the custom connector when you want OAuth, no stored password, and access that works from the Claude apps everywhere.
Before you start
You need:
- A WordPress site on a public HTTPS address. A site on
localhost, a VPN-only host or a staging server behind a login wall cannot be reached by the connector. - WP MCP installed and active. The safety engine and 274 tools are in the free plugin; 133 more are Pro. See pricing for what Pro adds.
- WordPress 6.9 or later and PHP 8.1 or later.
- Access to edit
wp-config.php, or to add a small plugin, to switch OAuth on. - A Claude plan that lets you add custom connectors. Claude’s help lists Free (limited to one custom connector), Pro, Max, Team and Enterprise, and on Team and Enterprise an owner has to add it. Plans change, so check Claude’s help on custom connectors for your account.
- A server reachable from the public internet on port 443, because the connection is made from Anthropic’s cloud even when you use Claude Desktop.
Step 1: switch OAuth on
WP MCP ships a full OAuth 2.1 authorization server with PKCE and dynamic client registration, and it is off by default. It stays off until the site owner opts in. With it off, the connector fails with “Couldn’t register with WP MCP’s sign-in service”, because the discovery addresses answer 404.
Add one line to wp-config.php, above the line that says to stop editing:
define( 'WPMCP_OAUTH_ENABLED', true );
If you would rather not edit that file, a small plugin or mu-plugin can use the filter instead:
add_filter( 'wpmcp_oauth_enabled', '__return_true' );
Check that it worked by opening the protected-resource discovery address in a browser. On a site at the domain root it is:
https://your-site.com/.well-known/oauth-protected-resource/wp-json/mcp/wpmcp-server
A JSON document means OAuth is on. A 404 means it is not, or that a caching layer or security rule is intercepting .well-known paths. The Connection screen under WP MCP in wp-admin lists the exact discovery addresses for your site, including sites installed in a subdirectory.
The article on MCP OAuth explains what these addresses are for.
Step 2: add the connector
- In Claude, open Customize and choose Connectors. Older versions put Connectors under Settings. On Team and Enterprise, an owner adds it under Organization settings, Connectors, and you then click Connect on it.
- Click Add, then Add custom connector.
- Give it a name, for example
My WordPress site. - Enter the endpoint as the URL:
https://your-site.com/wp-json/mcp/wpmcp-server
- Leave any OAuth Client ID and client secret fields empty, and do not choose “Use your own OAuth client”. WP MCP supports dynamic client registration, so Claude can register itself. If Claude offers a choice of how to register, “Register automatically” matches this.
- Click Connect.
A browser window opens on your own site. Log in as the WordPress user the connector should act as, then approve the request.
Step 3: choose what Claude may do
The approval screen is where the safety choice sits. WP MCP offers:
- Full access: the token can do what your WordPress user can do (the
mcpscope). - Read-only: the token may list and read, and is refused anything that changes the site (the
mcp:readscope). - A scoped identity, for site owners: the connection is bound to one of your scoped identities, so its permissions are the ones you defined for it.
For a first run, choose read-only. A token never gains scope when it is refreshed, and lowering a connection’s access on the Connection screen takes effect on its next request, without reconnecting.
Use a dedicated WordPress user for the connection, not your own administrator account. Then the connector can be revoked on its own, and the audit log shows its actions under a separate name.
Step 4: test it
Start a new chat, make sure the connector is enabled for it, and ask something that proves the connection and the sign-in:
List the post types on my site, then show my five most recent published posts.
Claude should call tools such as list-post-types and list-posts. You can see which tool was called in the chat, and the same calls appear on the Audit Log screen in wp-admin, on the Requests tab, with the calling client and whether each call succeeded.
Then try a small write, if you chose full access:
Create a draft post called "Connector test" with one paragraph that says hello.
Then change the title to "Connector test 2".
Each supported write is snapshotted before it happens and returns an operation id. To undo it, ask Claude:
List the last five operations, then undo the title change.
That uses list-operations and rollback-operation. You can also press Restore beside the operation in wp-admin. To unwind everything an agent did in one conversation, use rollback-session. Some changes cannot be snapshotted, such as package updates and raw database row writes. Those are off by default and say so in their response. The revisions and undo guide compares the options.
Troubleshooting
“Couldn’t register with WP MCP’s sign-in service.” OAuth is off. Do step 1 again and open the discovery address to check.
The sign-in page never opens, or loops. A caching plugin or a CDN rule may be caching or blocking the authorization pages. Exclude the WordPress REST route and the .well-known paths from caching, and check that a security plugin is not blocking the registration request.
The connector connects but no tools appear. Check the plugin version first. An older release sent a tool list that some clients rejected as a whole, so the chat showed zero tools while Settings listed them. Update the plugin, remove the connector and add it again. If it persists on a current version, look in the web server log while Claude lists tools: if no request arrives, the app is not asking your site, and the Claude Desktop config route is a working alternative.
You get a 401 after it worked. The token was revoked, the user was changed, or the connection’s access was lowered. Reconnect from the Connection screen’s list.
It cannot reach the site at all. The URL must be public HTTPS with a valid certificate. Test it from a network that is not your own.
To see the raw protocol messages when something is unclear, run the same endpoint through MCP Inspector.
Keep the connector safe
A connector is a standing credential, so treat it like one.
- Prefer read-only until you trust the workflow.
- Give the connected user the lowest role that does the job.
- Pin a scoped identity to the addresses you expect, where you can. WP MCP can restrict an identity to IP ranges, though a hosted client’s addresses may not be stable, so check before relying on it for Claude.
- Revoke connections you no longer use from the Connection screen.
- Read the MCP security checklist for WordPress before you give any agent write access to a client site.
When a connector is the wrong tool
If you work in a terminal, Claude Code with an application password is simpler, and it keeps the credential in your own config. If the site is private, use the Claude Desktop route with the bundle or the config file. A connector earns its place when you want the Claude apps themselves, on any device, to reach a public site through OAuth.
For what the server exposes once connected, see the WordPress MCP server page.
Choosing a sign-in method? See MCP authentication methods compared.
Common questions
What are Claude connectors?
Connectors let Claude reach outside services and tools through the Model Context Protocol. Some are listed in a directory you can add with a click, and a custom connector lets you add any remote MCP server by its URL.
How do I add a custom connector in Claude?
On Pro and Max, open Customize, go to Connectors, choose Add, then Add custom connector, enter the server URL and connect. On Team and Enterprise an owner adds it under Organization settings, Connectors. If the server uses OAuth, a browser window opens so you can sign in and approve access.
Can I connect Claude to my WordPress site as a custom connector?
Yes, with a WordPress site that runs an MCP server and has OAuth enabled. With WP MCP, switch OAuth on first with WPMCP_OAUTH_ENABLED, then add https://your-site.com/wp-json/mcp/wpmcp-server as the connector URL.
Why does the connector say it could not register with the sign-in service?
OAuth is off. WP MCP ships OAuth 2.1 switched off, so its discovery addresses return 404 and the connector cannot register. Turn it on in wp-config.php or with the wpmcp_oauth_enabled filter, then try again.
Can a custom connector reach a site on localhost?
Not from claude.ai, because the request comes from Anthropic's side and not from your computer. A site on localhost or a private network needs a public address. For local work use Claude Code or the Claude Desktop config route with an application password.
Is a connector safe to use on a live WordPress site?
It signs in as a real WordPress user and acts with that user's permissions. At approval you can choose read-only access. With WP MCP, each supported write is snapshotted first, so a change or a whole session can be undone.
All WP MCP guides, or see every plugin integration. Topic: Connect an AI client.