ChatGPT

ChatGPT can’t connect to your store’s MCP server today. This isn’t a Raqvio Agent Guardrails limitation; it comes from how ChatGPT and WordPress handle sign-in.

Why

ChatGPT can add custom MCP servers in developer mode (on Plus, Pro, Business, Enterprise and Education plans, on the web), but a server must either require no authentication or use OAuth 2.1. OpenAI states that ChatGPT can’t present custom API keys, and it doesn’t send custom headers or HTTP Basic credentials.

The WordPress MCP servers authenticate exactly that way:

• WooCommerce MCP needs the X-MCP-API-Key header.
• The MCP Adapter uses application passwords (HTTP Basic).

Neither offers an OAuth 2.1 sign-in, so ChatGPT has no way to authenticate.

Don’t remove authentication to make it work

An MCP endpoint without authentication would let anyone on the internet call your store’s abilities. Raqvio Agent Guardrails would treat those calls as unknown agents, but a public, unauthenticated endpoint is never a safe setup.

What it would take

ChatGPT could connect through an MCP server or gateway that signs users in with OAuth 2.1 (with PKCE and client registration, as OpenAI’s developer documentation describes), is reachable over public HTTPS, and then calls your site with a credential bound to a Raqvio Agent Guardrails agent. We haven’t tested such a setup, so we don’t publish a configuration for it.

Use one of these instead

Claude Desktop, Claude Code and Cursor can all send your site’s API key or application password, and connect directly.