Shippo MCP Server

Multi-carrier shipping for AI agents: compare rates, buy labels, track packages, validate addresses. Exposed over MCP by the shippo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This repo is the one-stop shop for building AI-powered shipping integrations with Shippo.

A skill is a folder containing a SKILL.md file, YAML frontmatter (at minimum: name and description) plus markdown instructions that tell an AI assistant how to perform a specific task. Skills can also bundle reference docs, scripts, and templates.

Its toolset

Everything the assistant can do here goes through one of these:

• URL — Transport
• Skill — What it does
• shippo-best-practices — Decision-router for Shippo integrations, which API to use, test vs. live mode discipline, response handling, critical rules
• address-validation — Validate, parse, and standardize US and international addresses
• rate-shopping — Compare rates across USPS, UPS, FedEx, DHL, and 30+ carriers
• label-purchase — Purchase domestic and international shipping labels with customs handling
• tracking — Track packages across carriers with status history, substatus codes, and webhooks
• batch-shipping — Process CSV files of shipments and generate labels in bulk
• shipping-analysis — Analyze costs, optimize package dimensions, compare carriers, review historical spend
• shippo-support-ticket — Build an auto-classified, routing-tagged support ticket (human + JSON) for a single shipment or label; read-only, for Shippo support agents
• upgrade-shippo — Guide for upgrading SDK versions, MCP server updates, breaking-change migration
• ClawHub — (Published as @shippo/shippo on the ClawHub registry.)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Shippo's toolset — URL, Skill, shippo-best-practices and 9 more — is a fair guide to whether it matches your workflow. It is maintained by com.shippo; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Shippo.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the shippo mcp server does with a few real requests.