Do you need an MCP server for your WooCommerce store? Free & Pro

Not to serve agents that follow the Personal Agent Protocol. Those use the agent API every store running Agent Adapt publishes. An MCP server reaches a different group: people whose AI assistant can connect to tools over the Model Context Protocol but does not speak the Personal Agent Protocol itself. If your customers use such an assistant and you want them to shop with you through it, an MCP server is how. Agent Adapt Pro runs one. This guide explains the difference so you can decide.

What MCP is

The Model Context Protocol is an open standard for giving an AI application tools. A server publishes a list of tools with names, descriptions and parameters; the assistant (the client) reads the list and calls tools when the conversation needs them. It is general purpose: the same mechanism connects an assistant to a calendar, a database or a store. Its current specification revision is 2026-07-28.

MCP says nothing about shopping. What a store’s MCP server offers is up to the store.

What a store’s MCP server does with Agent Adapt Pro

Your store runs one at https://your-store.com/agent-adapt/mcp, listed in your poppy.json. Its tools are the same actions as the agent API, under the same permissions and the same merchant policy: catalog_search, catalog_product, store_policies, the cart_* tools, cart_handoff, orders_list, orders_get, orders_reorder, orders_cancel_unpaid, account_addresses, and Pro’s orders_cancel_paid, returns_request and account_addresses_update. An action you switch off in policy disappears from the list.

A customer adds the address to their assistant as a custom connector. The assistant sends them to your store’s sign-in and approval page, the same one every agent uses. Once they allow it, the assistant can shop and manage their account for them. The order still ends with a checkout link and the customer paying on your checkout. See The MCP server.

How it differs from the agent API

	Agent API (free)	MCP server (Pro)
Who uses it	Agents that implement the Personal Agent Protocol	Any MCP-capable assistant, plus protocol agents that prefer MCP
How the agent is identified	Published metadata and signed requests, with key-bound tokens	A protocol agent: the same. A plain MCP client: a Client ID Metadata Document, PKCE, and a token bound to the MCP server’s address only
How the customer signs in	The store’s sign-in and consent page	The same page
Actions	The capability registry	The same registry, as tools
Approvals for refunds, returns, address changes	Operations, for agents that support them	The same, but most MCP clients cannot yet show operations, so those actions are refused with an explanation
Policy, blocking, Connected agents, insights	Yes	Yes, the same screens

The token difference matters for security. A protocol agent’s tokens are bound to a key it holds, so a copied token is useless. MCP clients cannot sign per-request proofs, so the protocol allows a plain Bearer token for them, with two conditions Agent Adapt enforces: the token works only at the MCP server, nowhere else on your store, and it is issued only for that purpose. The agent API refuses Bearer tokens outright.

Who it reaches

Assistants that let a person add their own MCP connectors. In October 2026 that includes several desktop and web assistants from the large AI companies, and many developer tools. Whether your customers use one is the question. A store selling to developers and technical buyers probably has customers who do. A store selling garden furniture probably has fewer, for now.

When to run one

• Yes, if customers have asked whether they can connect your store to their assistant, or you sell to people likely to try.
• Yes, if you want one address you can give a customer ("add this to your assistant") rather than waiting for their assistant to implement the protocol.
• Not yet, if your customers’ assistants do not support custom connectors, or you would rather keep the smaller surface of the free plugin until agents arrive.
• Not instead of the agent API. The MCP server is an addition. Protocol agents will mostly use the API.

What you give up

Nothing from the free plugin. The MCP server adds a second door with the same locks. The practical limitation is on the client side: most MCP assistants cannot yet display an operation’s terms for the customer to approve, so through them paid cancellations, returns and address changes are refused with a message explaining why. Unpaid orders can still be cancelled, carts built, orders read.

Common questions

Can a customer connect ChatGPT or Claude to my store?

If their assistant lets them add a custom MCP connector, yes, with Pro, by entering your store’s MCP address and signing in on your store. Assistant features change often; check the assistant’s own documentation for custom connectors.

Does the MCP server need any configuration?

No. It is on when Pro is active, and it is listed in your discovery document. The same hosting requirements apply as for the agent API: HTTPS, the Authorization header reaching PHP, and /agent-adapt/ not cached or blocked.

Is MCP part of the Personal Agent Protocol?

MCP is one of the two API types the protocol lets a business offer, alongside OpenAPI. The protocol defines how an agent gets a token for an MCP server; MCP itself is maintained separately.

Does the free plugin have an MCP server?

No. The free plugin offers the OpenAPI-described agent API, which is what protocol agents use. The MCP server is in Pro.