If you have looked into AI tools for your store lately, you have probably met the letters MCP. They appear in the setup steps of AI apps and in plugin descriptions, usually with little explanation. This article explains what MCP is, why it matters for a WordPress or WooCommerce site, and what a plugin has to add before it is safe to use on a shop that takes real orders.
What MCP is
MCP stands for Model Context Protocol. It is an open standard that Anthropic introduced in 2024. It describes a common way for an AI app to find and use tools that live somewhere else: on your computer, in a business system or on a website.
Think of it as an agreed plug shape. Without a shared standard, every AI app needs its own custom connection to every service. With one, a service describes its tools once and any app that speaks the standard can use them. Many AI apps and developer tools now support MCP, which is why a single WordPress plugin can work with several of them.
Two roles matter. The client is the AI app you talk to, such as Claude, ChatGPT, Claude Code or Cursor. The server is whatever offers the tools. Here the server is your website, and the plugin is what turns your site into one. When the app connects, it asks the server which tools it offers, then decides which of them to use for your request.
Why an AI app can’t reach into your site on its own
On its own, an AI app knows what it learned in training and what you paste into the chat. It cannot log in to your site, list your plugins, read your error log or look up an order. Nothing connects the chat window to your server.
WordPress has doors, of course: the admin login, a REST API, file access through your host. They were built for people and developers, and in practice they are all or nothing. Handing an AI app an administrator password gives it everything and leaves you no clear record of what it did.
The usual workaround is copy and paste. You describe the problem, the AI suggests something, you try it and paste the result back. It works, but you stay the go-between for every step, and the AI never sees the real state of the site.
Other ways to connect an AI app to WordPress
There are three common routes, and they suit different people.
The REST API with an application password. WordPress lets you create a password for an app, and the app then acts as your user, with all of that user’s rights. It is all or nothing. There is no log of what the app did, and no rollback beyond post revisions.
The official WordPress MCP Adapter. It is free and aimed at developers. It offers the abilities that plugins register through the WordPress Abilities API as MCP tools. Which tools exist, and how access to them is secured, depends on the plugins you install and the code you write. More about the adapter.
A plugin that ships the tools. A plugin such as PowerWP AI brings ready-made tools, permissions for each AI app and a record of changes you can roll back, so you can start without writing code. The comparison page sets the options side by side.
What a plugin like PowerWP adds
MCP defines how an AI app and a tool talk to each other. It does not decide which tools exist, who may use them or what happens when something goes wrong. That is the plugin’s job. PowerWP AI makes your site an MCP server, an address your AI app connects to over HTTPS, with a key or by signing in, and adds four things.
- Tools. There are 85, each with a plain job: read the site overview, query products, check a page, read the error log, edit a post, change one widget on an Elementor page, create a backup. Your AI app sees the list and picks the ones your request needs. A connection sees only the tools its permissions allow.
- Permissions. Each AI app gets its own connection with one of four levels: Read-only, Content manager, Developer or Full. A connection can expire by itself and can be limited to your IP addresses. One switch turns all AI access off.
- A record of changes. When something changes, PowerWP saves how it was and logs which connection did it. Changes are recorded, so you can roll them back. A few actions can’t be rolled back, such as clearing a cache, and the log marks them.
- Know-how. Site memory holds your rules and facts, such as “ask before changing prices”, and reaches every app you connect. Your AI app can propose entries; you approve them. Ready-made recipes give it a starting point for common jobs, such as a site check-up or a safe plugin update.
Risky changes get extra care. After a plugin or theme is updated, for example, PowerWP loads your site again and reverts the change if the site broke. If a fatal error takes the site down anyway, rescue mode lets your AI app work without your other plugins and theme, so it can read the error and switch off the cause.
What it looks like in practice
You type a question into your AI app, as you would to a colleague:
Which plugins need updates, and is any of them risky?
Example, on a demo kitchenware store. The AI app sees a tool called updates_check in its list and calls it. It may also call plugins_list to see what each plugin does. Then it answers in plain language: which updates are waiting, and which of those plugins sit close to checkout or payments. Nothing on the site changed, because those tools only read.
You see a question and an answer. Behind the answer are the tool call, the connection’s permissions and an entry in the activity log. If you ask for a change instead, the same chain applies, with a snapshot taken first. The How it works page walks through the three steps from installing the plugin to your first question.
What it does not do
A few limits are worth knowing before you start.
- It is not an AI. PowerWP AI is the plugin. You bring your own AI app and its plan. Whatever the app reads from your site goes to your AI provider under that provider’s terms. A model running on your own computer, for example through LM Studio, keeps it local.
- It does not send your content to us. Once a day, when the plugin is activated, updated, deactivated or deleted, and when you activate or deactivate a license, your site sends technical details such as software versions to our update and license service, plus your license key once you have activated one. Never content, customers, orders or AI activity.
- It has no tool that runs PHP, WP-CLI or shell commands. Those were removed from the plugin. An app with file permissions can still edit code files, and each edit is checked and recorded.
- It does not make the AI right. AI apps misread requests and make mistakes, like people do. That is why the sensible way in is a Read-only connection, a plan before any change, and a record you can check afterwards.
Which AI apps can connect
Claude (on the web, in the desktop app and on your phone) and ChatGPT (on the web and in its apps) connect by signing in. You add your site’s address as a connector, sign in to WordPress, choose what the app may do and click Allow. There is no key to copy. Signing in needs a site the app can reach from the internet.
Claude Code, Codex, Cursor, VS Code, Devin Desktop, Gemini CLI, Kimi Code and LM Studio connect with one message or one click, using a connection key. Any other app that supports remote MCP servers can connect with your site’s address and a key. The connect guides have the steps for each app.
Where to start
Start with the Free plan: one site, one read-only AI connection, no end date. Install the plugin, activate your plan under PowerWP AI › License, create a Read-only connection (about two minutes) and ask for an overview of your site. The quickstart has the steps for each app. Once you trust what you see, widen the permissions one level at a time.
Questions
Is MCP safe?
MCP is a protocol, not a safety layer. What an AI app may do on your site is decided by the plugin that offers the tools: PowerWP AI checks each connection’s permissions and records the changes.
Do I need to code?
No. You ask in plain words, and your AI app picks the tools.
Do I need a paid AI plan?
PowerWP has no AI of its own. You bring your AI app and its plan. A local model, for example in LM Studio, also works.