Status 

Zonos runs MCP servers internally today — these power AI-assisted workflows for Zonos engineering and support and are gated behind staff-only permissions, so they are not reachable through the customer Graph.

A customer-facing MCP server, scoped per-merchant via the same credentialToken model as the Zonos Graph, is the next step. This page tracks what that surface will do and how to connect once it ships. It is not yet generally available.

What is MCP? 

The Model Context Protocol is an open standard that lets AI assistants and agents (Claude, OpenAI's agents, Cursor, and others) connect to external systems through a uniform interface. A Zonos MCP server will let those agents query the Zonos Graph and trigger workflows on a merchant's behalf — for example, classifying a SKU, looking up a landed-cost quote, or fetching the status of an order — without each integrator writing custom code.

What the customer-facing MCP server will support 

Initial scope is read-heavy, with selective write operations:

• Look up products, orders, shipments, declarations, and landed-cost quotes.
• Run classifications and retrieve HS codes for a SKU.
• Request a landed-cost calculation for a draft order.
• Inspect webhook deliveries and replay events.

Write-side operations (creating orders, submitting shipments) are gated behind explicit user confirmation in the agent UI.

Authentication 

The MCP server will authenticate via the same credential token model as the Zonos Graph. Agents present a per-merchant token to the server; the server scopes every operation to that merchant.

Get notified when it ships 

If you want early access, contact us. Existing Zonos GraphQL integrations can use the TypeScript SDK or PHP SDK today.