List stores, search and get orders, update order status and cancel orders in ShippingEasy. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the ShippingEasy connector, then ask in plain words. The AI picks the tools.
For e-commerce merchants who ship orders through ShippingEasy.
Search orders across all stores by last update time, status, order number or tag. Then get one order to read its recipients and line items.
List the stores with their store API keys. Then search the orders of one store by its key, with the same filters.
Find the store API key in the store list. Then set the status of one order by its external order identifier. The new status shows in ShippingEasy.
Changes dataRead the order by its id first. Then cancel it in ShippingEasy, so the order is not shipped from there.
Changes dataThe login page asks for your API key and API secret.
Find both in ShippingEasy → Settings → API Credentials. Your keys are used only to sign calls to ShippingEasy on your behalf; they are never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"shippingeasy": {
"url": "https://shippingeasy.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"shippingeasy": {
"type": "http",
"url": "https://shippingeasy.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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: the login page asks for your API key and API secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this ShippingEasy server only. Ask your AI to run shippingeasy_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with shippingeasy_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with shippingeasy_upgrade before then undoes the cancel. Or write to [email protected].
shippingeasy_list_storesshippingeasy_search_ordersshippingeasy_search_store_ordersshippingeasy_get_ordershippingeasy_update_order_statusshippingeasy_cancel_ordershippingeasy_usage_statusshippingeasy_request_featureshippingeasy_upgradeshippingeasy_cancel_subscriptionReview orders that changed recently. List the orders of one store. Update the status of an order. Cancel an order shipped elsewhere. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by ShippingEasy. The server calls the ShippingEasy API with your own ShippingEasy access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your API key and API secret. See Before you connect for where to find them.
No. 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: the login page asks for your API key and API secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the ShippingEasy API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in ShippingEasy.
Yes, if you approve it. 2 of the 6 ShippingEasy tools can create or change data. The other 4 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this ShippingEasy server only. Cancel any time: your paid plan then runs to the end of the paid period. Run shippingeasy_usage_status to see how many calls you used.
Ask the AI to run shippingeasy_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run shippingeasy_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with shippingeasy_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.