About the Fuse Inventory MCP

What Is the Fuse Inventory MCP?

The Fuse Inventory MCP connects Claude to your Fuse account so you can ask questions about your live inventory in plain English and get answers grounded in your Fuse data. It uses the Model Context Protocol (MCP), the open standard for connecting AI assistants to business systems.

Once you connect, you can ask about stock levels, open purchase orders, demand and reorder recommendations, historical sales, vendor performance, product relationships, and the cash and cost picture behind them. Claude reads the answer live from Fuse and shows how it got there, so the numbers are current and complete every time.

This version is strictly read-only. Claude reads your Fuse data and answers questions. It cannot modify, delete, or overwrite data in your Fuse account or connected systems.

Requirements

Before you connect, you will need:

An active Fuse Inventory account. Answers come from your validated Fuse data.
A Claude account with connector access. Custom connectors require a paid Claude plan.
A Claude organization owner to enable the connection. For Claude Team and Enterprise accounts, the Fuse Inventory MCP must be enabled by an organization owner.

Who Should Use the Fuse Inventory MCP?

The Fuse Inventory MCP is for multi-channel inventory planners and brand operators who manage their inventory in Fuse. The connector can be used to automate inventory planning and supply chain workflows and make working-capital decisions from current, validated data without exporting a report. This includes:

Operations teams who track stockout risk, reorder timing, inbound POs, and vendor reliability.
Financial analysts who ask about inventory value, open commitment, and gross profit at risk.
Founders who want a fast read on stock, purchasing, and cash without opening the platform.

What Can the Fuse Inventory MCP Answer?

To Find	Ask Something Like
Your current stock and what it's worth	"What are my stock levels by warehouse, and what is my inventory worth right now?"
What runs out and what to order	"Which SKUs stock out in the next 90 days, and what should I reorder?"
What's arriving and when	"What's on open POs, when does it land, and what does it cost?"
Your working capital position	"How much cash is tied up in inventory, and how much gross profit is at risk from stockouts?"
Which vendors are reliable	"Which vendors run late most often, and by how many days?"
How your products relate	"What is this product made of, and what else uses this component?"
A specific product	"Find the SKU for our lavender hand cream."

Fuse Inventory MCP Tools

The connection exposes eight read-only tools:

Tool	What It Does
`find_products`	Look up a SKU by name or partial SKU
`get_stock_levels`	Current stock and inventory value by SKU and warehouse
`get_sales_report`	Units and revenue by SKU, channel, and period, with forecast
`get_order_recommendations`	Predicted stockouts and recommended reorders
`get_spend_and_cost_analysis`	Inventory value, open commitment, and profit at risk
`get_upcoming_stock`	Open POs, inbound lines, and ETAs
`get_vendor_performance`	Vendor reliability and current overdue lines
`understand_product_relations`	Bill of materials and where components are used

find_products

Searches your catalog by SKU or product name and returns a short summary for each match. Claude uses this to find the exact SKU before it calls another tool.

Returns: the SKU, product name, ID, gross price, and unit cost for each match.
Example question: "Find the SKU for our lavender hand cream."
When it's used: to find an exact SKU from a name or partial SKU before calling another tool.

get_stock_levels

Reports your current stock at the level of each SKU and warehouse, valued at cost, with totals by SKU and by warehouse.

Returns: on-hand, available, inbound, and reserved units per SKU and warehouse, plus inventory value.
Example question: "Get stock levels for this SKU across all warehouses."
When it's used: when you ask about current stock on hand, availability, or what inventory is worth right now.

get_sales_report

Pulls units and revenue per SKU over a date range (default last 90 days), with rollups by channel and period, along with each SKU's forecast and actuals.

Returns: placed, fulfilled, forecasted, and projected units and revenue. Revenue is top line only; does not include cost, COGS, or margin.
Example question: "What are my top sellers by revenue over the last quarter?"
When it's used: when you ask about sales, revenue, top sellers, a channel breakdown, or how actuals are tracking against forecast.
Note: the four measures answer different questions and should not be compared to each other. Placed is keyed to when an order was placed, fulfilled to when it was shipped, forecast is the forecast in Fuse, and projected combines actuals to date with forecast for the rest of the window.

get_order_recommendations

Tells you which SKUs are predicted to run out within a timeframe you set, along with recommended order quantities and timelines to prevent stockouts. Claude explains the order recommendations generated in Fuse. It does not generate the forecast.

Returns: at-risk SKUs with predicted stockout dates, and the recommended purchase orders with quantity, place-by date, and estimated cost.
Example question: "Which SKUs stock out in the next 90 days, and what should I reorder?"
When it's used: when you ask what will run out, what to reorder, or how much to reorder within a timeframe.
Note: the recommendations are only as current as Fuse's most recent run. When your timeframe extends past the forecast dates, Claude reports that as "not forecast yet," rather than "no risk."

get_spend_and_cost_analysis

Gives you the financial picture behind your inventory: what you own, what you owe, and what's at risk.

Returns: inventory value at cost and at gross price, open PO commitment including what you still owe, a spend calendar by arrival date, and gross profit at risk from predicted stockouts.
Example question: "How much cash is tied up in inventory, and how much gross profit is at risk from stockouts?"
When it's used: when you ask about total cash tied up, what you still owe on open POs, upcoming spend, or profit at risk.
Note: margin figures are gross, not contribution. Fuse doesn't track outbound shipping, fulfillment cost, or discounts, so the number doesn't include them. This tool works at the company- and vendor-level. For the cash tied up in a specific SKU, ask for stock levels sorted by value instead.

get_upcoming_stock

Shows your open POs: inbound line items with ETAs, financial totals per PO, or the full details for a specific PO.

Returns: what's arriving, when it lands, and what it costs, with overdue lines flagged.
Example question: "Give me a summary of inventory currently on order. Include ETAs."
When it's used: when you ask about open POs, inbound inventory, ETAs, or which POs are late.
Note: inbound warehouse transfers aren't purchase orders, so they don't appear here.

get_vendor_performance

Measures how reliably your vendors deliver.

Returns: two views per vendor: the vendor's open PO lines currently past their ETA, and the vendor's historical track record (on-time rate, average delay, and worst delay) measured against each line's original committed ETA.
Example question: "Which vendors historically run behind the most?"
When it's used: when you ask which vendors are reliable or which vendors run late.
Note: the two views answer the example question differently and can correctly name different vendors. The overdue view is a snapshot of late POs as of right now, so it comes back empty if nothing is currently past ETA. A vendor with late shipments now but nothing received during the specified time frame will return an empty track record, which means there is no data for that time period, not necessarily a clean record.

understand_product_relations

Maps how your products relate to each other in both directions.

Returns: the bill of materials, the assemblies that use a component, merge history, variant groupings, and fulfillment aliases.
Example question: "What is this product made of, and what else uses this component?"
When it's used: when you ask what a product is made of or what other products use a given component.
Note: components come back as SKUs, not names, so answering the example question in plain language may require a second lookup with find_products or get_stock_levels. Merge, variant, and fulfillment fields only appear when the product has those relationships, so an empty field means there is genuinely no relationship there, not missing data.

Answers Grounded in Your Fuse Data

Claude is only as good as the data behind it. The Fuse Inventory MCP is designed so answers reflect the current state of your Fuse data.

Answers come only from Fuse. Claude doesn't guess or invent numbers. If Fuse has no data for your question, the answer says so.
You get live data, not a stale export. Claude reads from Fuse the moment you ask, so the numbers match what's in Fuse right now.
Fuse makes the recommendations; Claude explains them. Fuse computes the reorder and stockout recommendations, and Claude reads them back and walks you through the reasoning. To regenerate them, use the Fuse app, not this connection.
You can tell how fresh a recommendation is. Recommendations are only as current as Fuse's most recent run, and the answer tells you when that was.
Each number tells you what it covers. When an answer reports a margin, for example, it's gross rather than contribution, and Claude tells you so up front.
When a sales channel stops syncing, its numbers read as zero instead of missing. A stale zero can look like missing data. To tell them apart, check when the channel last synced. The answer reports the last sync time for each channel.

How to Connect Fuse to Claude

Connect the Fuse Inventory MCP in the Claude app and authorize it with your Fuse account. Setup takes minutes and requires no engineering.

For step-by-step instructions, see Connect the Fuse Inventory MCP to Claude.

What the Fuse Inventory MCP Doesn't Do

Write access is not yet supported. The MCP is read-only, so it can't create or edit POs, plans, products, or anything else. Make those changes in the Fuse app.
It doesn't create order recommendations. Fuse generates order recommendations; Claude reads them back and explains them. When you want fresh recommendations, regenerate them in Fuse.
Shipments and Transfers are not yet available via MCP. Questions about shipment and transfer data won't return results.
Margin is gross, not contribution. Fuse doesn't track outbound fulfillment cost or discounts, so all margin calculations are gross margins.
The MCP only has access to the data available in Fuse. If it's not tracked in Fuse, the MCP won't surface it.
It's not a general chatbot. The MCP answers from your validated Fuse data, not from the open web, so it won't take questions that aren't about your inventory.

Fuse Inventory MCP Security and Permissions

The Fuse Inventory MCP is read-only, runs over an encrypted and permissioned connection, and doesn't train AI models on your data. The table covers its access mode, connection, permission scope, model-training policy, and protocol.

Aspect	What to Know
Access mode	Read-only. Claude reads your Fuse data and answers. It cannot modify, delete, or overwrite data in your Fuse account or connected systems.
Connection	Uses a remote connection over HTTPS, using streamable HTTP transport and OAuth 2.0 authentication with your existing Fuse credentials. Your data stays in Fuse and is read only when you ask.
Permission scope	Scoped to your Fuse account. No tool can reach data outside the authenticated Fuse account. A Fuse admin enables MCP access for the account.
Model training	Your data is not used to train any AI model. Claude also applies its own data policies.
Protocol	The connection runs on MCP, the open standard for connecting AI assistants to business systems.

For full details on how your data is handled, see the Fuse Inventory Connector Privacy Policy.

Limits and Technical Notes

Rate limits: Requests are limited to a rolling 200 calls per hour per account, with a burst ceiling of 20 back-to-back calls.

Result caps and pagination: Most tools cap the number of rows they return. Five surfaces let you page through the full result set with the offset parameter:

get_stock_levels: 500 rows
get_order_recommendations: 300 rows
get_sales_report: 300 rows
get_upcoming_stock (lines view): 500 lines
get_upcoming_stock (orders view): 200 rows

Two tools cap each response but don't paginate: find_products returns up to 200 products, and understand_product_relations returns up to 500. To get more, narrow the query or pass specific SKUs. The detail view of get_upcoming_stock returns up to 10 named POs and doesn't paginate.

Totals and rollups always cover the full result set even when the rows are truncated, with one exception: the per-SKU rollup in get_stock_levels covers only the 200 highest-value SKUs, and an omittedSkuRollups count reports the rest.

Data grain: Stockout dates in get_order_recommendations are keyed to each SKU and stock pool, while incoming ETAs in get_upcoming_stock are keyed to each SKU and warehouse. Pools and warehouses do not map one to one, so comparing a SKU's earliest stockout to its earliest arrival is directionally sound but not warehouse-exact.

Fuse Inventory MCP FAQ

Is this just an AI chatbot?

No. It answers only from your validated Fuse data across every channel, so you get concrete answers about your real numbers instead of generic AI output.

How accurate are the answers?

As accurate as your Fuse data. Claude doesn't guess; every answer comes straight from Fuse, pulled live when you ask, so it matches what's in Fuse right now.

Can't I just export my data into Claude?

You can, but an export goes stale the moment you pull it. With Fuse connected, Claude reads your live numbers across every channel, so the answer reflects what's happening right now.

How is this different from Fuse's built-in reports?

Reports are prebuilt; this isn't. You ask in plain English and get custom breakdowns that don't exist as a report yet, so you're not stuck with only what's already been built.

Can it change our data?

No. This version is read-only, so Claude reads and answers but can't change anything in Fuse.

Is my data secure, and do you use it to train AI models?

Your data stays in Fuse and is read only when you ask, over an encrypted, permissioned connection. It's not used to train any AI model, and Claude applies its own data policies too.

Do I need to be a Fuse customer?

Yes. Answers come from your Fuse data, so you'll need your inventory in Fuse first. Read access is included with every Fuse plan.

How do I set it up? Do I need engineering?

You connect your Fuse account to Claude once, then start asking. It takes minutes, with no engineering or IT project.

Do I need a paid Claude plan?

A paid Claude plan is required to use a custom connector. The connection runs inside Claude, so whatever plan and usage limits you have there still apply.

What does it cost?

Read access is included with every Fuse plan.