Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Sortly 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
Search inventory items and folders, low-stock alerts, jobs and purchase orders, and update stock.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sortly-mcp https://sortly.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# sortly_list_items, sortly_get_item, sortly_search_items and 17 more
Sortly 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 sortly-mcp https://sortly.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.
20 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 items and folders, newest first. By default the root level; pass folder_id for a folder's direct contents, plus include_subfolders for everything nested under it. Paginated via meta.next_page_url / total_pages. Sortly: GET /api/v1/items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder_id | integer | no | Only the direct contents of this folder. Omit for the root level. |
| include_subfolders | boolean | no | With folder_id: also return everything nested beneath it. Default false. |
| include | array | no | Nested associations to embed: custom_attributes and/or photos. |
| per_page | integer | no | Page size, 1-1000 (default 10). |
| page | integer | no | Page number, starting at 1. |
Fetch a single item or folder by numeric id: quantity, min_quantity, price, tags, sid, barcodes, and optionally custom field values and photos. Sortly: GET /api/v1/items/{item_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | integer | yes | The item's or folder's numeric id. |
| include | array | no | Nested associations to embed: custom_attributes and/or photos. |
Search items and folders by name, optionally limited to items or folders and scoped to specific folders. Read-only despite being a POST. Paginated: send the same arguments with the next page number. Sortly: POST /api/v1/items/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Name (or part of it) to search for. |
| type | string | no | Limit to items or folders. Default all. |
| folder_ids | array | no | Only search in these folders. |
| include_subfolders | boolean | no | With folder_ids: also search folders nested under them. Default false. |
| sort | string | no | Sort by name, ascending or descending. |
| include | array | no | Nested associations to embed: custom_attributes and/or photos. |
| per_page | integer | no | Page size, 1-100 (default 100). |
| page | integer | no | Page number, starting at 1. |
List items and folders changed since a Unix timestamp — the incremental-sync read ('what moved since yesterday?'). Without updated_since it behaves like sortly_list_items. Sortly: GET /api/v1/items/recent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| updated_since | integer | no | Unix epoch seconds; only items updated after this. |
| folder_id | integer | no | Only the direct contents of this folder. Omit for the root level. |
| include_subfolders | boolean | no | With folder_id: also return everything nested beneath it. Default false. |
| include | array | no | Nested associations to embed: custom_attributes and/or photos. |
| per_page | integer | no | Page size, 1-100 (default 10). |
| page | integer | no | Page number, starting at 1. |
List the account's custom fields (id, name, type, applies_to). Call this before writing custom_attribute_values to get the right custom_attribute_id. Sortly: GET /api/v1/custom_fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| per_page | integer | no | Page size (default 10). |
| page | integer | no | Page number, starting at 1. |
List the units of measure available to the account (unit_name, unit_type, scale) — the values measured_quantity and purchase-order lines expect. Sortly: GET /api/v1/units.
No parameter schema on file.
List stock (Quantity) and date (DateReminder) alerts, with is_fired showing which have already triggered — the quick way to find low-stock items. Sortly: GET /api/v1/alerts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| per_page | integer | no | Page size (default 10). |
| page | integer | no | Page number, starting at 1. |
List jobs (work orders that pull stock out), most recently updated first, filterable by name prefix and status. Paginated via meta.pagination.has_next. Sortly: GET /api/v1/jobs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Jobs whose name starts with this (case-insensitive). |
| status | array | no | Only these statuses. Default all. |
| sort_by | string | no | Sort field. Default updated_at. |
| sort_direction | string | no | Default desc. |
| per_page | integer | no | Page size, 1-100 (default 20). |
| page | integer | no | Page number, starting at 1. |
Fetch a single job: status, folder_id (where its pulled items sit), dates, notes, custom field values and the version needed for updates. Sortly: GET /api/v1/jobs/{job_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | The job's id. |
List purchase orders, most recently updated first, filterable by PO number and status. The list leaves out notes, terms, sub_total and line_items — use sortly_get_purchase_order for those. Needs Purchase Orders on the plan (else 402). Sortly: GET /api/v1/purchase_orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_number | string | no | POs whose number contains this. |
| status | array | no | Only these statuses. Default all. |
| sort_by | string | no | Sort field. Default updated_at. |
| sort_direction | string | no | Default desc. |
| per_page | integer | no | Page size, 1-100 (default 20). |
| page | integer | no | Page number, starting at 1. |
Fetch a single purchase order with its line_items (quantity vs received_quantity), vendor, addresses, charges, totals and version. Sortly: GET /api/v1/purchase_orders/{purchase_order_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | integer | yes | The purchase order's id. |
Report the most recent receive against a purchase order: pending / completed / failed, with the line ids received, pending and failed (and why). Returns 404 until something has been received. Sortly: GET /api/v1/purchase_orders/{purchase_order_id}/receive/status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | integer | yes | The purchase order's id. |
Create a trackable item (type item) or a folder (type folder), optionally inside a folder via parent_id, with quantity, price, tags, custom fields, barcodes and a measured quantity. WRITE. Sortly: POST /api/v1/items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name, max 190 characters. |
| type | string | yes | item = trackable stock; folder = a container. |
| parent_id | no | Folder to create it in. Omit/null = root. | |
| price | number/null | no | Unit price. |
| quantity | number/null | no | How many you have. |
| min_quantity | number/null | no | Minimum level; a Quantity alert can fire when stock reaches it. |
| notes | string/null | no | Free-text notes. |
| tags | array | no | Tag names, e.g. ["furniture", "used"]. |
| custom_attribute_values | array | no | Custom field values. Look up ids with sortly_list_custom_fields first. |
| label_url | string/null | no | Value encoded in the primary QR code / barcode. |
| label_url_type | no | Symbology of the primary code. | |
| label_url_extra | string/null | no | Value encoded in the secondary code. |
| label_url_extra_type | no | Symbology of the secondary code. | |
| photo_ids | array | no | Ids of photos already in the account to attach. |
| measured_quantity | object | no | For items measured in something other than units. |
Change fields on an existing item or folder — e.g. set a new quantity after a stock count, rename it, or relocate a folder via parent_id. Only the fields you pass change; pass null to clear a nullable field. Sending tags or custom_attribute_values replaces them. WRITE. Sortly: PUT /api/v1/items/{item_id} (returns 204).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | integer | yes | The item's or folder's numeric id. |
| name | string | no | New name. |
| parent_id | no | Move into this folder (null = root). To move PART of an item's stock use sortly_move_item. | |
| price | number/null | no | Unit price. |
| quantity | number/null | no | How many you have. |
| min_quantity | number/null | no | Minimum level; a Quantity alert can fire when stock reaches it. |
| notes | string/null | no | Free-text notes. |
| tags | array | no | Tag names, e.g. ["furniture", "used"]. |
| custom_attribute_values | array | no | Custom field values. Look up ids with sortly_list_custom_fields first. |
| label_url | string/null | no | Value encoded in the primary QR code / barcode. |
| label_url_type | no | Symbology of the primary code. | |
| label_url_extra | string/null | no | Value encoded in the secondary code. |
| label_url_extra_type | no | Symbology of the secondary code. | |
| photo_ids | array | no | Ids of photos already in the account to attach. |
| measured_quantity | object | no | New measured amount for a measured item. |
Move some or all of an item's quantity to another folder (items only — relocate a folder with sortly_update_item parent_id). A partial move splits off a new item with the same sid; a full move relocates the item; a matching item at the destination is merged, and the returned id is the destination's. Undo by moving it back. WRITE. Sortly: POST /api/v1/items/{item_id}/move.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | integer | yes | The item's numeric id. |
| quantity | number | yes | How much to move. |
| folder_id | integer | no | Destination folder. Omit to move to the root level. |
| leave_zero_quantity | boolean | no | Keep a zero-quantity record in the source folder. Default false. |
Create a stock alert on an item (type Quantity, e.g. threshold_method quantity_less_than with threshold_value 5, or less_than_or_equal_to_min_quantity), or a DateReminder on a datetime custom field (custom_attribute_id + before/after/same_day + threshold_interval). WRITE. Sortly: POST /api/v1/alerts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | integer | yes | The item the alert watches. |
| type | string | yes | Quantity = stock threshold; DateReminder = date custom field. |
| threshold_method | string | yes | What triggers it: a quantity_* method for Quantity, before/after/same_day for DateReminder. |
| threshold_value | number | no | The number compared against (or the interval count). |
| threshold_interval | string | no | Required for DateReminder; omit for Quantity. |
| custom_attribute_id | integer | no | For DateReminder: the datetime custom field to watch. |
| recipient_groups | array | no | Who is notified: owners, admins, members, limited, or a custom role name. Default owners. |
Create a job (and its job folder) in not_started status. Name must be unique in the company. Then use sortly_pull_items_into_job to record the stock it uses. WRITE. Sortly: POST /api/v1/jobs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Unique job name, max 190 characters. |
| notes | string | no | Job notes, max 4000 characters. |
| start_date | string | no | YYYY-MM-DD. |
| end_date | string | no | YYYY-MM-DD. |
| external_job_link | string | no | Link to the job in another system. |
| subfolders | array | no | Subfolder names to create, up to 25. |
| custom_field_values | array | no | Up to 2 job custom field values. |
Move quantities of existing items (from any folders) into a job's folder — how usage on a job is recorded. Up to 100 items per call; items are processed independently, so ALWAYS check data.errors (a partial failure still returns 200). Undo with sortly_return_items_from_job. Returns 403 on a completed job. WRITE. Sortly: POST /api/v1/jobs/{job_id}/items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | The job's id. |
| items | array | yes | 1-100 items. |
| notes | string | no | Optional note kept in each item's history. |
Move items off a job's folder back into inventory (destination_folder_id, or All Items if omitted). Up to 100 per call; check data.errors — items are processed one by one. WRITE. Sortly: POST /api/v1/jobs/{job_id}/items/return.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | The job's id. |
| items | array | yes | 1-100 items. |
| notes | string | no | Optional note recorded in the item's history. |
Create a purchase order in draft status (no stock or ordering happens until it is moved on in Sortly). Sortly computes amounts, sub_total and total from the lines; omit purchase_order_number to have one generated. Needs Purchase Orders on the plan (else 402). WRITE. Sortly: POST /api/v1/purchase_orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| currency_code | string | yes | ISO 4217 code, e.g. USD. |
| purchase_order_number | string | no | Unique PO number, max 20 chars. Omit to auto-generate. |
| vendor | object | no | The vendor, captured on the PO. |
| ship_to | object | no | Shipping address. |
| bill_to | object | no | Billing address. |
| notes | string | no | — |
| terms | string | no | e.g. Net 30. |
| charges | object | no | Order-level charges; each defaults to 0. |
| expected_delivery_date | string | no | ISO 8601 timestamp, e.g. 2026-08-20T00:00:00Z. |
| line_items | array | no | Up to 100 lines. |
- 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 Sortly 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.11.1.
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 Sortly 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.