shippo-mcp

by Shippo

SSE

275 downloads

Not rated

GitHub Website

About

Multi-carrier shipping for AI agents: compare rates, buy labels, track packages, validate addresses

Details

Author: Shippo
Downloads: 275
Transport: SSE
Categories: Other, Finance

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name shippo-mcp

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

From the repository

{
  "mcpServers": {
    "remote-server": {
      "type": "http",
      "url": "https://mcp.shippo.com"
    }
  }
}

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "shippo-mcp": {
            "remote-server": {
                "type": "http",
                "url": "https://mcp.shippo.com"
            }
        }
    }
}

McpServers

{
    "remote-server": {
        "type": "http",
        "url": "https://mcp.shippo.com"
    }
}

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

- 9 Agent Skills: Workflow knowledge for AI assistants covering rate shopping, address validation, label purchase (with customs), package tracking, batch shipping, shipping cost analysis, support-ticket drafting, integration best practices, and SDK/API upgrades. Authored once and distributed across multiple AI surfaces.
- Claude Code Plugin(providers/claude/plugin/): Install via--plugin-diror the plugin marketplace (/plugin marketplace add goshippo/ai).
- OpenAI Codex Plugin(providers/codex/plugin/): Install via the Codex plugin marketplace; bundles the skills plus the OAuth MCP server.
- ClawHub Skill(providers/clawhub/skills/shippo/): Install viaopenclaw skills install @shippo/shippo.
- Claude apps (claude.ai / Desktop / Cowork): The whole plugin is packaged as a single upload-ready ZIP (shippo-plugin.zip), attached to every GitHub Release. One upload provisions all the skills.
- Knowledge Pack (ChatGPT and other chat assistants)(providers/knowledge-pack/shippo-knowledge-pack.md): A single consolidated markdown for assistants that donotloadSKILL.mdfolders. A user drops it into a chat, a Custom GPT's Knowledge, or a Project as context. It provides the shipping knowledge; live actions still use the hosted MCP connector.

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

rate-shopping/ ├── SKILL.md # required: metadata + instructions └── README.md # optional: human-facing orientation

Agents load skills byprogressive disclosurein three stages:
- Discovery: at startup, the agent loads only each skill'snameanddescription, just enough to know when it might be relevant.
- Activation: when a user prompt matches a skill's description, the agent loads the fullSKILL.mdbody into context.
- Execution: the agent follows the instructions, optionally loading referenced files (shippo/references/.md) as it works.

Agent Skillsis an open standard originally developed by Anthropic. The sameSKILL.mdworks in Claude Code, Cursor, OpenAI Codex, GitHub Copilot, VS Code, and 30+ other agents.

In this repo, the 9 skills underskills/are thecanonical source. They're propagated intoproviders/claude/plugin/skills/andproviders/codex/plugin/skills/(1:1 mirrors),providers/clawhub/skills/shippo/(consolidated digest), andproviders/knowledge-pack/shippo-knowledge-pack.md(a single upload-ready knowledge pack for ChatGPT and other non-skill-loading assistants) automatically by the sync scripts.

Shippo hosts a remote MCP server with per-user OAuth. Each user authorizes once through Shippo, there is no API key to copy. The Claude Code and OpenAI Codex plugins point at this endpoint and trigger the sign-in on first use.

For per-tool semantics and usage, see the Shippo MCP server docs.

Building on OpenAI? See Using the Shippo MCP from the OpenAI Responses API / Agents SDKfor the developer config (no submission required).

The 9 skills in this repo are organized bymode of engagement: what the user is doing, not by product surface. The AI assistant matches the user's intent to one of three modes, then loads the right skill.

Maintain, "upgrade or migrate"

A user who already knows the workflow they need ("buy a label", "track this package") jumps straight to a Do skill. A user starting fresh ("I'm building a checkout flow with shipping, where do I start?") hits the Decide skill, which routes them to the right Do skill. Maintenance gets its own skill so production-readiness questions don't compete with workflow content.

The 9 skills lean on11 shared reference docsunderskills/shippo/references/(carriers, customs, CSV format, error reference, etc.). Skills load references on demand, the AI doesn't pull all 11 into context, just the ones a given workflow needs.

git clone https://github.com/goshippo/ai.git claude --plugin-dir ./ai/providers/claude/plugin

/plugin marketplace add goshippo/ai /plugin install shippo@shippo

Skills are namespaced under/shippo:: invoke directly with/shippo:rate-shopping,/shippo:label-purchase,/shippo:tracking, etc., or just describe what you're doing in natural language.

Codex installs the Shippo plugin (skills + OAuth MCP) from this repo's plugin marketplace:

codex plugin marketplace add goshippo/ai codex plugin add shippo@shippo # install the "shippo" plugin codex mcp login shippo # authorize the remote MCP over OAuth

See providers/codex/plugin/for details. (To pull just the skill content without the plugin, Codex'sskill-installercan also install a singleproviders/codex/plugin/skills/<name>directory.)

(Published as@shippo/shippoon the ClawHub registry.)

Claude apps (claude.ai / Desktop / Cowork)

The Claude apps load the plugin as a single ZIP.shippo-plugin.zip(the whole plugin: manifest, OAuth MCP config, and all skills) is attached to every GitHub Release. Download it and add it via the app's Plugins UI. A Team/Enterprise admin can provision it org-wide in one step: Organization settings → Plugins → uploadshippo-plugin.zip→ set "Installed by default" (or assign to a group), and all skills become available to members. (Code execution must be enabled in Organization settings.)

To build the ZIP locally:npm run build:app-plugin(output indist/app-plugin/).

You'll need a Shippo account. Getting rates and validating addresses incur no charge; purchasing a label uses Shippo's discounted carrier rates and charges your account. The Claude Code and Codex plugins authorize per-user via OAuth on first use, so there's no API key to copy.

This plugin bundles two things, with a deliberate division of labor between them:

- Skills(this repo): Cross-toolworkflow narrative: routing decisions (checkout vs single label vs batch), UX gates ("ask before purchasing a live-mode label"), CSV ingestion, validation sequencing, test/live mode discipline, response-handling rules. Loaded on activation when the user's request matches a skill's description.
- MCP server(docs): Per-toolsemantics: tool name, parameters, return shape, single-call constraints. Each tool description is terse, one verb phrase, one tool. Workflow guidance is intentionally NOT duplicated here.

The skills teach the assistanthowto ship across multiple API calls. The MCP server gives the assistant theper-call*truth about each tool. The two surfaces are disjoint by design, same precedent Stripe uses (tersemcp.stripe.comtool descriptions, rich stripe/agentsskills): so raw MCP users get accurate per-tool semantics and skill-installed users additionally get the workflow narrative, without contradiction.

- skills/: canonical skill content (9 skills + 11 shared references).Edit here; everything else flows from here.
- providers/claude/plugin/: Claude Code plugin distribution. 1:1 mirror of canonical viascripts/sync.js.
- providers/codex/plugin/: OpenAI Codex plugin.skills/is a 1:1 mirror of canonical viascripts/sync.js;.codex-plugin/plugin.json+.mcp.json(hand-authored) carry the manifest and the OAuth MCP wiring. Cataloged from.agents/plugins/marketplace.jsonat the repo root.
- providers/clawhub/skills/shippo/: ClawHub bundle distribution. TheSKILL.mdis auto-generated fromSKILL.md.template(hand-curated framing) + canonical skill bodies viascripts/compose-clawhub-digest.js. References are auto-synced viascripts/build-clawhub-bundle.js.
- dist/app-plugin/: the singleshippo-plugin.zipfor the Claude apps, built fromproviders/claude/plugin/byscripts/build-app-plugin.js(not committed; produced on demand and on release).
- scripts/: sync, compose, and build helpers.

# 1. Edit canonical content vim skills/<skill-name>/SKILL.md # (or skills/shippo/references/<name>.md, or providers/clawhub/skills/shippo/SKILL.md.template # if you're changing ClawHub-only framing) # 2. Sync + verify (one command) npm test # 3. Commit canonical edits AND synced output together git add -A && git commit -m "..."

npm testruns all the sync steps (Claude Code + Codex mirrors, ClawHub digest compose, ClawHub references sync) and verifies the result is internally consistent. CI runs the same command. Nonpm installneeded, the repo has no third-party dependencies, just scripts.

- Claude Code:runclaude --plugin-dir ./providers/claude/pluginfrom the repo root to launch Claude Code with the local plugin loaded. Edits toskills/<name>/SKILL.mdare reflected immediately. Skills are namespaced under/shippo:(e.g.,/shippo:rate-shopping).
- ClawHub digest:afternpm testruns, the rendered output lives atproviders/clawhub/skills/shippo/SKILL.md: read it directly to see what ClawHub-installed users will get. There's no local-server preview today.

See CONTRIBUTING.mdfor the full authoring discipline, including the version-bump rules and the cross-reference phrasing rule for skill content.

Transaction-complete hotel booking over MCP — 300K+ properties, real hotel confirmation numbers, loyalty points, secure checkout. Hotels are merchant of record. Builders set their own booking fee via Stripe Connect. Built on proven distribution infrastructure.

An MCP server for AI video generation. MCP server for AI video generation. Lets Claude, ChatGPT, OpenClaw , Hermes & other agents create AI videos and publish them to YouTube, TikTok, Instagram etc..

Institutional research and manager diligence reports on hedge funds, venture capital and private equity managers. Summary of filings, personnel changes, media screening and social signals delivered to you in minutes.

ALTER - identity infrastructure for the AI economy

D2C eCommerce fulfillment platform: manage orders, inventory, shipments, campaigns, and billing via AI agents

Apigene MCP Gateway is the runtime layer that connects AI agents to APIs and MCP servers via Model Context Protocol.

MCP to interface with multiple blockchains, staking, DeFi, swap, bridging, wallet management, DCA, Limit Orders, Coin Lookup, Tracking and more.

MCP server for Bitnovo Pay integration with AI agents. Provides cryptocurrency payment capabilities through Bitnovo Pay API. Features include payment creation, status checking, QR code generation, and webhook management with support for multiple tunnel providers (ngrok, zrok, manual).

Shop for gift cards, esims, phone topups. Pay with cards and crypto.

You built it, now get users! GoToMarket MCP server

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

Maintain, "upgrade or migrate"

Claude apps (claude.ai / Desktop / Cowork)

Install

More like this

Sequential Thinking

Filesystem

EverArt

Google Drive

Reactive Resume

FastMCP v2 🚀