Shippo MCP Server
Connect Shippo to your AI agents with the Shippo MCP server.
Updated
What is Shippo MCP?
The Shippo MCP server is a Model Context Protocol server that connects Shippo to AI agents and assistants as a set of tools. With it connected, an agent can work with Shippo (multi-carrier shipping — rates, labels and tracking) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses a bearer token, so you point your client at the server URL, authorize once, and the Shippo tools become available to the model.
Connect the Shippo MCP server
Connect Shippo MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Shippo MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (a bearer token) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Shippo tool to confirm the connection is live.
Connect Shippo MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Shippo
Provide the Shippo MCP server URL or command and complete authentication.
- 3
Test
Reference Shippo from chat to confirm Cursor can reach the tools.
Using Shippo MCP with Gamut
On Gamut, the Shippo MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Shippo and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Shippo MCP server?
It is a Model Context Protocol server that exposes Shippo to AI agents as tools so they can work with it (multi-carrier shipping — rates, labels and tracking).
How do I connect the Shippo MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Shippo MCP server URL and complete authentication (a bearer token). See the official documentation for the exact URL and scopes.
Can I use Shippo MCP with Gamut?
Yes — Gamut supports the Shippo MCP server, so your agents can use it as a tool in automated, triggered workflows.