Skip to main content

​
Overview

The Shippo MCP (Model Context Protocol) Server lets AI assistants and LLMs interact with the Shippo API in natural language: compare carrier rates, buy shipping labels, track packages, validate addresses, handle customs for international shipments, and process batches. To connect, point any MCP-compatible client at Shippo’s hosted server, https://mcp.shippo.com, and authorize with your Shippo account. Nothing to install, no API key to manage.

​
What is MCP?

Model Context Protocol (MCP) is an open protocol, developed by Anthropic, that standardizes how AI applications connect to external tools and data. The Shippo MCP Server implements it, making Shippo’s shipping capabilities available to MCP-compatible clients such as Claude, ChatGPT, and Cursor.

​
Features

The Shippo MCP Server provides access to core Shippo API functionality:
  • Validate addresses: verify and standardize shipping addresses
  • Create address records: store addresses for future use
  • Address book: manage sender and recipient addresses
  • Create shipments: set up shipments with origin, destination, and parcel details
  • Get rates: compare shipping rates across multiple carriers
  • Generate labels: purchase shipping labels for your shipments
  • Track packages: monitor shipment status and location
  • List carrier accounts: view all connected carrier accounts
  • Manage carriers: add or update carrier account settings
  • Multi-carrier support: works with USPS, UPS, FedEx, DHL, and more
  • Customs declarations: create customs documentation for international shipments
  • Customs items: define items for customs processing
  • Multi-country support: ship internationally with proper documentation
  • Batch operations: process multiple shipments at once
  • Pickups: schedule carrier pickups
  • Manifests: generate end-of-day manifests
  • Webhooks: set up event notifications

​
Connect to the hosted server

Connect any MCP-compatible client to https://mcp.shippo.com. The first time you use it, your client opens a Shippo sign-in window. Authorize it once and you are connected.
There is no API key to configure for the hosted server: authentication is handled by signing in to your Shippo account. The hosted server operates against your live Shippo account; see Live account and charges.
Quick add (one click). If your client supports it, add Shippo in one click; you will still complete the Shippo sign-in on first use. Otherwise, follow the per-client steps below.

Cursor

VS Code

LM Studio

Goose

Claude and ChatGPT don’t offer a one-click add; use their steps below.

​
Claude (claude.ai and Claude Desktop)

  1. Open Customize and go to Connectors.
  2. Click +, then Add custom connector.
  3. Name it Shippo and paste the server URL https://mcp.shippo.com. Leave the advanced OAuth fields blank.
  4. Click Add, then complete the Shippo sign-in when prompted.
Team and Enterprise admins can make Shippo available to everyone: in Organization settings → Connectors, choose Add → Custom → Web, enter the URL, and add it. Members then connect it under Customize → Connectors and complete the Shippo sign-in individually on first use.

​
Claude Code

Then run /mcp, select the Shippo server, and complete the browser sign-in to authorize.

​
ChatGPT

ChatGPT connects to the hosted Shippo server as a custom connector (some versions call it an “app”). This works on free and paid plans. On Business and Enterprise, a workspace admin may first need to allow custom connectors.
  1. Open Settings and go to the connectors area. Depending on your plan and ChatGPT version this is labeled Apps, Connectors, or Plugins; some versions ask you to turn on a developer or advanced option before custom connectors appear.
  2. Add a new connector, name it Shippo, set the server URL to https://mcp.shippo.com, and set Authentication to OAuth.
  3. Acknowledge the “I understand and want to continue” prompt and create the connector. ChatGPT opens the Shippo sign-in window; complete it to authorize.
To use Shippo in a conversation, open the + menu in the message box, choose More, and select Shippo. Then ask in natural language, for example: “What are the cheapest rates to ship a 2 lb box from San Francisco to Austin, TX?”

​
Cursor

Add a remote MCP server in .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
Cursor supports OAuth for remote MCP servers. After saving the config, open Settings → Tools & Integrations, find Shippo, and complete the sign-in prompt.

​
Other MCP clients

Any client that supports a remote MCP server over HTTP with OAuth can connect: use the URL https://mcp.shippo.com and complete the Shippo authorization when prompted.

​
Skills and knowledge for AI assistants

The connector gives your assistant Shippo’s tools, the actions above. To also give it Shippo know-how, so it picks the right service, formats addresses and customs data correctly, and follows shipping best practices, add Shippo’s skills and reference knowledge as context. Shippo maintains ready-to-use skills and assistant integrations in the open-source goshippo/ai repository:
  • Claude: install the Shippo plugin, which bundles this MCP connector together with Shippo’s skills.
    • Claude Code: run /plugin marketplace add goshippo/ai, then /plugin install shippo@shippo.
    • Claude apps (claude.ai and Desktop): download the Shippo plugin from the latest release and add it in the Plugins UI. A Team or Enterprise admin can install it for everyone under Organization settings → Plugins.
  • ChatGPT, Cursor, and other assistants: download the Shippo knowledge pack and add it as context (a Project file, a custom GPT’s knowledge, or an attached document), then connect the MCP server above so the assistant can act on it.
Knowledge plus the connector is the full experience: the assistant understands how to ship and can actually do it. Knowledge on its own lets it advise you and draft API requests; add the connector when you want it to fetch live rates, buy labels, or track packages.

​
Usage examples

Once connected, you can interact with Shippo through natural language:

​
Create a shipping label

​
Track a package

​
Validate an address

​
Compare shipping rates

Actions that buy a label or otherwise change your account ask for confirmation before they run.

​
Live account and charges

The hosted MCP server authorizes your live Shippo account, so:
  • Read operations are free: comparing rates and validating addresses do not charge your account, and tracking packages purchased through Shippo is free too. Tracking a package purchased outside Shippo is a billable action.
  • Buying a label is a live action that charges your account. Write actions such as purchasing a label ask for confirmation before they run.
The hosted MCP server has no separate test mode. If you need test labels and mock tracking for development, use a test API key (shippo_test_) directly against the Shippo API, see Testing the Shippo API. Test and live data (and object IDs) are completely separate.

​
Security

Requests are sent to Shippo’s hosted MCP server over HTTPS, authenticated by your per-user Shippo authorization, and forwarded to the Shippo API on your behalf. There is no API key to store and no local process in the path. To disconnect, remove the Shippo connector from your client’s settings and revoke access from your Shippo account if desired.

​
Troubleshooting

  • Shippo doesn’t appear in the connector or tool picker: confirm the server was added and the Shippo sign-in completed. Reopen your client’s connector settings to check its status.
  • You’re asked to sign in again: the authorization session expired. Re-authorize from the connector settings (in Claude Code, run /mcp).
  • The sign-in window is blocked: allow pop-ups for your client and retry.

​
Resources

​
Support

For questions or issues:

​
About Shippo

Connect with multiple carriers, get discounted shipping labels, track parcels, and much more with just one integration. You can use your own carrier accounts or take advantage of Shippo’s discounted rates. Shippo simplifies carrier integrations, rate shopping, tracking, and the entire shipping workflow.
Last modified on July 16, 2026