Remote endpoint
How to connect
Add the URLhttps://api.zippendo.com/mcp to your client as a custom MCP connector. The client runs
the OAuth login and consent flow in your browser automatically — nothing to install, no token to
paste, and tokens refresh on their own. See Connect your agent for step-by-step
setup per client.
What you can do
Once connected, the agent can work across your Zippendo data — bounded by the scopes you approve:- Shipments — create, split, send, and track shipments; fetch labels and documents.
- Orders — read synced channel orders and turn them into shipments.
- Carriers — list connected carriers, products, and drop-off points.
- Addresses & shipping rules — read and manage sender addresses and rules.
- Automations, webhooks, printers, and more — anything exposed by the public API.
Requirements
- A Zippendo account with access to at least one organization.
- An MCP-capable client. Remote OAuth connectors are the easiest path; some plans (for example, ChatGPT and Claude Desktop custom connectors) gate this behind paid tiers — see Connect your agent.
How it works
The remote endpoint is a stateless Streamable HTTP MCP server built into the Zippendo API. It exposes the same tools that power Zippy, the in-app assistant. Every tool call runs through the real API — the same authentication, scope checks, billing limits, and validation as any other request. The agent acts as you, only within the organization and scopes you approve, and never with admin privileges.Connect your agent
Step-by-step setup for Claude, Cursor, VS Code, ChatGPT, and more.
Authentication
How the OAuth flow works, choosing an org, and narrowing scopes.
Tools & scopes
Which tools map to which permissions, with example prompts.