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.

Hosted server (no install)

Assistants that connect to a URL rather than running a local command — Muse custom connectors, web-based chat apps, hosted agent platforms — can use FLUF's hosted MCP server instead:

URL:     https://fluf.io/wp-json/fc/mcp
Auth:    OAuth sign-in, or Authorization: Bearer fluf_pat_your_token

It is a Streamable HTTP server with the same tools and behaviour as the npm package. Clients that support OAuth (Claude, ChatGPT) discover it on their own: you sign in to FLUF and approve access, and there is no token to copy. Other clients take a token. Enter it in your assistant's credential or connector settings, not in the chat.

Claude

Works in Claude on the web, desktop and mobile apps:

1. Open Customize → Connectors, choose Add → Add custom connector.
2. Name it FLUF Connect and enter https://fluf.io/wp-json/fc/mcp.
3. Select Connect, sign in to FLUF and choose Allow.

Claude runs the read tools (products, channels, orders, drafts) without asking and asks your approval before anything that publishes, deletes or messages FLUF support. To disconnect, revoke the Claude token under More → Developers in FLUF Connect.

Muse

In Muse Code, add the npm server to your MCP settings the same way as above. In Muse, create a custom connector with this prompt:

Create a custom connector for FLUF Connect, my multichannel selling platform. It is a remote MCP server at https://fluf.io/wp-json/fc/mcp (Streamable HTTP) that authenticates with the header Authorization: Bearer . Ask me for my FLUF API token through your secure credential flow. Don't have me paste it into the chat.

What it can do

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, including the one created when you connect Claude, can do everything your plan allows. On Pro (including Pro Legacy) that means reading only, so list_products, list_channels, get_orders, ask_intesa and report_bug work, but crosslist, delete_products and approve_draft are refused. Super Seller 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.