Fluf

io.flufPublished by fluf.iov0.2.7Updated Oct 24, 2026

Manage a FLUF resale account from an AI agent: inventory, crosslisting and unified orders.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage a FLUF resale account: read inventory and orders, crosslist products to marketplaces, fix failed listings, and file support tickets.

What you can do
Exposes six tools for a FLUF Connect resale account: list_channels shows which marketplaces are connected, list_products shows products and where they are live, crosslist lists products on marketplaces, get_orders returns orders across all connected marketplaces, list_drafts and approve_draft handle listings a marketplace refused, ask_intesa queries FLUF's own assistant, and report_bug raises a support ticket. It also ships named recipes as MCP prompts, such as dead_stock, morning_sales, listing_failures, expansion and support, which chain the tools into workflows.
When to use it
Use it when you sell on multiple marketplaces through FLUF Connect and want an assistant to research what to crosslist, summarize sales, diagnose failed listings, or open support tickets without handling per-marketplace APIs or credentials.
Requirements
A FLUF Connect account on an active paid plan, plus a personal access token supplied as the FLUF_API_TOKEN environment variable. The recommended Claude Desktop bundle needs no Node install; the npx route requires Node 18 or later. FLUF_BASE_URL optionally overrides the API host, which defaults to the FLUF site.
Before you install
The token is shown once and should be stored like a password; it can be revoked from the same settings screen. crosslist and approve_draft change data on marketplaces, and listings may be queued in your own browser rather than completed immediately, so a repeat can duplicate a listing. Recipes are documented as listing nothing without confirmation. ask_intesa sends account questions to FLUF's assistant and can take up to a minute.

Installation

In SourceWeft

  1. Open Fluf in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

RecipeOutcomeArguments
dead_stockFinds stock that isn't listed on the channels actually selling for you, ranked by what to crosslist first.period, limit
morning_salesYesterday's trading in ninety seconds: orders, revenue, channel mix, what changed against a fair baseline.date, compare
listing_failuresInvestigates failed and stuck listings, groups them by root cause, and proposes a fix per cause.channel, period
expansionDecides what to seed onto a newly connected marketplace, chosen to match what already sells for you.channel (required), batch_size
supportDiagnoses 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_stock and expansion research and recommend; they call crosslist only 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

ToolWhat it does
list_channelsWhich marketplaces this account has connected, and which it can list to.
list_productsYour products, with the channels each one is already live on.
crosslistList one or more products on one or more marketplaces.
get_ordersYour orders across every connected marketplace, in one shape.
list_draftsListings 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_draftCorrect a draft's fields and send it to the marketplace.
ask_intesaAsk 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_bugRaise 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-<version>.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 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.

bash
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:

json
{  "mcpServers": {    "fluf": {      "command": "npx",      "args": ["-y", "fluf-mcp"],      "env": { "FLUF_API_TOKEN": "fluf_pat_..." }    }  }}

Claude Code

bash
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):

json
{  "mcpServers": {    "fluf": {      "command": "npx",      "args": ["-y", "fluf-mcp"],      "env": { "FLUF_API_TOKEN": "fluf_pat_..." }    }  }}

Environment variables

VarRequiredDefaultNotes
FLUF_API_TOKENyes—Your personal access token.
FLUF_BASE_URLnohttps://fluf.ioOverride 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

bash
npm installnpm run buildFLUF_API_TOKEN=... node dist/index.js

Smoke-test without an MCP client:

bash
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

[email protected]

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.

Source: README.md at commit a121d67

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.2.7LatestSep 27, 2026
  2. v0.1.2Sep 16, 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 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