Spree Commerce: open-source B2B and marketplace ecommerce

io.github.spreePublished by GitHub account spreev6.0.1Updated Nov 6, 2026

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

The publisher's own server: Source

VerifiedStreamable HTTPWeb executableProductivity & Workflow Business & Commerce

Server details

Identifier: io.github.spree/ecommerce-b2b-marketplace
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 30, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account spree for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.spree%2Fecommerce-b2b-marketplace.svg)](https://sourceweft.com/mcp/io.github.spree%2Fecommerce-b2b-marketplace?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Spree's MCP server lets an AI assistant merchandise a Spree store's catalog, answer reporting questions and manage store setup in plain language.

What you can do: Merchandise the catalog: create and edit products and related catalog data through the Spree back office tools.
Answer reporting questions about the store's data.
Manage store setup and configuration.
Operate under the same tenancy and permission rules as the Admin API, with tools gated by the signed-in admin's permissions.
When to use it: Use it when you run a Spree store and want an MCP client such as Claude Code, Cursor or an in-house agent to handle catalog merchandising, store setup and reporting through the admin back office.
Requirements: A Spree store with the MCP server enabled (added via the spree CLI or the spree_mcp gem). The remote endpoint is POST /api/v3/admin/mcp on the store domain and requires an OAuth token issued to a person, who signs in and approves the requested permissions. Secret API keys are refused.

Before you install

The assistant can change store data such as catalog and setup, so review write actions before approving. Access is tied to a person's OAuth approval and their admin permissions; the token is narrowed to what was approved. Secret API keys are deliberately rejected, so unattended jobs need the Admin API or CLI instead.

Installation

In SourceWeft

Open Spree Commerce: open-source B2B and marketplace ecommerce in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

Spree 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.

The endpoint is POST /api/v3/admin/mcp, authenticated with an OAuth token issued to a person: the client sends them to the store to sign in and approve what it may do. The token carries that admin's own permissions, narrowed to what they approved, and those decide which tools the model is offered, so an agent is never told about a capability its credential does not carry.

A Spree secret API key (sk_…) is deliberately refused here. A nightly job or a server-side integration has no person behind it; it calls the Admin API with a key, or uses the spree api CLI.

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.

Source: spree/mcp/README.md at commit 4f54659

Tools

SourceWeft has not read this server's tools yet.

Version history

v6.0.1LatestOct 30, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts