SkillFoxx

Spree Commerce MCP

Spree admin MCP: an assistant finds products, builds reports, cancels orders and edits the catalog within granted rights.

  • 15,833 ★ on the repository
  • Last commit
  • BSD-3-Clause
MCP serverOfficial

Broad access

Why this level

  • The assistant cancels orders, captures payments and processes refunds with the user rights.
  • Customer and order data goes into the model context.
All reasons and checks

spree/spreeAuthor:spree

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/spree-commerce

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The assistant cancels orders, captures payments and processes refunds with the user rights.
  • Customer and order data goes into the model context.

This is third-party code. Review the repository files before installing.

What it does

A Spree store hosts the MCP server itself, with nothing separate to deploy: the `spree_mcp` gem is in the starter `Gemfile` of new stores. The address is `https://your-store/api/v3/admin/mcp`. It is the back office with catalog, orders, reports and store settings, not the storefront. Each assistant task maps to an Admin API action: find products, report on sales, cancel an order, capture a payment, mark a delivery, add a market. A person picks the permissions when connecting over OAuth, the assistant sees only approved tasks and never exceeds the user own rights. There is also a separate documentation MCP at `spreecommerce.org/docs/mcp` for people writing store code.

Who it is for. Owners and staff of Spree stores who want to run the catalog, orders and reports in a conversation with Claude, Cursor or ChatGPT.

Good fit when

  • You need to learn quickly what sold in Germany last month and get a report without a spreadsheet export.
  • The assistant finds products by conditions and edits descriptions in a batch.
  • A manager cancels an order or marks shipment and delivery right from the chat.
  • A store developer teaches the assistant custom tasks through custom tools.

Not a fit when

  • The assistant is for shoppers on the storefront: the server is built for the staff back office.
  • A nightly sync or data exchange with no person involved: use the Admin API or the `spree api` CLI.
  • Staff should not touch payments and refunds: permissions would have to be narrowed at every connection.

Example request

How many orders shipped to Germany last month? Show the report and suggest which order with an address error to cancel, but cancel only after my confirmation.

MCP

Transport
http
Authentication
OAuth

Limitations

This is a server part of Spree 6 and newer: a store without `spree_mcp` has no server, and it is added with `spree add mcp` or a line in the `Gemfile`. The assistant never gets API keys, integrations and webhooks, roles and staff accounts, gift card and discount codes, or customer erasure: those actions sit outside the server. Permissions are fixed at connection time and do not grow with yours. The server rejects API keys, and unattended nightly tasks need the Admin API. A person signing in to the store admin over OAuth is required.

How to disable. In the admin open Settings, AI Agents and revoke the assistant access: it stops working from the next request. To remove the server completely, delete the `spree_mcp` gem from the `Gemfile`.

FAQ

What is needed to connect?

A Spree 6 store with `spree_mcp` and the address `https://your-store/api/v3/admin/mcp`. The client sends you to the store sign-in, where you approve the permissions.

How do I connect Claude Code?

In the admin open Settings, AI Agents, Connect an agent and choose Claude. The Claude Code tab shows a ready `claude mcp add --transport http` command with your client ID and port `3118`.

Can the assistant do more than I can?

No. You can hand over only the rights you hold, and extra requested rights are dropped.

What is off limits to the assistant?

API keys, integrations and webhooks, roles, staff accounts, gift card and discount codes, and customer erasure.

How does this differ from the documentation MCP?

The documentation server helps write code and searches Spree docs. The admin server runs a real store.

Discussion

No questions or reviews yet.

MCP servers
Russian stack

An MCP server for the InSales online store platform: products, orders, customers and categories via the admin API

MCP serverBroad access1

RetailCRM MCP

retailcrm-mcp

Russian stack

RetailCRM MCP server: orders, customers, products, stock, payments, tasks and store analytics via API v5

MCP serverBroad access2

MoySklad MCP

moysklad-mcp

Russian stack

MoySklad MCP server with 60 tools: products, stock, orders, shipments, receipts, payments, profit reports

MCP serverBroad access10
Russian stack

An MCP server for MoySklad: product and stock search, counterparties by INN, creating and reading orders, a sales summary via a single npx package

MCP serverBroad access

RetailCRM MCP server

RetailCRM MCP Server

Russian stack

A RetailCRM MCP server with one-click Railway or Render deploy: orders, customers, products, statistics and reference data

MCP serverBroad access1

A local MCP server gives an assistant 379 tools for the eBay Sell APIs: listings, orders, payouts, ads and seller analytics.

MCP serverBroad access199

README in short

The Spree README mentions the local MCP server, agent skills and the documentation MCP. Structure, permissions and the task list are covered in the `developer/mcp` documentation section.

README badge

Report a problem