Connect ShipStation to Claude Code

Have Claude create labels and mark orders shipped in ShipStation. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect ShipStation to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect ShipStation, you add a ShipStation MCP server: a small hosted service that exposes ShipStation's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own ShipStation account. No API keys pasted into config files.

claude mcp add --transport http shipstation https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in ShipStation once connected?

Full read-write ShipStation access lets Claude create a shipping label for an order, apply tags to route or flag it, hold or mark an order shipped, and add tracking so the source store updates, once you approve. The fulfillment steps that used to mean opening the dashboard happen from where you already work.

Create a shipping label for an order once carrier and service are confirmed
Apply or remove tags to route, flag, or batch orders
Mark an order shipped and push tracking back to the source store
Put an order on hold or release it from hold
Update an order's shipping address or requested service before fulfillment
Add a note to an order for the fulfillment team

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same ShipStation access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the ShipStation API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when ShipStation changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build ShipStation connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same ShipStation connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own ShipStation account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on ShipStation's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to ShipStation?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the ShipStation account it signs in with. Revoking access is one click in ShipStation.

More on the ShipStation connector

ShipStation connector for claude.ai Wix + Claude Code Ecwid + Claude Code Etsy + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us