What Is MCP? A Plain-English Guide for Resellers
What the Model Context Protocol is, in plain English — and how it lets an AI assistant do real work on your reselling account.
Short version: MCP (Model Context Protocol) is an open standard that lets AI assistants connect to software safely. FLUF Connect has an MCP server, so you can ask an assistant like Claude or Cursor to do real work on your reselling account — find dead stock, summarise yesterday’s sales, crosslist a batch, chase failed listings — in plain English, without clicking through the dashboard yourself. It is included on every FLUF Connect plan.
What is MCP?
MCP, or the Model Context Protocol, is an open standard that lets AI assistants connect securely to other software. It was published by Anthropic and is freely available for anyone to implement, which is why support for it has spread quickly across AI tools.
The easiest way to picture it is USB-C for AI. Before USB-C, every device needed its own cable. Now one connector works across laptops, phones and monitors. MCP does the same job for AI assistants: instead of every AI company building a custom integration with every piece of software, an application publishes one MCP server and any MCP-capable assistant can use it.
Why does MCP matter for resellers?
Because it changes what you can ask for. Most reselling software makes you find the right screen, apply the right filter, and read the answer yourself. With MCP, you describe the outcome and the assistant does the steps.
| Without MCP | With MCP |
|---|---|
| Every AI tool needs a custom integration built for it | One MCP server works with every assistant that speaks MCP |
| You click through screens to get an answer | You ask a question and get the answer |
| New AI models mean new integration work | Future assistants use the same connection |
| Multi-step jobs are done by hand | Multi-step jobs run as one instruction |
What can an AI assistant actually do with FLUF Connect?
The FLUF MCP server gives an assistant six things it can do on your account. It never sees or handles your marketplace passwords — it works through your FLUF Connect account, across whichever marketplaces you have already connected.
- See your channels — which marketplaces the account is connected to, and which it can list to.
- Read your products — your inventory, and which channels each item is already live on.
- Crosslist — list one or more products to one or more marketplaces.
- Read your orders — every connected marketplace’s sales, in one consistent shape.
- Ask FLUF’s own assistant — open questions about your account, like why a channel stopped syncing or what a listing error means.
- Raise a support ticket — either because you asked, or because the assistant got stuck and needs a human.
Five ready-made jobs you can just ask for
Tools are the building blocks. What most people want is the outcome, so FLUF ships five named workflows that chain those tools in the right order. In Claude Desktop and Claude Code they show up as slash commands; in other clients they appear in the prompt picker.
| Ask for this | What you get back |
|---|---|
dead_stock |
Stock that isn’t listed on the channels actually selling for you, ranked by what to crosslist first. |
morning_sales |
Yesterday’s trading in ninety seconds — orders, revenue, channel mix, and what changed against a fair baseline. |
listing_failures |
Failed and stuck listings, grouped by root cause, with a suggested fix for each cause. |
expansion |
What to seed onto a marketplace you have just connected, chosen to match what already sells for you. |
support |
A diagnosis of your problem, and a support ticket filed with the evidence attached. |
Is it safe to let an AI touch my shop?
This is the right question to ask, and the honest answer is that safety comes from limits, not trust. MCP does not hand an assistant the keys to your account. The application decides exactly what is exposed, and FLUF Connect applies four limits:
- You mint the connection, and you can revoke it. Access runs on a token you create in FLUF Connect under Settings → Developer. It is shown once, you store it like a password, and you can revoke it there at any moment.
- Nothing gets listed without your say-so. The
dead_stockandexpansionworkflows research and recommend. They only publish after you confirm. - You can see what it did. The Agents panel in Settings → Developer shows what an assistant listed, what failed, and lets you cut its access.
- Queued is reported as queued. Some marketplaces finish listing in your own browser, so an item can be accepted but not yet live. The workflows say so rather than claiming success, and they will not re-push an item and risk duplicating it.
How to get started
- Check your plan. MCP access is included on every FLUF Connect plan — there is no separate developer tier and no extra credential to buy. See plans and pricing.
- Create a token. In FLUF Connect, go to Settings → Developer and create a personal access token. Copy it somewhere safe — it is only shown once.
- Add FLUF to your assistant. Install the fluf-mcp package and paste your token into your client’s configuration. Full setup instructions for each client are on the FLUF developers page.
- Ask for something. Start with
dead_stockormorning_sales— both work with no arguments at all.
The same token also works with FLUF’s REST interface and sale notifications, so one credential covers everything on the developers page.
Why FLUF built an MCP server
Reselling at scale is mostly repeated judgement: what is not selling, where should it go next, what broke overnight. Those are exactly the questions an assistant is good at, provided it can see real data rather than guess. Supporting an open standard means FLUF works with the assistant you already use, and keeps working with whatever you switch to next — without us building a separate integration each time.
It also means the work happens where you are. If you live in Claude or Cursor all day, you no longer have to break off and go clicking through a dashboard to find out which fifty items deserve a push to a new marketplace.
Save 40% when you pay yearlySources & Verification
Last verified: 2026-08-02. Please contact us if any detail here is out of date.
- Model Context Protocol — official documentation — the open standard, and what it specifies
- fluf-mcp on npm — the published FLUF MCP server, version and licence
- FLUF-io/fluf-mcp on GitHub — source, tools and workflow definitions
- FLUF Connect developers page — setup instructions and token management
- FLUF Connect integrations — the marketplaces an assistant can list to
Frequently Asked Questions
MCP stands for Model Context Protocol. It is an open standard that lets AI assistants connect securely to software and services, so an assistant can read information and carry out actions instead of only chatting.
You need to paste a token into your AI assistant's settings once, following the step-by-step instructions on the FLUF developers page. After that you type ordinary sentences. The five ready-made workflows run with no arguments at all, so typing /dead_stock on its own works.
Any assistant that supports MCP, including Claude Desktop, Claude Code, Cursor, Windsurf and Cline. Because MCP is an open standard rather than a private integration, assistants that add support later will work too, with no change needed at your end.
No. The dead stock and expansion workflows research and recommend, then only publish after you confirm. You can also see everything an assistant did in the Agents panel under Settings and revoke its access at any time.
No. The assistant connects to your FLUF Connect account using a token you create and can revoke. It never sees or handles your Depop, eBay, Vinted or other marketplace credentials.
It is included on every FLUF Connect plan. There is no separate developer tier and no additional credential to buy. The cheapest plan is Growth at 19 pounds a month for 1,000 products, and paying yearly saves 40% on any plan.
Start with morning_sales for a summary of yesterday's trading across every connected marketplace, or dead_stock to find inventory that is not listed on the channels actually selling for you. Both work immediately with no setup beyond connecting the token.