How to Connect ChatGPT to WordPress

Connecting ChatGPT to your WordPress site lets you manage content from a ChatGPT conversation: draft and edit posts, update pages, organize media, or review comments. Easy MCP AI runs the MCP server inside WordPress, and ChatGPT connects to it as a custom MCP server over OAuth.

Custom MCP servers work on every ChatGPT plan, including Free, and no longer need Developer Mode. On ChatGPT Business and Enterprise workspaces, an admin decides who can create them.

In this article

• Prerequisites
• Connect ChatGPT to Your Site
• Verify the Connection
• Alternative: Connect with an API Token
• What You Can Do Once Connected
• Control What ChatGPT Can Access
• Security

Prerequisites

• A WordPress site served over HTTPS with Easy MCP AI installed and activated (see the installation guide).
• Pretty permalinks enabled (Settings > Permalinks set to anything other than "Plain").
• A ChatGPT account. Any plan works, including Free.

You'll need your site's MCP endpoint URL, which is always your domain followed by /wp-json/easy-mcp-ai/v1/mcp:

https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp

You can copy it from Easy MCP AI > Dashboard in your WordPress admin, where it is shown in the sidebar as MCP URL. The Add this site step of the connect card shows the same URL.

Connect ChatGPT to Your Site

1. Go to Easy MCP AI > Dashboard, click Connect an AI client, choose ChatGPT, and click Connect to ChatGPT. This should open ChatGPT's Create custom MCP server form. ChatGPT does not accept a pre-filled server, so you enter the details yourself.

   If the form doesn't open

   Open it from ChatGPT: click Plugins in the sidebar (if you don't see it, it may be hidden under the ... menu), then click the Add button in the top right corner and select Create custom MCP server.

2. Enter a name, for example "WordPress". The icon and description are optional.

3. In the Connection field, keep Server URL selected and paste your MCP endpoint URL.

4. Leave Authentication set to OAuth. You don't need to change the Advanced OAuth settings.

5. ChatGPT shows a "Custom MCP servers introduce risk" warning. This appears for every custom MCP server and does not indicate a problem with your site. Tick I understand and want to continue, then click Create as a plugin.

6. The WordPress authorization page opens. Choose an access level (Read-only, Full access or Custom) and click Approve & Continue. You are returned to ChatGPT. No token is needed.

See Managing OAuth Access in Easy MCP AI for access levels, grant management, and what to do after changing your site address.

If ChatGPT opens your site's homepage instead of the WordPress authorization page, check that Authentication was set to OAuth when you created the plugin. If it was not, create the plugin again with OAuth selected. If OAuth was selected, a caching, security, or maintenance/coming-soon layer can be replacing the authorization page: follow Troubleshooting Easy MCP AI Connection Issues to run the diagnostics and the internet test.

If you create the plugin with the wrong details, remove it under Plugins in ChatGPT and add it again.

On a ChatGPT Business or Enterprise workspace, the Create custom MCP server option only appears if your admin allows it. The admin setting is called Create custom MCP servers (it used to be called Developer mode). Ask your workspace admin to turn it on for your role.

Verify the Connection

Back on the Easy MCP AI Dashboard, the top of the page shows Connected: 1 OAuth grant. (If you already had other connections, the number is higher.)

To check that ChatGPT can reach your site, ask it something simple in a new chat, such as:

Which are the five most recent posts on my site, and which of them are still drafts?

The call appears under Recent activity in the Dashboard sidebar.

If nothing reaches your site, click Run diagnostics on the Dashboard, or remove the plugin in ChatGPT, add it again and start a new chat. If you enable an integration later, start a new chat so ChatGPT loads the updated tool list. If tools are still missing, see Enabled Tools Not Showing in Your AI Client.

Alternative: Connect with an API Token

If OAuth does not work in your setup, you can create a custom MCP server whose URL carries an API token instead:

1. Create an API token in Easy MCP AI > Connections (API tokens tab) and copy it.
2. Create the custom MCP server as above, but use your endpoint URL with the token appended:

https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp/YOUR_API_TOKEN

Replace YOUR_API_TOKEN with your actual token (it starts with wpmcp_). Treat this as a fallback: tokens in URLs can end up in server logs and browser history, so prefer OAuth when available. This method does not work on a site that accepts API keys only in the Authorization header; see Keep API Keys Out of URLs.

What You Can Do Once Connected

Easy MCP AI exposes your site's capabilities as MCP tools, organized by area: posts, pages, media, comments, categories and tags, menus, custom post types, blocks, revisions, users, plugins, themes, site settings, and search. Integrations such as WooCommerce and SEO data sources are included when available. What ChatGPT can actually touch is always bounded by the WordPress user's role and your plugin settings.

Some things to try:

Draft a 600-word post about our new spring collection and save it as a draft.

Find every page that still mentions our old phone number and update it.

Show me the comments awaiting moderation and summarize what they're about.

Control What ChatGPT Can Access

The connection acts as the WordPress user who approved it (or the token's assigned user), so WordPress roles apply as usual. On top of that, you can globally disable sensitive tools such as deletions, user management, and site settings. You can also set rate limits, force AI-created posts to stay drafts, and review every action in the audit log. See Creating and Managing API Tokens for all the guardrails.

Security

If you identify a potential security vulnerability in this plugin, please disclose it responsibly. Follow the protocols on the Themeisle Security Page.