Spree Commerce: open-source B2B and marketplace ecommerce
RemoteAbout Spree Commerce: open-source B2B and marketplace ecommerce
An MCP server for the Spree back office, allowing MCP clients to manage catalogs, ask reporting questions, and configure stores in plain language. Its tools follow Spree API key tenancy and permissions, and are supplied by spree_core.
Key features
- 01Manage product catalogs
- 02Ask business reporting questions
- 03Manage store setup
- 04Limit tool visibility by API key scope
- 05Reuse tools and permissions from spree_core
Use cases
- 01Adjust merchandise through an agent
- 02Ask about sales reports in plain language
- 03Configure a store within granted permissions
MCP support
It exposes Spree back-office tools to MCP clients at POST /api/v3/admin/mcp and authenticates with a Spree secret API key. Credential scopes determine available tools; their definitions and permission gates live in spree_core.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://{store_domain}/api/v3/admin/mcpclaude mcp add --transport http spree-ecommerce-b2b-marketplace https://{store_domain}/api/v3/admin/mcp{"mcpServers":{"spree-ecommerce-b2b-marketplace":{"type":"http","url":"https://{store_domain}/api/v3/admin/mcp"}}}Open in Cursor{"servers":{"spree-ecommerce-b2b-marketplace":{"type":"http","url":"https://{store_domain}/api/v3/admin/mcp"}}}Open in VS Code{"mcpServers":{"spree-ecommerce-b2b-marketplace":{"type":"http","url":"https://{store_domain}/api/v3/admin/mcp"}}}{"mcpServers":{"spree-ecommerce-b2b-marketplace":{"serverUrl":"https://{store_domain}/api/v3/admin/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMESpree MCP Server
A Model Context Protocol server for the Spree back office. Any MCP client — Claude Code, Cursor, an in-house agent — can merchandise the catalog, answer reporting questions and manage store setup in plain language, under the same tenancy and permission rules as the Admin API.
spree add mcp # or add gem 'spree_mcp' to the Gemfile
The endpoint is POST /api/v3/admin/mcp, authenticated with a Spree secret API
key sent as X-Spree-API-Key: sk_… or Authorization: Bearer sk_…. The key's
scopes decide which tools the model is offered, so an agent is never told about
a capability its credential does not carry.
This gem is a protocol adapter and nothing more. The tools, their schemas and
the permissions gating them live in spree_core as Spree.admin_agent_tools, which
means an extension registers a tool without depending on this gem, and the
dashboard assistant offers the same tools over a different transport.
See the documentation
and docs/plans/6.0-mcp-server.md.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.