Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Description from the maker (original English)
Manage a FLUF resale account from an AI agent: inventory, crosslisting and unified orders.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
FLUF_API_TOKEN, FLUF_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"fluf": {
"command": "npx",
"args": [
"-y",
"fluf-mcp"
],
"env": {
"FLUF_API_TOKEN": "your-value",
"FLUF_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add fluf --env FLUF_API_TOKEN=your-value --env FLUF_BASE_URL=your-value -- npx -y fluf-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"fluf": {
"command": "npx",
"args": [
"-y",
"fluf-mcp"
],
"env": {
"FLUF_API_TOKEN": "your-value",
"FLUF_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"fluf": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"fluf-mcp"
],
"env": {
"FLUF_API_TOKEN": "your-value",
"FLUF_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
FLUF_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified against the domain fluf.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: FLUF_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.7) reached the registry 43 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol server that lets an AI agent (Claude, Cursor, Windsurf, Cline, and anything else that speaks MCP) work a FLUF Connect account: read inventory, list items across marketplaces, read orders, ask FLUF's own assistant a question, and raise a support ticket.
One account, one token, every marketplace you've connected — the agent never has to learn a per-marketplace API, and never handles your marketplace credentials.
Six tools are the primitives. Five recipes are the outcomes — named workflows that chain the tools in the right order, surfaced in your client as slash commands. Most people want a recipe.
Recipes ship as MCP prompts. In Claude Desktop and Claude Code they appear as slash commands; in Cursor and other clients, in the prompt picker.
| Recipe | Outcome | Arguments |
|---|---|---|
dead_stock | Finds stock that isn't listed on the channels actually selling for you, ranked by what to crosslist first. | period, limit |
morning_sales | Yesterday's trading in ninety seconds: orders, revenue, channel mix, what changed against a fair baseline. | date, compare |
listing_failures | Investigates failed and stuck listings, groups them by root cause, and proposes a fix per cause. | channel, period |
expansion | Decides what to seed onto a newly connected marketplace, chosen to match what already sells for you. | channel *(required)*, batch_size |
support | Diagnoses a problem through Intesa, then files a support ticket with the evidence attached. | problem *(required)* |
Every argument is optional unless marked, and every recipe has a sensible default — /dead_stock on its own works.
/dead_stock period="30 days" limit=10
/morning_sales compare=previous_week /expansion channel=vinted batch_size=25
Two things the recipes are deliberately strict about, because getting them wrong is how an agent loses a seller's trust:
dead_stock and expansion research and recommend; they call crosslist only after you say yes.| Tool | What it does |
|---|---|
list_channels | Which marketplaces this account has connected, and which it can list to. |
list_products | Your products, with the channels each one is already live on. |
crosslist | List one or more products on one or more marketplaces. |
get_orders | Your orders across every connected marketplace, in one shape. |
list_drafts | Listings a marketplace refused for a fixable reason (size, brand, category, price, wording), with the reason and the editable fields — plus anything waiting for your go-ahead. |
approve_draft | Correct a draft's fields and send it to the marketplace. |
ask_intesa | Ask FLUF's own assistant an open-ended question about your account — why a channel stopped syncing, what a listing error means, what sold and where. |
report_bug | Raise a bug with FLUF support on your behalf — either when you report a problem, or when the agent itself gets stuck and can't finish the job. |
Create one at https://fluf.io/connect/developers — in FLUF Connect that's More → Developers in the left sidebar. It's shown once, so store it like a password. Revoke it on the same screen any time.
You need a FLUF Connect account on an active plan; the API is a paid feature.
Two ways in. Pick the first unless you have a reason not to.
Download `fluf-mcp- .mcpb` from the latest release and open it. Claude Desktop shows an install dialog, asks for your token in a form field, and that's it — no terminal, no JSON, and no Node install: Claude Desktop ships its own Node runtime and uses it for installed bundles.
For Cursor, Claude Code, Windsurf, Cline, or if you'd rather manage it yourself. This route does need [Node](https://nodejs.org) 18+ on your machine — the runtime bundled with Claude Desktop is only used for installed .mcpb bundles, not for claude_desktop_config.json entries, which spawn command from your system PATH.
npm install -g fluf-mcp
Only needed for the npx route — the .mcpb bundle configures itself.
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "fluf": { "command": "npx", "args": ["-y", "fluf-mcp"], "env": { "FLUF_API_TOKEN": "fluf_pat_..." } } } }
claude mcp add fluf --env FLUF_API_TOKEN=fluf_pat_... -- npx -y fluf-mcp
~/.cursor/mcp.json (or a per-project .cursor/mcp.json):
{
"mcpServers": { "fluf": { "command": "npx", "args": ["-y", "fluf-mcp"], "env": { "FLUF_API_TOKEN": "fluf_pat_..." } } } }
| Var | Required | Default | Notes |
|---|---|---|---|
FLUF_API_TOKEN | yes | — | Your personal access token. |
FLUF_BASE_URL | no | https://fluf.io | Override for staging. |
Reach for a recipe when you want an outcome — they encode the tool order and the caveats. Otherwise ask in plain language and the agent picks the tools:
"What have I got in stock that isn't on eBay yet? List the ten cheapest."
"Show me everything that sold last week and which channel it sold on."
"Why did my last five Vinted listings fail?"
Three things worth knowing:
npm install
npm run build FLUF_API_TOKEN=... node dist/index.js
Smoke-test without an MCP client:
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
| FLUF_API_TOKEN=... node dist/index.js
echo '{"jsonrpc":"2.0","id":1,"method":"prompts/list"}' \ | FLUF_API_TOKEN=... node dist/index.js
Recipes live in src/prompts.ts — one entry in RECIPES per recipe, no registration step. They're plain text aimed at the agent, so editing one needs no client change.
MIT — see LICENSE. © FLUF.io.
The server itself is open; the account it talks to is not. You'll still need a FLUF Connect account on an active plan for any of it to do anything.