← All integrations

Shippo MCP server

57 operations1 webhook

Multi-carrier shipping with Shippo - quote rates across carriers, buy and refund labels, track parcels, declare customs and manage pickup paperwork.

Try Shippo with your agent

Connect Shippo, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Shippo on my account, then run one read-only example and show me the result.

Runs once, when you ask

Shippo tools and triggers

Tools are what your agent can do in Shippo through Corsair's MCP server. Triggers are the Shippo events a routine can start from.

Parcel Templates

  • CreateWrite

    Save a reusable parcel template, optionally based on a carrier template token

    parcelTemplates.create

  • DeleteDestructive

    Delete one of the account’s parcel templates. Anything still referring to its token stops resolving

    parcelTemplates.delete

  • GetRead-only

    Read one of the account’s parcel templates

    parcelTemplates.get

  • Get CarrierRead-only

    Read one carrier parcel template by its token

    parcelTemplates.getCarrier

  • ListRead-only

    List the account’s own parcel templates

    parcelTemplates.list

  • List CarrierRead-only

    List the carrier’s predefined parcel templates, whose tokens can be reused instead of dimensions

    parcelTemplates.listCarrier

  • UpdateWrite

    Change one of the account’s parcel templates

    parcelTemplates.update

Carrier Accounts

  • CreateWrite

    Connect the caller’s own carrier account, with that carrier’s credential set

    carrierAccounts.create

  • GetRead-only

    Read one carrier account

    carrierAccounts.get

  • ListRead-only

    List the carrier accounts on the account. Every call that asks for rates depends on one of these being active

    carrierAccounts.list

  • RegisterWrite

    Enrol a Shippo-supplied carrier account rather than the caller’s own

    carrierAccounts.register

  • Registration StatusRead-only

    Check whether a carrier has approved the account for live rates

    carrierAccounts.registrationStatus

Connect Shippo to Claude, ChatGPT or Cursor

  1. 1

    Connect Shippo in Corsair

    Add your Shippo API key once in Corsair. Corsair stores the credential encrypted and makes the Shippo API calls for your agent, so it never goes into a prompt or a config file. Connect Shippo

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Shippo. On a ChatGPT personal plan, connect Shippo here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Shippo's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/shippo, add the Shippo plugin, and connect with an API key. Then call methods like corsair.shippo.api.addresses.create() from your app. Corsair verifies webhooks, and keeps each tenant isolated.

Yes. Shippo requires an API key from your Shippo account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Shippo, GitHub, Notion, Stripe, and the rest. Trigger Shippo from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for multi-carrier shipping with Shippo - quote rates across carriers, buy and refund labels, track parcels, declare customs and manage pickup paperwork. Common builds include sync jobs, admin tooling, and agents that call Shippo APIs from your backend. Webhook handlers react to Shippo events and fan out to Slack, email, or other plugins in the same tenant.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Shippo API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/shippo in the open repo. When Shippo ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Shippo data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Shippo data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Shippo on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Shippo operations. You can change a link's mode at hub.corsair.dev/me.