pleasefixai/shippo
Shipping rates, labels, tracking and address checks for 40+ carriers, through Shippo.
Validate, parse, and standardize shipping addresses via the Shippo API
Process bulk shipments from CSV files, create and purchase batch labels, and generate end-of-day manifests via the Shippo API
Purchase domestic and international shipping labels, handle customs declarations, return labels, and void/refund labels via the Shippo API
Compare multi-carrier shipping rates, find cheapest/fastest options, and get shipping recommendations via the Shippo API
Analyze shipping costs, compare carriers, optimize package dimensions, and review historical shipping spend via the Shippo API
Guides Shippo integration decisions, choosing between Rates at Checkout vs. full Shipments+Transactions vs. Batch processing, address validation strategy (v1 vs v2 fields), domestic vs international workflows (customs declarations, incoterms), label format selection, and webhook setup. Use when planning, building, or reviewing any Shippo integration, including building checkout flows, bulk fulfillment pipelines, address validation, label generation, package tracking, customs handling, or webhook subscriptions.
Generate a complete, auto-classified, ready-to-paste Shippo support ticket for a single shipment or label. Use when a support agent or customer needs to escalate a shipping issue (lost/delayed package, unused-label refund, billing/rate adjustment, address exception, customs hold, carrier-account, or tracking-webhook problem). Given a tracking number + carrier, a transaction (label) ID, or a shipment ID, it classifies the issue, runs the right read-only Shippo MCP lookups, computes the triage timeline, and emits both a copy-paste support message and a routing-tagged JSON block so the ticket lands in the right pipeline first time.
Track packages across carriers, view tracking history, and set up tracking webhooks via the Shippo API
Guide for Shippo API version changes, webhook payload versioning, and how the hosted MCP server handles updates. Use when reasoning about backward compatibility, handling new fields in webhook payloads or API responses, troubleshooting OAuth/version-mismatch errors against the hosted MCP, or auditing an existing Shippo integration before a change.