Shipcloud MCP by usefulapi
Connect
- Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste
https://shipcloud.usefulapi.io/mcp.
- Claude Code:
claude mcp add --transport http shipcloud https://shipcloud.usefulapi.io/mcp, then run /mcp to log in.
- VS Code: Add to VS Code.
- Cursor and other clients: add the URL as a remote MCP server:
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Shipcloud credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/shipcloud/
Tools
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
Pricing
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with shipcloud_upgrade (it returns a Stripe Checkout link). Cancel any time with shipcloud_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running shipcloud_upgrade before then undoes the cancel. Or write to [email protected].
License
MIT
Account access and data
Connect only your own customer-controlled key under your authorization and processing instructions. Find the key under your account email → API Key. Sandbox keys produce test labels; live keys can incur real carrier charges. Vendor plans, carrier eligibility and charges are separate. This is an independent customer-authorized connection, with no partner approval claimed.
The key is encrypted. Requested sender/recipient addresses, orders and tracking information reach your connected AI client and LLM provider. Connect only data you are authorized to process there. Revoke the key in Shipcloud to stop access; disconnect UsefulAPI to stop this connection. Billing follows customer number, normally across sandbox/live keys and key rotation.
Buying a label, deleting a shipment/cancelling a label and requesting a carrier pickup require explicit confirmation. Pickups may be charged and cannot be cancelled through these tools. Prepared shipments have no label or label charge. An optional notification email causes Shipcloud tracking emails to that address. Notes and results explain uncertain outcomes; no operation is automatically replayed.
Reference lookups and same-instance guards reduce duplicate label purchases but are not atomic across Worker instances. Serialize purchases for each reference. A timeout can occur before a slow carrier completes; check Shipcloud before repeating a purchase. A valid create id and HTTPS label URL are required before reporting a label purchase; deletion requires the documented204 acknowledgement.
All22tools were checked against current vendor documentation and local mocks. No real customer shipping data, labels, pickups or charges were tested.