Developers › Docs › MCP server
MCP server
Let an AI assistant work a FLUF account directly.
FLUF ships a Model Context Protocol server, so any MCP-compatible assistant — Claude, Cursor, Cline, or anything else that speaks MCP — can work a FLUF account directly, in plain language.
Source is open on GitHub under the MIT licence, published to npm as fluf-mcp.
Install
Add it to your client's MCP configuration:
{
"mcpServers": {
"fluf": {
"command": "npx",
"args": ["-y", "fluf-mcp"],
"env": { "FLUF_API_TOKEN": "fluf_pat_your_token" }
}
}
}
The token is the same Personal Access Token the REST API uses — create one under More → Developers in FLUF Connect. See Getting started.
What it can do
| Tool | |
|---|---|
list_products | Search and filter the catalogue |
list_channels | The marketplace accounts connected |
crosslist | Publish items to marketplaces |
get_orders | What sold, where, and when |
delete_products | Remove products from FLUF (restorable for 60 days); optionally end their marketplace listings too |
ask_intesa | Ask FLUF's own assistant an open-ended question |
report_bug | File a bug against FLUF with context attached |
Then just ask:
- "What's in stock that isn't on eBay yet? List the ten cheapest."
- "What sold last week, and on which channel?"
- "List these forty items on Vinted and Depop."
ask_intesa is worth knowing about: Intesa is the assistant built into FLUF and can see listing history, sync records and error text the REST API doesn't expose. For "why did my last five listings fail?", it gives FLUF's own answer rather than the model's guess.
Two things to tell your assistant
crosslist publishes to real marketplaces. Reads are free; publishing is not reversible in one call and a re-run can create duplicates. Confirm before calling it, and never re-push an item already reported as queued.
queued is not failed. Some marketplaces publish asynchronously and legitimately sit queued for a few minutes. An assistant that reads queued as a failure and retries is how duplicate listings get made.
Token scope
A token can do everything your plan allows. On Seller that means reading only, so list_products, list_channels, get_orders, ask_intesa and report_bug work, but crosslist and delete_products are refused. Pro and above can do everything. If you give an assistant a token, create a separate token for it so you can revoke that one without affecting anything else.
Something missing? Email [email protected] — we prioritise by what people actually ask for.
