An e-commerce MCP server for Claude, ChatGPT and Cursor

Yes: CommerceForAI is a commerce API that ships its own MCP server. Connect it and an AI agent can run a store: create products, adjust stock, look up and refund orders, buy shipping labels, handle returns, issue gift cards and send invoices. The commerce backend and the MCP server are one product, so there is nothing to wrap or host.

Connect it

Hosted, with no install. Add this as a connector in Claude, ChatGPT or any MCP client that supports remote servers. The store owner signs in and picks read-only or full access.

https://api.commerceforai.com/mcp

Or run it locally with an API key (Claude Code, Cursor, Claude Desktop):

.mcp.json

{
  "mcpServers": {
    "commerce": {
      "command": "npx",
      "args": ["-y", "@commerceforai/mcp"],
      "env": { "COMMERCEFORAI_API_KEY": "cfa_...", "COMMERCEFORAI_MAX_REFUND": "5000" }
    }
  }
}

No store yet? npx commerceforai init creates a free test store and API key without signing up.

What the agent can do

Area	Examples
Catalog	Create and update products and variants, collections, images; import from Shopify, Printify or Printful
Stock	List inventory, find low stock, adjust or set counts
Orders	Search orders, mark shipped, split shipments, edit an order before it ships, refund
Shipping and returns	Get label rates, buy a label, open, approve and receive returns
Selling	Discount codes, automatic discounts, gift cards, draft orders and invoices, subscriptions
Insight	Sales reports, customers, sales tax by state

About 65 tools in all. Add ?toolsets=core to the URL to load only the 20 everyday ones and keep the agent's context small.

Limits the owner controls

Read-only connections can look things up and change nothing.
Spending caps: a largest refund and a largest shipping label, enforced on the server. Hosted connections default to $50 each.
Limited API keys: a key can be read-only or capped per refund, label and gift card, whatever client it's used from.
Previews: order edits and store syncs can be run as a dry run first.

How this differs from an MCP wrapper around another platform

Most commerce MCP servers are adapters over an existing platform's admin API, written by someone else. Here the API, the errors and the tools are designed together for agents: errors say what to fix, setup_status lists what's left before the store can sell, and simulate_order runs a full test purchase without a browser. See how it compares.

Listed in the official MCP Registry as com.commerceforai/mcp. Source: github.com/leeshadle/commerceforai-js.