e-Courier MCP by usefulapi
Connect
- Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste
https://e-courier.usefulapi.io/mcp.
- Claude Code:
claude mcp add --transport http e-courier https://e-courier.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 e-Courier credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/e-courier/
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 ecourier_upgrade (it returns a Stripe Checkout link). Cancel any time with ecourier_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running ecourier_upgrade before then undoes the cancel. Or write to [email protected].
License
MIT.
API access and data
Customer API enablement is arranged through e-Courier support. The default API host is database.e-courier.com; the optional assigned URL also supports post.database.e-courier.com for that database. Arbitrary hosts or endpoint paths are not accepted.
Requested shipment/customer contacts, addresses, driver, manifest and financial records pass to your chosen AI client and LLM provider. Only connect data you may process with that service. Credentials are masked from results/diagnostics; card fields and base64 images/signatures are removed. Price quotes do not create courier jobs.
No operation is automatically retried. A refused cached token is cleared for the next explicit call. Disable the API user or change its password to stop new logins; already-issued tokens can remain valid until revoked or expired (20 idle days). Usage and billing follow database and normalized username. Independent integration; no vendor approval or endorsement claimed.