How to connect your WordPress site to ChatGPT
Want ChatGPT to actually manage your WordPress site — not just write drafts you paste in? Install one free plugin on your self-hosted site, click Open ChatGPT, and approve. No code, no terminal, no API key to copy — a few minutes. New to MCP? Start with the WordPress MCP server guide.
What can ChatGPT do on your WordPress site once it's connected?
Once connected, ChatGPT acts on your live WordPress site with real tools — it does the work itself instead of handing back text you paste in. Ask in plain English and it can draft and schedule posts, put a WooCommerce collection on sale, run a Wordfence scan, or back up the site before an update. Cowboy MCP turns your site into an MCP server ChatGPT can act on directly.
Does this work on self-hosted WordPress, or do I need WordPress.com?
A self-hosted WordPress site runs on hosting you control, where you can install plugins — and that is exactly where Cowboy MCP lives: it is a plugin inside your own site, so the site itself becomes the MCP server. WordPress.com's built-in MCP covers WordPress.com and Jetpack-connected sites through Automattic's platform; hosting-level MCP servers such as Hostinger's are tied to a hosting account, not installed per site. Cowboy MCP needs only WordPress 6.2+ and PHP 8.0+.
ChatGPT connects from OpenAI's servers, so the site needs a public HTTPS address; for a local site, the Codex CLI runs on your computer and signs in through your browser there — no public address needed.
How do you connect ChatGPT to a self-hosted WordPress site in three steps?
Connecting takes three steps and no code. Install the free Cowboy MCP plugin, open Settings → Cowboy MCP, and follow the built-in guided setup — it walks you through adding your site to ChatGPT as a custom connector (OpenAI now groups these under Plugins) with one-click sign-in. There's no key to copy or keep safe, and nothing is allowed until you click Approve on your own site.
- 1
Install the free plugin
In WordPress, go to Plugins → Add New, search for Cowboy MCP, and click Install then Activate.
- 2
Click Open ChatGPT
On the Connections tab pick ChatGPT and click Open ChatGPT. One click copies your connection link — your site's /wp-json/cowboy-mcp/v1/endpoint URL — and opens ChatGPT in a new tab.
- 3
Add it in ChatGPT and approve access
In ChatGPT on the web, open Settings → Security and login and turn on Developer mode once. Then go to Plugins, click +, choose Add custom MCP server, paste the link as the MCP server URL, set Authentication to OAuth, and create it. ChatGPT opens a sign-in page on your site — approve it as an administrator, and the Connections tab confirms the moment ChatGPT connects. Then pick Developer mode from the + menu in a chat and select your site.
OpenAI keeps renaming this area (Connectors, Apps, now Plugins), so ChatGPT's labels may differ from the guided setup. If ChatGPT tried to connect while new connections were off, the Connections tab says so and puts the switch right there. Prefer the terminal? Pick Codex and run the one pre-filled codex mcp add command — Codex opens your browser to the same sign-in page, no key to copy. See the Codex guide.
Is it safe to let ChatGPT manage your live WordPress site?
You're handing ChatGPT the keys, so Cowboy MCP keeps guardrails on: safe mode is on by default (destructive actions ask first), any change can be previewed as a dry run, and every action is written to an audit log. It all runs on your own server. More on security →
Questions, answered.
Does this work on self-hosted WordPress, or only on ChatGPT?
Any self-hosted WordPress site (version 6.2 or newer, on PHP 8.0+) where you can install plugins. It runs on your own server and isn't tied to WordPress.com or any particular host.
Do I need to know how to code?
No. Install the free plugin and follow the guided setup in Settings → Cowboy MCP — no code, no terminal, and no config files for the standard path.
Does my content get sent to OpenAI?
Only what ChatGPT needs to read to do the task you asked. Cowboy MCP adds no cloud, proxy, or tracking of its own — your site talks directly to the ChatGPT app you chose, and everything runs on your own server.
ChatGPT or the Codex app — which should I use?
Either. ChatGPT connects with one-click sign-in and no terminal; the Codex app and Codex CLI are the developer options. Pick whichever you already use — the guided setup covers each.
Which ChatGPT plan do I need?
A ChatGPT Plus, Pro, Business, Enterprise or Edu plan on the web, with Developer mode turned on under Settings → Security and login — the setting that lets you add your own MCP server as an app under Plugins. On Business and Enterprise workspaces an admin has to allow Developer mode first. Your site must also be on public HTTPS, because ChatGPT connects from OpenAI's servers.
ChatGPT says the app's identity document on chatgpt.com is invalid — what now?
Update Cowboy MCP to 1.7.3 or newer, then connect again. ChatGPT changed how it identifies itself when it signs in, and 1.7.2 rejected the new identity with that message. 1.7.3 accepts it, and nothing else needs to change on your site.
ChatGPT says the server doesn't support RFC 7591 Dynamic Client Registration — what's wrong?
Almost always it means your site said no right now, not that it lacks the feature. ChatGPT registers itself with your site when you click Create, and Cowboy MCP accepts that registration only while New connections is on, a switch that turns itself off 30 minutes after you enable it. ChatGPT reports any refusal from that endpoint as “doesn't support RFC 7591”, which is misleading. Fix: on the Connections tab click Open ChatGPT (or Enable for 30 minutes), then click Create in ChatGPT straight away and approve the sign-in on your site. Once connected, ChatGPT keeps working after the window closes. The Connection Doctor passes in this case because the plugin is healthy; it is the window that was shut.
My log shows auth_missing_header and the Doctor's authenticated handshake fails — what now?
A few auth_missing_header entries are normal: ChatGPT's first contact before it has a token. A steady stream of them after you approved the sign-in means your server strips the Authorization header before WordPress sees it, so every request arrives without the token ChatGPT sent. It happens on CGI/FastCGI hosts (check Tools → Site Health → Info → Server → Server API) and on some LiteSpeed setups. Fix: add the standard rewrite rule that passes the header through at the top of your .htaccess — RewriteCond %{HTTP:Authorization} . followed by RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] — or CGIPassAuth On, then run the Connection Doctor again; if the host does not allow it, ask support to pass the Authorization header to PHP. Paste the Doctor report into the support forum (opens in new tab) if it still fails.
I get a 401 or 403 when connecting — what's wrong?
Run the Connection Doctor on the Connections tab. A 401 with a Basic Auth prompt means server-level password protection answers before WordPress — exclude /wp-json/cowboy-mcp/ and /.well-known/ from it; MCP clients can't send two Authorization headers. A 403 or 503 from Cloudflare is a bot challenge; a 403 or 406 mentioning ModSecurity is a firewall blocking JSON POSTs. Still stuck? Paste the report into the support forum (opens in new tab).
The connector says no tools are available — why?
A short list is normal: Cowboy MCP exposes two gateway tools, cowboy_discover and cowboy_run, instead of loading every schema into ChatGPT's context — ask it to “discover tools for WooCommerce”. If even those two are missing, the connection's scope is probably empty: check it under Connected apps on the Connections tab. Still nothing? Ask in the support forum (opens in new tab).
My host blocks the connection (Cloudflare, SiteGround, LiteSpeed, Basic Auth) — what do I change?
The fix is always an exclusion for the MCP paths. Cloudflare: a WAF skip rule (or disable Bot Fight Mode) for /wp-json/cowboy-mcp/* and /.well-known/oauth-*. SiteGround and other ModSecurity-style firewalls: ask support to allowlist POST /wp-json/cowboy-mcp/v1/endpoint. LiteSpeed or any page cache: exclude /wp-json/cowboy-mcp/ and the root /.well-known/ paths from caching. Basic Auth: exclude /wp-json/cowboy-mcp/ and /.well-known/. If the fix doesn't take, paste the Connection Doctor report into the support forum (opens in new tab).
Ready to connect ChatGPT to your WordPress site?
Install the free plugin, click Open ChatGPT, approve the sign-in, and ChatGPT is working your site minutes later. The same site also works with Claude, Perplexity, Grok and, from the terminal, Codex.