InfiPlex MCP tools reference: all tools, what they do, and what they need
This is the complete list of tools the InfiPlex MCP server publishes to a connected AI assistant, taken directly from the server's tools/list response. For each tool: the exact name, whether it reads or writes, every input with its meaning, and the behaviors the tool description instructs the assistant to follow. Tool names, inputs, and gates on this page match the live server; when the server changes, this page changes with it.
18 Read ToolsListed on any key with the matching read scope. No confirmation step.
10 Previewed Write ToolsAnything that changes stock, prices, shipments, products, warehouses, or settings returns a preview and an argument-bound token first; the second call executes.
5 Direct Write ToolsInternal notes, the processed flag, order status, additional info fields, and bin locations execute on the first call. None of them touch a channel listing, quantity, or price.
Index
Every tool, by area
Seven areas mirror the InfiPlex REST API scopes (shown on each tool as the exact scope name a key needs). A key with only read scopes in an area sees only that area's read tools; uncheck an area entirely and its tools do not appear in the assistant's tool list at all.
Search the shop log by log type, text, and date range: why orders did not import, why tracking or inventory did not reach a channel, or everything logged for one order.
Orders
Orders: 10 tools
Find, read, annotate, ship, and close orders from every connected channel.
The step-by-step record of how each line of an order was routed to a warehouse.
orderidrequired InfiPlex internal order id.
One entry per order line, in processing order; process_events lists each step, and every Valid Warehouse Found event carries the zip rule check, default warehouse, and inventory adjustment as child_events.
quantity_to_process_at_warehouse is negative for units taken, 0 when none were.
An Overflow Inventory Quantity Adjustment event means no warehouse could fill the full quantity and the shortfall went to the default warehouse.
Written once when routing runs and never changed, so inventory figures are as of that moment. For current stock the assistant uses inventory_get.
Set one additional info field on an existing order.
orderidrequired InfiPlex internal order id.
additional_info_namerequired Field name, for example warehouse_being_picked_from or netsuite_class_id.
additional_info_valuerequired Field value.
These fields are consumed by Order Automation and ERP push logic, including every netsuite_custom_field_* name.
The name must exactly match one the account uses; an unknown name is stored but maps to nothing, so the assistant confirms the exact name rather than guessing.
Record a shipment against an order and submit tracking to the sales channel.
orderidrequired InfiPlex internal order id.
tracking_numberrequired Carrier tracking number.
carrier_namerequired Carrier as the customer wants it recorded, for example UPS, FedEx, USPS. Any value accepted.
package_itemsrequired Every line in this package with quantity, keyed by itemid from order_get (not SKU). Required even when the package holds the whole order. Optional lot_number and serial_number per line.
carrier_methodoptional Service level, for example Ground, 3rd Day.
save_items_as_qty_oneoptional Record each unit as its own line; needed for lot or serial tracked items.
set_ship_from_info + ship_from_*optional Override the ship-from address, or ship_from_warehouse_id to name the warehouse.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Externally visible to the customer and the marketplace, so it sits behind the confirmation preview.
Cancel an order, and send the cancellation to the marketplace where supported.
orderidrequired InfiPlex internal order id.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Externally visible and generally irreversible, so it sits behind the confirmation preview and the assistant confirms the specific order first.
Not for fixing a data mistake; that is order_update_status.
Create an order manually: offline, phone, wholesale, or test.
order_sourcerequired Channel to attribute the order to, for example Manual.
order_itemsrequired Lines with sku, quantity, price, and optional product_name, item_total, tax_total, discount_total.
ship_* / bill_*optional Full ship-to and bill-to address fields; ship_country is a two letter code.
email, phone, po_number, external_order_num, order_date, order_tagoptional Customer and reference fields.
ship_label, ship_price, ship_total, tax_total, discount_total, item_total, order_totaloptional Totals as decimal strings; order_total must reconcile.
additional_infooptional Key-value pairs consumed by automation and ERP push, for example netsuite_class_id.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Never used to re-enter an order that already exists on a channel; channel orders are ingested automatically.
Payment card details are never collected or sent through this tool.
Inventory
Inventory: 7 tools
Quantities per warehouse, change history, restock, bulk adjustments, bin locations.
Each entry shows when, the resulting total, whether it was a delta (quantity_added, negative for a decrease) or an absolute set (quantity_set), and a note on the cause such as an order number or product creation.
This is how the assistant explains why a SKU has the quantity it has.
warehouse_idoptional Warehouse the quantity applies to. Omit to apply account wide.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Propagates to every connected channel, so it sits behind the confirmation preview.
For more than a few SKUs the assistant is directed to inventory_set_bulk.
Change inventory for many SKUs in one call, mixing sets and deltas per row.
itemsrequired Rows of sku, warehouse_id, and exactly one of quantity_to_set or quantity_to_add. No fixed batch limit.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
One preview covers every row.
A row for a SKU the API cannot resolve returns null for that row rather than failing the call, so the assistant checks each row.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Propagates to connected channels and becomes visible to customers, so it sits behind the confirmation preview.
The assistant reads the current value with price_get first.
productsrequired Rows with sku and title required; optional price, upc, gtin, asin, isbn, barcode, image_url, ship_weight_oz, ship_length_inches, ship_width_inches, ship_height_inches. No fixed batch limit.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Only for SKUs that do not exist; the assistant checks pim_sku_get first because a duplicate SKU fragments inventory and pricing across channels.
warehouse_identifieroptional Short code, for example main.
street1, street2, city, state, region, zip, countryoptional Address.
use_zip_rulesoptional "0" or "1": whether zip based routing rules apply.
fulfill_ordoptional ASC or DESC, sort direction used when ordering this warehouse for fulfillment.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
A structural change that affects routing on every channel, so it sits behind the confirmation preview and the assistant checks warehouse_search first to avoid duplicates.
street1, street2, city, state, region, zip, countryoptional Address.
use_zip_rulesoptional "0" or "1".
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Address and routing changes affect allocation on every channel, so it sits behind the confirmation preview; the assistant reads warehouse_get first.
Settings
Settings: 3 tools
Discover, read, and, if the key allows, change account behavior.
setting_valuerequired New value, sent as a string.
confirmation_tokenoptional Omit on the first call to receive the preview and token. Pass the token on the second call to execute. Changing any other argument invalidates it.
Settings govern routing, inventory propagation, and channel behavior account wide, so it sits behind the confirmation preview and the assistant reads the current value first.
Refused unless the key has MCP Allow Setting Writes in addition to the setting-write scope.
Settings that start or stop live marketplace traffic (pulling orders, sending inventory or tracking) are additionally refused unless the key has MCP Allow Arming.
Credential settings cannot be written here at all.
Listed under the settings read scope because it only issues a link; it does not connect anything by itself. The account owner authorizes without needing an InfiPlex login.
Expires the same day. Anyone holding it can attach an account, so it goes only to the person who owns the marketplace account.
Shopify is split into push and pull; the assistant asks which direction if unclear.
Logs
Logs: 2 tools
The shop log is the record InfiPlex writes for every channel call (order pulls, tracking sends, inventory sends) and for system processes such as routing each order line to a warehouse. These two tools let the assistant read it, which turns "why did this not import" from a support ticket into a question.
List every shop log type on this instance, as an object mapping each log_type id to its label, for example 1026 Amazon Get Orders: Failed and 1027 Amazon Get Orders: Successful.
No inputs.
This is how the assistant finds the log_type id to pass to log_search. Most labels name the channel, the action, and whether it failed or succeeded.
Each channel also has an Any Log type, for example 1999 Amazon: Any Log, that matches every log for that channel.
Search the shop log by log type, text, and date range.
log_typeoptional Log type id from log_types_get, for example 1026 for Amazon Get Orders: Failed.
search_termoptional Text to match in the log body (log_message), for example an InfiPlex order id such as 104404. Does not match log type labels; use log_type for that.
start_date / end_dateoptional Written on or after / on or before. Format 2026-09-01 12:00:00 AM.
sortoptional Sort expression, for example log_time DESC.
just_countoptional 1 to return only the count.
limit / limit_startoptional Paging, maximum 100.
Each row carries log_time, log_type, log_type_message (the label), and log_message (the detail). log_message is returned decoded when it holds JSON, otherwise as text.
Log messages can be large, so the assistant is told to narrow by log_type and date range and keep limit small.
Typical use: find why orders did not import from a channel, why tracking or inventory did not reach a channel, or everything logged for one order, then pair with order_get or shop_setting_get to explain it.
The write flow
What a write looks like on the wire
Every previewed write tool follows the same two-call shape. The assistant never sees a way around it, because the token is issued by the server, bound to the exact arguments, and required for execution.
→ tools/call price_set {"sku":"HB-2201","price":24.99} ← PENDING Price for SKU HB-2201 will change from 27.50 to 24.99. This propagates to every connected sales channel. confirmation_token: 8f3a…c1e0 (assistant shows the preview; you say yes) → tools/call price_set {"sku":"HB-2201","price":24.99,"confirmation_token":"8f3a…c1e0"} ← OK price updated 27.50 -> 24.99
If the arguments on the second call differ in any way, the server rejects the token and returns a fresh preview. For inventory_set_bulk and products_create one preview covers the whole batch. The write safety guide shows the exact refusal messages for a missing scope, a missing setting-write opt-in, and a missing arming opt-in.
Scopes
Which key permissions expose which tools
The MCP server publishes a tool only when the key carries the REST scope that tool's endpoint requires. Read scopes expose the read tools in an area, write scopes expose the write tools. Two per-key flags sit on top of scopes: MCP Allow Setting Writes is required for shop_setting_set to execute at all, and MCP Allow Arming is required for it to touch any setting that starts or stops live marketplace traffic. Both default to off. A key with MCP Enabled but every write scope unchecked is a safe read-only agent key, which is the right starting point for most teams and the right thing to hand a client.
On connect the client calls initialize and then tools/list. The server answers with the tools the key is permitted to use, each with a name, a description, and a JSON schema for its inputs. The assistant reads those at runtime, so there is nothing to configure per tool and new tools appear automatically after the next connect.
The InfiPlex id is unique across every channel; marketplace numbers are not. When you give the assistant a marketplace number it runs order_search with text_search to resolve the id, then calls the tool you asked for. You do not have to know the internal id yourself.
For the ten previewed write tools, it can make the first call, which produces a preview and a token but changes nothing. To execute it must send the token, and every write tool's description instructs it to show the preview and wait for your go-ahead first. The gate is enforced by the server, not by the assistant's good behavior. The five direct write tools (notes, processed flag, status, additional info, bin locations) execute on the first call because none of them changes a quantity, price, or shipment; they are still limited by the key's write scopes.
order_tracking_create ships it: it records the package and submits tracking to the sales channel. order_processed only sets an internal flag that the order has been handled; nothing goes to the marketplace or the customer.
order_additional_info_create on an existing order and the additional_info array on order_create. Both write the key-value fields that the ERP push and Order Automation consume, such as netsuite_class_id, netsuite_location_id, or any netsuite_custom_field_* name. The field mapping guide lists them.
Yes. The server is a layer over the REST API, so each new endpoint can be published as a tool. The two log tools were added in September 2026; connection job tools are a possible next addition. This page is updated when tools go live.
Tool names, inputs, and behaviors are reproduced from the InfiPlex MCP server's tools/list response as of September 23, 2026. Claude is a trademark of Anthropic, PBC. ChatGPT and Codex are trademarks of OpenAI. Model Context Protocol is an open standard.
Our website uses cookies to help provide the best user experience. By continuing to use this site, you consent to the use of cookies as described in our Privacy Policy. OK
