Read orders, shipments and tracking events; create orders and rate quotes in Webshipper. For merchants and fulfilment teams who ship parcels with carriers through Webshipper. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"webshipper": {
"url": "https://webshipper.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"webshipper": {
"type": "http",
"url": "https://webshipper.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List the orders by status, channel or creation date. Open one order to read its delivery address and lines.
webshipper_list_orders webshipper_get_order
List the shipments of an order, then list the tracking events of one shipment to see each carrier scan.
webshipper_list_shipments webshipper_get_shipment webshipper_list_tracking_events
List the carriers connected to the account, and the order channels that send orders to Webshipper.
webshipper_list_carriers webshipper_list_order_channels
Create an order with a delivery address and lines. Use a new ext_ref each time, then find the order by that reference. It can start shipping work.
Changes data · webshipper_create_order webshipper_list_orders
The login page asks for your Webshipper account name and Webshipper access token.
The account name is the part before .webshipper.io in your Webshipper address. Create the token in Webshipper under Settings → Access and tokens. It is used only to call the Webshipper API on your behalf and to derive a private account id; it is never shown to anyone.
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 Webshipper account name and Webshipper access token. 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.
Turn on the Webshipper connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
webshipper_list_orders | read | List orders List orders in the Webshipper account, 30 per page. Filter by status, your own reference, channel, destination country, free text or creation date. Use page to read more. Webshipper API: GET /orders. |
webshipper_get_order | read | Get an order Get one order by id, with its status, delivery and sender addresses, and order lines. Webshipper API: GET /orders/{id}. |
webshipper_list_shipments | read | List shipments List shipments (parcels booked with a carrier), 30 per page. Filter by order, carrier, status, tracking number, reference, destination country, return flag, free text or creation date. Webshipper API: GET /shipments. |
webshipper_get_shipment | read | Get a shipment Get one shipment by id: carrier, service, tracking number, status and addresses. Webshipper API: GET /shipments/{id}. |
webshipper_list_tracking_events | read | List tracking events List carrier tracking events (scans and status changes), 30 per page. Pass shipment_id to read one shipment's history. Webshipper API: GET /tracking_events. |
webshipper_list_carriers | read | List carriers List the carriers connected to the Webshipper account (ids, names, carrier types). Use the id in shipment filters. Webshipper API: GET /carriers. |
webshipper_list_order_channels | read | List order channels List the order channels (shops or marketplaces that send orders to Webshipper), 30 per page. Use the id in order filters. Webshipper API: GET /order_channels. |
webshipper_create_order | write | Create an order Create a new order in Webshipper with a delivery address and order lines. Use a new ext_ref for every order: Webshipper's response may not return the new order id, so find the order later with webshipper_list_orders and ext_ref. Creating an order can start shipping work in the account. Webshipper API: POST /orders. |
webshipper_create_rate_quote | write | Get rate quotes Ask Webshipper which shipping rates apply to one parcel sent to an address. Returns the quotes it finds. Webshipper API: POST /rate_quotes. |
webshipper_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
webshipper_request_feature | Request a missing feature Tell usefulapi that the user needs something the Webshipper tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
webshipper_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Webshipper (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
webshipper_cancel_subscription | Cancel the Pro subscription Cancel the caller's Webshipper Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run webshipper_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Webshipper server only. Subscribe with webshipper_upgrade (it returns a Stripe Checkout link). Cancel any time with webshipper_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running webshipper_upgrade before then undoes the cancel. Or write to [email protected].
Find orders waiting for dispatch. Track a parcel. Check the connected carriers and channels. Create a shipping order from a sale. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Webshipper. The server calls the Webshipper API with your own Webshipper 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 Webshipper account name and Webshipper access token. 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 Webshipper account name and Webshipper access token. 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 Webshipper 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 Webshipper.
Yes, if you approve it. 2 of the 9 Webshipper tools can create or change data. The other 7 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 unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Webshipper server only. Cancel any time: Pro then runs to the end of the paid period. Run webshipper_usage_status to see how many calls you used.
Ask the AI to run webshipper_upgrade: it returns a Stripe Checkout link. To cancel, run webshipper_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with webshipper_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.