01 / Needs OAuth
ChatGPT: a custom MCP server, signed in with OAuth
Signs in with OAuth 2.1. ChatGPT cannot send an application password, so the config snippets on the Connection screen do not apply to it.
- Switch OAuth on. Add the constant below to wp-config.php, or return true from the wpmcp_oauth_enabled filter in a plugin or mu-plugin. Either one is enough.
- Reload WP MCP, Connection in wp-admin. It now reports that OAuth is on and lists the discovery addresses clients use for this site.
- In ChatGPT, add a custom MCP server (ChatGPT also calls this a connector or an app, depending on the version) and enter your endpoint as the server URL. Choose OAuth as the sign-in method. You do not need to enter a client ID or secret: ChatGPT registers itself with the site. OpenAI's documentation has the current menu path.
- ChatGPT opens your site in a browser window. Sign in to WordPress as the user the agent should act as and approve the request. You choose full access or read-only at this step.
- Back in ChatGPT, start a chat with the WP MCP server enabled and ask it to list your post types.
switch OAuth on
// wp-config.php, above "That's all, stop editing!"
define('WPMCP_OAUTH_ENABLED', true);
// or, from a plugin or mu-plugin
add_filter('wpmcp_oauth_enabled', '__return_true');the server URL to enter in ChatGPT
https://your-site.com/wp-json/mcp/wpmcp-serverWith OAuth off, the site's sign-in discovery addresses return 404 and ChatGPT cannot register or sign in. That is the default state, not a fault. Read-only is a sensible first choice: the token can list and read, and is refused anything that changes the site. You can raise or lower a connection's access later on the Connection screen without reconnecting.