We’re getting this question a lot. A client reads that WordPress (or WooCommerce) now supports “MCP”, and asks whether they can plug ChatGPT or Claude into their site to get easier answers about their content, enquiries or sales.

It’s a good (and exciting!) question, so here’s the answer we give our own clients.

Short answer: yes, you can connect an AI assistant to your WordPress site, and in most cases it should only be allowed to read, not change. But it won’t do everything you might expect, and there’s one bit most people miss entirely – customer data!

As with anything; just because you CAN doesn’t mean you SHOULD, and with a live website, it will nearly always have personal information stored in contact forms, registered users or in Woocommerce, extensive customer data and buying habits.

What MCP actually is

MCP stands for Model Context Protocol. It’s a standard way for an AI assistant to talk to another system, such as your website, using a set of defined tools.

Without it, you’d copy and paste data into ChatGPT or Claude yourself. With it, you can ask “what were my most popular pages last month?” or “which orders are still on hold?” and the assistant fetches the answer directly from your site.

Think of it as giving the AI a controlled set of keys. Which keys it gets, and whether they only open doors or can also move the furniture, is entirely up to how it’s set up.

How it works on WordPress

WordPress doesn’t have an MCP server built in. What it has, since version 6.9, is the Abilities API: a standard way for WordPress, plugins and themes to declare what they can do. A separate layer then turns those abilities into tools an AI can use.

In practice there are three ways to connect a self-hosted WordPress site:

Route What it is Things to know
The official MCP Adapter A plugin from the WordPress project that exposes your site’s abilities over MCP Needs WordPress 6.9+. Still pre-1.0 and not in the plugin directory, so no one-click updates
A self-hosted community server A small program run on your computer or a server that talks to your site’s REST API You own the setup, the credentials and the updates – very important!
Hosted MCP from your web host Your host runs it for you Easiest to switch on, but you get whatever your host decided to build

Two things worth knowing. First, the older Automattic WordPress MCP plugin was archived in January 2026, so any tutorial telling you to install it is out of date. Second, “our host supports MCP” can mean very different things. Pressable’s version, for example, is read-only, and WP Engine’s is limited to published content.

Read or write: start with read-only

For most business owners, read-only is the right place to start, and often the right place to stay.

A read-only connection lets the AI answer questions: what’s in draft, which pages have no meta description, how many enquiries came in this week. It can’t publish, delete, update plugins or change settings, however the question is worded.

Write access is where things get interesting and where things go spectacularly wrong. An AI that can edit your live site can also make a confident mistake on your live site.

You know that little note at the bottom of EVERY single AI agent? Yeah… and of course, it can get things wrong about your data too…

If you do want it to make changes, that should happen on a staging copy first, with a dedicated user account that has only the permissions it needs.

Never your own admin login.

One technical detail worth knowing: if the official adapter is set up without proper permission checks, it defaults to letting any logged-in user reach it, including a basic subscriber account. That’s a setup problem, not an MCP problem, but it’s exactly the sort of thing a non-technical owner wouldn’t know to check.

Customers on our support plans can void their protection if connecting directly, so it’s important to think about what, how and why you want to connect.

WooCommerce: what it adds, and what it won’t do

WooCommerce has its own MCP support. It first appeared as a beta in version 10.3, and version 10.9 (June 2026) added a proper set of product and order abilities, with the lookup ones marked as read-only. You switch it on under WooCommerce > Settings > Advanced > Features, and the AI connects using a REST API key. Create that key with Read permission only and the AI can look but not touch.

That gets you questions like:

  • What were last month’s sales compared with the month before?
  • Which products are running low on stock?
  • Which orders are still on hold?
  • What has a particular customer bought this year?

What it won’t do is tell you anything unprompted. MCP only works when you ask it something. So if what you really want is “let me know when one of my trade customers places an order”, MCP isn’t the tool. That needs a WooCommerce webhook or a small automation that watches for new orders and sends you an email or a message. It’s a simple build, but it’s a different thing, and it’s the part people usually want most.

Woocommerce already has a lot of this info in its analytics, so the question is more whether it’s connecting the MCP for ease (or to further connect to other MCPs) – but in any case, there are some important warnings:

The bit nobody mentions: your customers’ data

Read-only protects your website. It doesn’t protect your customers’ data.

Every time you ask the AI about orders, enquiries or form submissions, names, email addresses, delivery addresses and purchase history get sent to the AI provider to answer your question.

Under UK GDPR, you’re responsible for where that data goes.

Before connecting anything that can see customer information, it’s worth checking:

  • Which AI provider you’re using, and whether you’re on a business plan with proper data terms
  • Whether that provider uses your conversations to train its models, and how to turn that off
  • Whether your privacy notice covers sharing customer data with an AI service
  • Who in your business has access to the AI account, and therefore to that data
  • Whether you have solid 2FA or MFA protocols in your business, and proper security tools running on your computer

None of this is a reason not to do it. It’s a reason to do it properly.

Keys, updates and who looks after it

Every MCP connection runs on a credential: an application password, an API key or a connection link with a token in it. Whoever holds it has whatever access it grants. We regularly see keys like these pasted into emails, shared documents and chat messages, then forgotten about.

A few simple rules:

  • Use a dedicated user or key for the AI, not your own login
  • Give it the least access that does the job
  • Keep a note of where it’s used, and revoke it when it’s no longer needed
  • Change it if someone leaves or a device goes missing

Then there’s upkeep. The official adapter is still pre-1.0 and its workings have changed between versions. WooCommerce’s MCP support is still developing too. Something that works today may need attention after an update, so it’s worth deciding up front who’s responsible for keeping an eye on it.

A safer option: let the AI see less

There’s a way to get most of the benefit with far less risk: don’t give the AI your customers’ personal details in the first place.

Instead of connecting the AI straight to your store, we can build a small, read-only connector that sits in between. It pulls the data from WooCommerce, strips out or replaces the personal bits, and only then passes it to the AI. Names and email addresses become a customer reference like “C-1042”, and you keep the key that links the two on your side.

That means the AI can still answer “what has C-1042 bought this year?” or “which products sold best in the East Midlands last quarter?”, without ever seeing who C-1042 actually is.

A few things make this work properly:

  • It’s more than names. Phone numbers, full postcodes and free-text fields such as order notes can all give someone away, so they’re removed or reduced to something general, like a region
  • The connector decides what’s visible. The AI only gets the handful of questions you need, not the whole store
  • Alerts stay separate. Order notifications run as a simple automation with no AI involved, so they can still use real names where that’s useful

One honest caveat: under UK GDPR, data that can be linked back to a person with a key is “pseudonymised”, and it’s still classed as personal data. So this reduces the risk rather than removing it. Genuinely anonymous information, such as totals by product, region or week, is the lowest-risk option of all.

How we approach it at DeType

When a client asks us about connecting AI to their site, we don’t start with the technology. We start with one question: what do you actually want to know, and when?

Usually the answer is a handful of things:

  1. A few regular questions they’d like answered quickly, such as sales, stock or enquiries
  2. One or two moments they want to be told about straight away, such as a key customer ordering or a large order coming in
  3. A simple way to see how things are trending over time

Once we know that, the right setup tends to be obvious. Sometimes it’s a read-only MCP connection that we configure, secure and look after. Sometimes it’s a few automated alerts. Sometimes a simple dashboard does the job better than a chatbot ever would. Often it’s a mix.

What we try to avoid is handing over an API key and a set of instructions, then leaving someone to work out the rest on their live site.

The short version

  • Yes, you can connect AI to your WordPress or WooCommerce site
  • Start read-only, and keep it that way unless there’s a good reason not to
  • It answers questions; it doesn’t send alerts, so plan for those separately
  • Think about your customers’ data before you think about the tech
  • Where you can, give the AI pseudonymised or summary data rather than customer details
  • Treat the keys like the keys to your shop
  • If you’re thinking about doing this on your own site, get in touch. Tell us what you’d like to be able to see, and we’ll suggest the simplest, safest way to get there.

Sources