Learn / Protocols and standards
Should you run an MCP server for your store?
An MCP server exposes your store as a set of tools an agent can call, which is genuinely useful in contexts where an agent already has a relationship with you and largely redundant for anonymous shopping traffic, where a public feed and readable pages do the same job with no maintenance and no attack surface.
For most stores the answer is not yet, and the reason is worth understanding, because MCP is genuinely useful for a shape of problem that most retail traffic does not have.
What it is for
An MCP server exposes capabilities an agent can call: check this stock level now, price this basket for this account, tell me the status of this order. That is interaction, and it presumes a relationship.
Anonymous shopping traffic has no relationship. An agent answering a shopper’s question wants published data it can read without credentials, documentation or setup.
What a feed does instead
A public feed and readable product pages answer the same questions for that audience, with no authentication, no maintenance burden and no new attack surface. They are also what every channel already expects.
See how to publish a product feed for AI agents.
When it earns its place
- B2B with account specific pricing, where the answer genuinely depends on who is asking. See agentic commerce for B2B stores.
- Replenishment ordering, where the supplier decision is made and what remains is execution.
- A customer base already running agents against you, which is a fact you can observe rather than assume.
- Volatile stock, where a published snapshot is wrong often enough to cost you.
The cost side
It is a new authenticated surface with real operations behind it: authentication, authorisation, rate limiting, monitoring and a maintenance commitment. That is an ordinary API cost and it should be weighed against a benefit that, for a typical store, is currently small.
The order
Readable product data, then a feed, then measure who is actually reaching you. If the answer points at a known counterparty rather than anonymous shopping traffic, revisit this. See do you need to adopt a commerce protocol at all.
Questions
What would an MCP server give me that a feed does not?
Interaction rather than publication: live stock checks, account specific pricing, order status. Those matter where a relationship exists. Anonymous shopping traffic needs published data, not a callable interface.
Is it a security concern?
It is a new authenticated surface with real operations behind it, which deserves the same scrutiny as any API you expose. That cost is worth weighing against a benefit that may not apply to your traffic.
When does it become worth it?
B2B with account specific pricing, repeat and replenishment ordering, or a customer base already operating agents against you. All three involve a known counterparty.