Starshipit

@starshipit get shipping rates for a 2kg parcel going to Auckland, New Zealand, with dimensions 30×20×15cm

Based on your parcel specs (2kg, 30×20×15cm to Auckland), Starshipit returned four carrier options: NZ Post CourierPost Overnight ($12.50 ETA 1 day), NZ Post ParcelPost ($8.20 ETA 2-3 days), DHL Express ($45.00 ETA next day by 10:30am), and Aramex Standard ($9.80 ETA 2-4 days). All prices exclude GST. CourierPost and Aramex offer tracking; ParcelPost is signature-on-delivery only. This is an illustrative example—actual rates depend on your Starshipit account's negotiated carrier contracts and the destination postcode.

Rate quotes require valid destination details and realistic package dimensions. Starshipit pulls rates from your account's enabled carriers, so results vary by which shipping services you've configured. No API key scopes are consumed by quoting—it's a read-only operation with no side effects.

@starshipit create a shipping label for order #SO-4429 using NZ Post CourierPost, then show me the tracking number

Label created for order SO-4429. Starshipit assigned tracking number 9NZAA012345678901 via NZ Post CourierPost and generated a 4×6 thermal label PDF. The order moved to 'Printed' status in your Starshipit dashboard. You can now hand the parcel to your courier or schedule a pickup. This is an illustrative example—the real operation is irreversible and immediately commits the shipment to your carrier account, potentially triggering billing.

Creating a label is a write operation that cannot be undone. It consumes a shipment from your carrier account and may incur costs even if you never dispatch the parcel. Starshipit requires the order to exist and have a valid destination. Always verify order details before running this prompt in production.

@starshipit pull tracking events for all shipments created in the last 48 hours and summarize which ones are delayed or stuck in customs

Starshipit returned tracking data for 23 shipments from the past two days. Of those, two are flagged: Tracking 9NZAA012345678902 (order SO-4431) has been 'In Transit' at Auckland depot for 36 hours with no scan updates, and tracking DHLE1234567890 (order SO-4438) shows a customs hold in Sydney since yesterday morning. The remaining 21 shipments are progressing normally—18 are out for delivery today, 3 were delivered yesterday. This is an illustrative summary; actual event granularity depends on each carrier's tracking API and update frequency.

Tracking synthesis combines Starshipit's Get Tracking tool with AI reasoning to surface exceptions. Starshipit's tracking data freshness depends on carrier APIs—some update hourly, others every few hours. This example assumes you have API access to historical shipments; restricted accounts may only see recent orders.

When Starshipit makes sense for small-batch shipping

A two-person direct-to-consumer brand shipping 40-80 orders a week from a home warehouse hits the sweet spot for this MCP. The Create Order and Create Shipping Label tools let you script label generation from a spreadsheet or Airtable base without logging into Starshipit's web UI for every batch. The Get Shipping Rates tool helps you quote customers accurately before they check out. The threshold: if you're shipping fewer than 10 orders a week, the API_KEY setup overhead probably isn't worth it—just use Starshipit's dashboard. If you're over 200 orders a week, you need a proper WMS integration, not an MCP. For the mid-volume DTC operator who wants to automate label printing during morning packing sessions, this is the right call.

Why the tracking tool works for support teams

A four-person customer support team fielding 'where's my order' inquiries can use the Get Tracking tool to pull shipment status without switching to Starshipit or the carrier's site. The MCP returns carrier events in a structured format, so you can paste tracking updates into Intercom or Zendesk tickets in seconds. The limitation: Starshipit only surfaces what the carrier reports, so if the carrier's tracking is stale or incomplete, this won't magically fix it. If your support volume is under 20 tracking lookups a day, the manual dashboard is faster. Above that, scripting the lookup with this MCP saves 10-15 minutes per shift. The buying call is simple: if your team is already in Switchy for other workflows, adding tracking lookup here beats alt-tabbing to three different carrier portals.

When manifest creation needs a second set of eyes

A three-person warehouse team closing out daily shipments with Create Manifest hits a real problem: manifesting is irreversible, and Starshipit's warning is buried in the tool description. If you manifest the wrong batch, you can't undo it without calling the carrier. The MCP's explicit shipment-list input helps, but the risk is still there. The scenario where this works: you're already using Switchy to review the day's shipments in a shared context, and one person double-checks the manifest list before another person runs the tool. If your warehouse is solo or you're manifesting more than twice a day, the web UI's visual confirmation is safer. For small teams doing end-of-day reconciliation together, the MCP adds a collaboration layer that the dashboard doesn't offer.