How to Connect WordPress to ChatGPT or Claude with MCP

The short answer

You can connect a WordPress website to ChatGPT, Claude and other compatible AI clients by installing a WordPress MCP server plugin, connecting the client to the server URL and approving only the permissions it needs.

In the video above, I use Easy MCP AI. The plugin turns the WordPress installation into a Model Context Protocol server, so an approved AI assistant can work with the site through defined tools instead of receiving an administrator password or relying on brittle browser automation.

This is useful, but it is not a reason to hand an AI unrestricted control of a production website. Start with read-only access, use a dedicated WordPress user and keep publishing behind human review until you trust the workflow.

What MCP changes for WordPress

A normal chatbot can suggest copy or code, but it cannot see the current state of your website unless you paste that information into the conversation. MCP gives a compatible AI client a structured way to ask WordPress for specific information and, where you allow it, make specific changes.

That means you can use natural-language requests for jobs such as:

• finding an existing post or page;
• preparing or updating a draft;
• checking media, categories or other site data;
• editing supported SEO fields;
• reviewing WooCommerce or analytics information when the relevant integrations are configured; and
• recording a repeatable website-maintenance workflow.

The important distinction is that the plugin exposes tools. The AI client can use only the tools and WordPress capabilities granted to its connection.

How to connect ChatGPT or Claude to WordPress

The exact screens change as WordPress, ChatGPT, Claude and the plugin evolve, but the underlying setup is straightforward.

1. Install the plugin

Install Easy MCP AI from the official WordPress plugin directory and activate it on the site you want to connect. Use a staging site first if the website is commercially important.

2. Create the right WordPress user

Do not automatically connect the AI as a full administrator. Create or choose a user whose role matches the work you want performed. A content workflow may need permission to edit posts, but it probably does not need permission to install plugins, alter users or change site-wide settings.

3. Add the MCP connection

Open the plugin dashboard and use the connection instructions for your chosen client. Claude and ChatGPT can connect through the MCP server URL and an approval flow. Other clients may use a generated configuration or API token.

Treat the server URL and any token like a credential. Do not paste them into public documentation, screenshots or shared prompts.

4. Approve the minimum tools

Enable only the capabilities required for the task. A sensible first connection is read-only. Confirm that the assistant can find a known page and report its title before allowing it to write anything.

For writing, start with draft creation. Review the output in WordPress, confirm the links and metadata, and publish it yourself. The current plugin listing describes a Force Draft on Create option for its own creation tools, which is a useful additional guardrail.

5. Test and audit

Run a harmless test, then check the plugin's audit and change-history screens. You should be able to identify which connection called which tool and what changed. Revoke the connection immediately if its behaviour is broader than expected.

My recommended safety setup

For a production website, I would use these defaults:

• HTTPS with no exceptions;
• a dedicated WordPress user with the smallest practical role;
• read-only tools first;
• draft-only content creation during testing;
• explicit approval for high-impact actions;
• logging and change history enabled;
• regular WordPress backups; and
• separate connections for separate jobs rather than one all-powerful token.

The official listing currently describes OAuth 2.1, WordPress capability checks, per-connection permissions, rate limits, audit logging and change history. Those are meaningful controls, but configuration still matters. A secure feature cannot protect a connection that has been given unnecessary administrator permissions.

ChatGPT, Claude or another client?

The WordPress side of the connection is broadly the same: the plugin exposes an MCP server and the client calls its approved tools. Your choice of client comes down to the model you prefer, the MCP features available in your account and how you want the workflow to run.

ChatGPT or Claude can be convenient for conversational editing. Cursor, Codex or Claude Code may suit repository and development work. The best client is the one that supports the connection you need and lets you keep permissions narrow.

Is this better than a conventional WordPress automation?

It depends on the job. Use a conventional webhook or API workflow when the steps are fixed, predictable and should run identically every time. Use an MCP-connected assistant when the task benefits from inspecting context, choosing among approved tools and explaining its work.

For deterministic workflows, my beginner's guide to Make.com webhooks explains the event-driven alternative. If your goal is to connect a Custom GPT to a small, approved data source, see my ChatGPT and Google Sheets guide.

The practical takeaway

Connecting WordPress to an AI assistant is now much easier than building a bespoke integration. The opportunity is not simply “let AI run the website”. It is to give a capable assistant a small set of auditable tools, prove the workflow on low-risk tasks and expand access only when the results justify it.

Watch the video for the quick overview, then use the current WordPress.org listing for the latest installation and compatibility details. The video was recorded in September 2026; plugin features and client interfaces can change after publication.