Model Context Protocol
MCP servers for ecommerce.
MCP servers connect AI assistants and agents to ecommerce platforms, payments, analytics and marketing tools. Compare what each one connects to, how it runs, how it authenticates and who maintains it.
- MCP servers listed
- 97
- integrations
- 33
- published by the platform itself
- 25
- offer a hosted endpoint
- 20
- Repositories and docs last checked
- Sept 2026
Connect AI to your ecommerce stack
MCP servers by the platform or service they connect to. Counts are listings, not usage.
Shopify14 servers1 official
WooCommerce10 servers
WordPress10 servers
Magento / Adobe Commerce5 servers
Stripe5 servers1 official
Odoo4 servers
Amazon Ads3 servers
eBay3 servers
Salesforce Commerce Cloud3 servers1 official
Amazon2 servers
BigCommerce2 servers
Google Ads2 servers
Google Analytics2 servers
Klaviyo2 servers
Meta Ads2 servers
PayPal2 servers1 official
Xero2 servers1 official
What do you want your agent to do?
From the tools each server's documentation lists.
- Manage productsRead or edit products, variants and collections.53
- OrdersLook up and manage orders.46
- CustomersLook up customer records.43
- PaymentsQuery charges, refunds, subscriptions and invoices.31
- AnalyticsQuery sales and marketing data.30
- Product contentProduct copy, images and translations.25
- Store developmentPlatform docs, code and developer tooling.25
- InventoryRead or update stock levels.24
- Shipping and fulfilmentLabels, shipments and tracking.12
- Agentic shoppingSearch, add to cart and check out as a buyer.11
What are you connecting from?
Counts servers whose own documentation gives setup steps for that client. A server without them may still work with any client that supports its transport.
How it connects
The transport from the MCP specification each server uses.
- stdio (local)77The AI client starts the server as a program on your own machine and talks to it over standard input and output.
- HTTP (remote)32The server runs as a separate service and the client sends each message to one HTTP endpoint. Hosted MCP servers use this.
- SSE (deprecated)9The older HTTP with Server-Sent Events transport. Deprecated in the MCP specification since March 2025 in favour of Streamable HTTP.
Active filters
5 MCP servers match your filters
Showing 1 to 5 of 5, ordered by recently updated
How results are ordered
By the date the server's source repository last changed, newest first. Hosted servers without a public repository use the date we last read their documentation. This is a measure of recent activity, not quality.
There are no paid placements in the MCP directory, and no ratings.
Stripe AI (Stripe MCP)
Officialby Stripe
Stripe's official repo offering a hosted MCP server at mcp.stripe.com plus agent plugins and skills for working with Stripe payments and billing.
Stripe
Tasks: Payments · Customers · Store development
- Runs
- Local or hosted · HTTP, stdio
- Auth
- OAuth, API key
- Setup for
- Claude Code, Cursor
- Install
- npm
Stripe ACP
Third-party companyby CodeSpar
MCP server for Stripe and the Agentic Commerce Protocol, with tools for agent checkout sessions, customers, products, invoices, subscriptions and refunds.
Stripe
Tasks: Payments · Manage products · Customers · Agentic shopping
- Runs
- Local · stdio
- Auth
- API key
- Setup for
- Claude Desktop, Claude Code, Cursor, VS Code
- Install
- npm
MnemoPay
Third-party companyby MnemoPay (Jeremiah Omiagbo, J&B Enterprise LLC)
TypeScript SDK and MCP server for AI agent payments, giving clients tools for memory, wallet balance, charges, settlements, refunds and agent reputation scoring.
Stripe
Tasks: Payments · Agentic shopping
- Runs
- Local · stdio
- Auth
- API key
- Setup for
- Claude Code
- Install
- npm
Stripe MCP (agenticledger)
Communityby agenticledger
MCP server exposing Stripe API calls over Streamable HTTP with bearer token passthrough authentication.
Stripe
Tasks: Payments
- Runs
- HTTP
- Auth
- Token
- Setup for
- Not documented
- Install
- Source only
MCP Stripe Server
Communityby Atharva Gupta
MCP server for Stripe that lets an AI client create and update customers, create payment intents, list charges and issue refunds.
Stripe
Tasks: Payments · Customers
- Runs
- Local · stdio
- Auth
- API key
- Setup for
- Claude Desktop
- Install
- npm
From the ecommerceguide dataset
MCP for ecommerce in numbers
Calculated from every listed server, not just this page. Each figure opens the list filtered to it.
- MCP servers listed
- 97
- Published by the connected platform
- 25 26%
- Can run locally
- 83 86%
- Offer a hosted endpoint
- 20 21%
- Ask for an API key
- 68 70%
- Support OAuth sign-in
- 21 22%
Where a server's documentation lists its tools, 63 can create or change data and 24 only read it. The other 10 do not list their tools clearly enough to say.
What to check before connecting an MCP server
An MCP server acts with the access you give it to your store, payments or marketing accounts.
What it can access
Check which tools it exposes and whether any create, change or delete data, issue refunds or send messages. Profiles record read-only or read and write only where the documentation lists the tools.
Where it runs
A local server runs on your machine with the credentials you give it. A hosted server runs on the maintainer's infrastructure, so your requests pass through it.
Hosted serversHow it authenticates
Local servers usually read an API key or access token from a config file. Hosted servers can use OAuth, where you sign in to the platform and approve the access requested.
Servers with OAuthWho maintains it
Official servers come from the platform's own company. A community server is not endorsed by the platform it connects to, even when its name suggests otherwise.
25 official serversWhether your client supports it
Clients differ in which transports they support. Check the transport a server uses against your client's documentation before installing.
How active it is
Each profile shows when the source repository last changed. Archived repositories are not listed here.
Model Context Protocol
What is MCP?
The Model Context Protocol is an open standard for connecting AI applications to outside tools and data. An MCP server exposes a service's data and actions as tools that an AI client such as Claude or Cursor can call. In ecommerce, that can mean an assistant looking up Shopify products, checking a Stripe payment or pulling campaign figures.
Understand MCP and agentic commerce
- Choosing an MCP Ecommerce ServerHow to choose an MCP server for ecommerce. Vetting criteria, storefront vs admin coverage, marketing execution, and backend orchestration.
- MCP vs. API for Ecommerce: Choosing Your Agent StrategyWhen to use the Model Context Protocol versus traditional REST APIs for ecommerce agents. Dynamic tool discovery, deterministic payments, and the hybrid integration path.
- Agentic Commerce Protocols: How the Competing Standards DifferAgentic commerce protocols differ on who holds the payment credential and who owns the order. Compare the four axes, and see which commitments reverse.
- Product Feeds for AI Agents: What Machines Need to CompareProduct feeds for AI agents need typed prices, identifiers and availability. Why advertising feeds fall short, and what to fix before integrating.
How this directory works
Where listings come from
Candidates are found on public MCP directories (PulseMCP, mcpservers.org, MCP Market, Build with Claude), on vendor sites, and through submissions. A directory listing is only a lead; nothing is listed from it alone.
How each one is checked
We read the source repository through the GitHub API (README, file tree, package manifests, licence, archive status), the npm package where one is named, the official MCP Registry, and the vendor's documentation for hosted servers. Last full check: Sept 2026.
What gets listed
Only MCP servers, or plugins that install one, that connect to a commerce platform, perform store operations, or serve a business function ecommerce teams use (SEO, ads, analytics, support, accounting). Duplicates are merged into one listing.
What “official” means
Published by the company whose product the server connects to, from that company's GitHub organisation or own domain. Anything else is labelled third-party company or community.
What is extracted, and how
Integrations, tasks, transport, authentication and the clients a server documents setup for are extracted by a language model from that evidence, with the evidence kept for review. Commands are shown as documented and are not tested by us.
What is not listed
Of 219 candidates reviewed, 48 were plugins, skills or libraries without an MCP server, 45 were not about running a store, 11 were duplicates and 17 had an archived, missing or unverifiable source.
Corrections: hello@ecommerceguide.com.