Skip to main content
The MCP server exposes Zippendo’s operations as tools, generated automatically from the public API. Your agent sees a tool for each operation it’s allowed to run — filtered by the scopes you approve.

​
How tools map to scopes

Every tool has a required scope derived from the resource and action it touches:
  • Reading data needs a read:* scope — e.g. listing shipments needs read:shipments.
  • Changing data needs the matching write:* scope — e.g. creating a shipment needs write:shipments.
Scopes are hierarchical, so you can grant broadly or narrowly:
  • write:all implies every read and write scope.
  • read:all implies every read scope.
  • write:<resource> implies read:<resource> (e.g. write:shipments includes read:shipments).
An agent granted only read:shipments sees the shipment read tools (list, get, tracking, documents) but none of the tools that create, send, or delete shipments.

​
Scope reference

Grant the narrowest set that gets the job done. read:all plus write:shipments is a good default for an assistant that reports on everything but only acts on shipments.

​
Example prompts

Once connected, talk to your agent in plain language. It picks the right tools and asks Zippendo:
  • “How many shipments are still pending, and which carriers are they on?”
  • “Create a shipment for order #10421 with PostNord and give me the tracking number.”
  • “Split the shipment for order #10388 into two parcels and send both.”
  • “Which orders from the last 24 hours don’t have a shipment yet?”
  • “Track shipment shp_8f3kd9 and tell me if it’s delayed.”
  • “Add a shipping rule that routes orders over 10 kg to GLS.”

​
Documentation & SDK tools

Beyond the action tools above, the MCP server also lets an agent read Zippendo’s documentation so it can help you build an integration — in your language. These tools need no scope and are available to every connected agent. The agent is steered to prefer the official SDK for your language, and to fall back to the raw OpenAPI spec only when no SDK exists for it. Content is pulled live from zippendo.com/docs and the SDK repositories, so it’s always current. Try prompts like:
  • “Using the Zippendo Python SDK, write a script that creates a shipment for an order and prints the tracking number.”
  • “How do I authenticate to the Zippendo API in Go? Show me the SDK setup.”
  • “I’m on PHP — generate a webhook handler that verifies the signature and reacts to shipment.delivered.”

​
Safety model

Acts as you

Tool calls run with your identity, only within the scopes you approved.

Org-isolated

A connection is bound to one organization; it can’t read or change another org’s data.

No admin access

MCP callers can never perform Zippendo admin (superAdmin) actions.

Full validation

Every call runs the same auth, billing-limit, and schema validation as the app.
Some sensitive operations are intentionally excluded from the tool catalog and won’t be available to any agent, regardless of scope.

​
The same tools power Zippy

The MCP server shares its tool catalog with Zippy, Zippendo’s in-app assistant. The difference is only the surface: Zippy runs inside the app, while MCP lets your own agent use the same capabilities. Both enforce identical scopes, org isolation, and validation.

Connect your agent

Ready to set this up? Follow the per-client setup guide.