Not directly, today. ChatGPT adds a remote MCP server from a URL and authenticates with OAuth or not at all. WP Visibility’s endpoint authenticates with a WordPress Application Password sent as a header, and ChatGPT’s form has nowhere to put one. This page says what that means so you do not spend an afternoon on it.
What ChatGPT’s connector needs
In ChatGPT, you turn on Developer mode under Settings, Security and login, then create a developer-mode app for your remote MCP server. The server needs a public HTTPS endpoint, or a Secure MCP Tunnel from inside your network. The documented authentication is OAuth, no authentication, or a mix of the two set per tool. None of those takes a username and password or a custom header, and OpenAI’s authentication guide says ChatGPT cannot present custom API keys. Checked September 27, 2026 against OpenAI’s developer mode guide, authentication guide, Secure MCP Tunnel guide and Connect from ChatGPT guide.
Why the plugin does not fit that form
The endpoint at /wp-json/wp-visibility/mcp uses ordinary WordPress REST authentication, which for a remote client means an Application Password. That is deliberate: the credential is a WordPress user with a role you chose, revocable from the user’s Edit User screen (WordPress’s Application Passwords guide, checked September 27, 2026), and each ability it runs successfully is recorded in the activity log under that user and the Application Password’s name. The plugin does not act as an OAuth provider.
The two workarounds, and why we do not recommend them
A public relay with no authentication. You could host a small service that accepts ChatGPT’s requests and forwards them to your site with the Application Password added. Registering it as a no-authentication connector means anyone who learns the relay’s URL has the assistant’s authority on your site. Do not do this.
A relay that speaks OAuth. The same relay, fronted by an OAuth server you run. This is a real piece of infrastructure to build and keep secure, for one client. If you run it, the plugin’s side is unchanged: the relay is just another client sending Basic authentication.
OpenAI’s Secure MCP Tunnel changes where a relay can live, not what it is: its tunnel-client runs inside your network and forwards to an MCP server over stdio or HTTP, so the relay need not be public. It needs OpenAI Platform tunnel permissions, and you still run and secure a relay that holds your Application Password.
What to use instead
Claude Desktop and Claude Code connect today, in one config block or one command. Other clients that accept a URL plus a custom header, or that can run a local command, connect through the general doc.
If ChatGPT adds header or password authentication for connectors, or if the plugin gains an OAuth provider, this page will change. Until then, treat “ChatGPT connected to WP Visibility” claims elsewhere with care.