PO Pilot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PO_PILOT_LICENSE_KEY | No | License key from the Self-Hosted Lifetime Kit, which unlocks unlimited SKUs and live Shopify Admin GraphQL integration. | |
| SHOPIFY_ACCESS_TOKEN | No | A read-only Shopify Admin API access token (shpat_...) with read_products, read_inventory, and read_orders scopes. Optional; kept in memory only and never logged or written to disk. | |
| SHOPIFY_STORE_DOMAIN | No | Your Shopify store domain (e.g. your-store.myshopify.com). Optional; used together with SHOPIFY_ACCESS_TOKEN to enable live read-only Shopify Admin GraphQL mode. The server runs in demo/CSV mode with zero credentials. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_replenishment_planA | Replaces Shopify Stocky's retired forecasting brain. Computes margin-weighted ABC classes, stockout-adjusted daily sales velocity, demand + lead-time variability safety stock (SS = Z * sqrt(LTsigma_d^2 + d^2sigma_LT^2)), reorder points, inventory position (On-Hand + On-Order - Committed - Backorders), days of cover, and carton-rounded order recommendations. Free Local Sandbox processes up to 25 SKUs per call; Pro/License unlocks unlimited SKUs and Live Shopify sync. |
| build_supplier_purchase_ordersA | Turns SKU demand signals into ready-to-send Purchase Orders grouped by vendor. Enforces carton/case-pack multiples, per-SKU MOQs, supplier-level minimum units/USD thresholds (topping up A-class SKUs first), US import tariff + freight landed unit costs with margin-erosion alerts, and optional Open-to-Buy ( |
| reconcile_po_three_way_matchA | Deterministic Finance Ops 3-way match engine for wholesalers and Shopify merchants. Cross-examines approved Purchase Order lines, warehouse dock receiving counts (good vs damaged units), and billed supplier invoice lines to catch silent unit-price creep, short-shipments billed in full, unapproved surcharges, and freight cap overages. Emits ready-to-import QuickBooks Online ( |
| migrate_stocky_csv_snapshotA | Shopify Stocky shut down on August 31, 2026 and never provided a Supplier Directory export. Paste a historical Stocky Purchase Orders CSV export (or pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| monday_morning_reorder_run | Runs a complete stockout-adjusted reorder audit and builds MOQ-compliant Shopify Draft PO CSVs. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| shopify-po-csv-spec | Column contract and post-Stocky workflow instructions for importing POs into Shopify Admin. |
TDQS
Scored across 4 tools
The four tools target mostly distinct stages of the purchasing workflow: forecasting, PO construction, reconciliation, and Stocky migration. The main possible confusion is between calculate_replenishment_plan and build_supplier_purchase_orders, since one produces order recommendations and the other turns demand into vendor POs, but the descriptions clarify the handoff.
All tool names use consistent snake_case with a clear verb-first pattern: calculate_, build_, reconcile_, and migrate_. The names are predictable and readable despite being fairly long.
Four tools is well-scoped for a focused PO/inventory planning server. Each tool represents a meaningful workflow stage rather than a marginal convenience operation.
The surface covers the core forecast-to-PO-to-reconciliation lifecycle and includes a migration path from Stocky. Minor gaps remain around explicit supplier directory maintenance, receiving/invoice ingestion, and PO status lifecycle operations, but agents can work around these by supplying data as tool inputs.