Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Inventory Planner MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read Inventory Planner forecasts, replenishment and purchase orders; create draft purchase orders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http inventory-planner-mcp-by-usefulapi https://inventory-planner.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# inventoryplanner_list_variants, inventoryplanner_get_variant, inventoryplanner_list_variant_vendors and 8 more
Inventory Planner MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http inventory-planner-mcp-by-usefulapi https://inventory-planner.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List product variants with Inventory Planner's computed metrics (forecast, replenishment, days to sell out, lost revenue, lead time, review period and ~200 more). Always pass fields to pick the metrics you need (default: id,sku,lead_time,review_period,replenishment,oos,under_value; oos = forecasted days to sell out, under_value = forecasted lost revenue, replenishment = recommended order quantit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | string | no | — |
| filters | object | no | Filters, as {"<field>": value} or {"<field>_<operator>": value}. Operators: eq (default), eqi (case-insensitive), ne, gt, gte, lt, lte, range ("5-10"), match (regex), in (comma-separated). Example: {" |
| sort | object | no | Sort by one field, e.g. {"field": "under_value", "direction": "desc"}. |
| include_removed | boolean | no | — |
| page | integer | no | Page number, counting from 0 (default 0). Pass the previous reply's next_page. |
| limit | integer | no | Results per page, 1-1000 (default 25). |
One variant by its Inventory Planner id, with the metrics named in fields (default: id,sku,lead_time,review_period,replenishment,oos,under_value). GET /api/v1/variants/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| variant_id | string | yes | Inventory Planner id. |
| fields | string | no | — |
The vendors a variant can be ordered from, with cost_price, landing_cost_price, vendor_reference (vendor SKU), vendor_name, vendor_packaging (MOQ) and uom_ordering. GET /api/v1/variants/{id}/vendors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| variant_id | string | yes | Inventory Planner id. |
One vendor's terms for a variant: cost_price, landing_cost_price, vendor_reference, vendor_name, vendor_packaging (MOQ), uom_ordering. vendor_id is the vendor name in lowercase. GET /api/v1/variants/{id}/vendors/{vendor_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| variant_id | string | yes | Inventory Planner id. |
| vendor_id | string | yes | The vendor name in lowercase, as listed by inventoryplanner_list_variant_vendors. |
List stock orders: purchase orders, transfers and assembly orders (the type field is "po"/empty, "transfer" or "assembly"). Filter with filters, e.g. {"status": "OPEN", "vendor": "Acme", "expected_date_lt": "2026-11-01"}. Default fields: id,reference,status,type,vendor,warehouse,source,created_date,expected_date,received_date,currency,total,total_ordered,total_received. GET /api/v1/purchase-or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | string | no | — |
| filters | object | no | Filters, as {"<field>": value} or {"<field>_<operator>": value}. Operators: eq (default), eqi (case-insensitive), ne, gt, gte, lt, lte, range ("5-10"), match (regex), in (comma-separated). Example: {" |
| sort | object | no | Sort by one field, e.g. {"field": "under_value", "direction": "desc"}. |
| page | integer | no | Page number, counting from 0 (default 0). Pass the previous reply's next_page. |
| limit | integer | no | Results per page, 1-1000 (default 25). |
One purchase order, transfer or assembly order by id, with its header fields (reference, status, vendor, warehouse, dates, addresses, totals, notes) and line items. GET /api/v1/purchase-orders/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | string | yes | Inventory Planner id. |
| fields | string | no | — |
The line items of a purchase order: variant id, sku, title, ordered quantity (replenishment), received quantity and received_history, cost price, tax, discount and stock snapshots. GET /api/v1/purchase-orders/{id}/items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | string | yes | Inventory Planner id. |
| fields | string | no | — |
| page | integer | no | Page number, counting from 0 (default 0). Pass the previous reply's next_page. |
| limit | integer | no | Results per page, 1-1000 (default 25). |
Whether and how a purchase order was saved to connected systems (ERP, accounting): per connection the status (success, error, run, queued), save_po flag and the PO's id and reference there. Read-only. GET /api/v1/purchase-orders/{id}/connections.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | string | yes | Inventory Planner id. |
The stock updates a purchase order has computed: per warehouse (wh) the items with stock_before, delta and error. for_destination false reads the source warehouse of a transfer. Read-only: nothing is pushed. GET /api/v1/purchase-orders/{id}/stock-update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | string | yes | Inventory Planner id. |
| for_destination | boolean | no | true (default) = the destination warehouse; false = the source warehouse (transfers only). |
WRITE: create a purchase order with status "draft" in Inventory Planner (POST /api/v1/purchase-orders). A draft is only a plan inside Inventory Planner: it is NOT sent to the vendor, NOT saved to any connected system and moves no stock or money. Purchase orders only (no transfers or assembly orders). Each line item is a variant id plus the quantity to order (replenishment).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendor | string | yes | The vendor name, as it appears in Inventory Planner. |
| warehouse | string | yes | The destination warehouse, as it appears in Inventory Planner. |
| reference | string | no | Your PO reference. |
| expected_date | string | no | Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00. |
| currency | string | no | — |
| notes | string | no | — |
| items | array | yes | — |
WRITE: change the reference, expected date or notes of a purchase order that is still a draft (PATCH /api/v1/purchase-orders/{id}). The order is read first and refused unless its status is "draft". It never changes the status, sends the order, or touches line items or received quantities.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | string | yes | Inventory Planner id. |
| reference | string | no | — |
| expected_date | string | no | Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00. |
| notes | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Inventory Planner MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Inventory Planner MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.