Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Fluf MCP
Overview
Description from the maker (original English)
Manage a FLUF resale account from an AI agent: inventory, crosslisting and unified orders.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: FLUF_API_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
FLUF_API_TOKEN,FLUF_BASE_URL
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
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.
Or copy the settings yourself
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.
Or copy the settings yourself
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.
Values you fill in
- Personal access token from https://fluf.io/connect/settings (Developer tab). Requires an active FLUF plan.
FLUF_BASE_URLenvOverride the API host. Defaults to https://fluf.io.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain fluf.io (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1744 servers in this category
- Published to the registry more recently than 46% of the other 1744 servers in this category
- Basic checks equal to or better than 100% of the other 1744 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Fluf MCP safe?
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.
What keys or codes does it need?
You need to fill in: FLUF_API_TOKEN
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.7) reached the registry 40 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
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.
fluf-mcp — FLUF Connect for AI agents
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
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:
- Nothing gets listed without confirmation.
dead_stockandexpansionresearch and recommend; they callcrosslistonly after you say yes. - Queued is reported as queued. Extension-first channels finish in your own browser, so an item can be accepted but not yet live. The recipes say so rather than claiming success, and they don't re-push (a repeat can duplicate the listing).
Tools
| 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. |
Get a token
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.
Install
Two ways in. Pick the first unless you have a reason not to.
Claude Desktop — one click, no Node (recommended)
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.
Everything else — npx
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
Configure
Only needed for the npx route — the .mcpb bundle configures itself.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "fluf": { "command": "npx", "args": ["-y", "fluf-mcp"], "env": { "FLUF_API_TOKEN": "fluf_pat_..." } } } }
Claude Code
claude mcp add fluf --env FLUF_API_TOKEN=fluf_pat_... -- npx -y fluf-mcp
Cursor
~/.cursor/mcp.json (or a per-project .cursor/mcp.json):
{
"mcpServers": { "fluf": { "command": "npx", "args": ["-y", "fluf-mcp"], "env": { "FLUF_API_TOKEN": "fluf_pat_..." } } } }
Environment variables
| Var | Required | Default | Notes |
|---|---|---|---|
FLUF_API_TOKEN | yes | — | Your personal access token. |
FLUF_BASE_URL | no | https://fluf.io | Override for staging. |
Using it
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:
- Always call `list_channels` first. The available marketplaces differ per account and change over time; don't hardcode a list.
- `crosslist` is not always instant. Some channels are handed to your own browser session to complete, so the response may say *queued* rather than *listed*. Read the per-channel status; don't assume success.
- `ask_intesa` is the slow, clever one. It hands the question to Intesa, the assistant inside FLUF, which runs its own multi-step investigation before answering — so it can explain *why* something happened, not just report what is. Replies can take up to a minute. Use the direct tools for simple reads; reach for this when the question is diagnostic or open-ended.
Develop
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.
Support
License
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.