Read delivery orders, quotes, customers, drivers, manifests, invoices and payment records. For courier operations teams with customer-authorized e-Courier API access. 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": {
"e-courier": {
"url": "https://e-courier.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"e-courier": {
"type": "http",
"url": "https://e-courier.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.
Read shipment status, pickup/delivery stops and tracking details without changing the courier job.
ecourier_get_order
Check price and availability for a customer with pickup/delivery addresses and optional parcel details. No job is created.
ecourier_quote_order
Inspect orders assigned to a driver and read the driver’s manifest.
ecourier_get_driver_orders ecourier_get_manifest
Find a customer record and its saved ship-to addresses. Only retrieve records authorized for your AI service.
ecourier_get_customer_by_code ecourier_list_customer_ship_tos
List invoices in a date range and inspect their fee lines. No billing or payment changes are exposed.
ecourier_list_invoices ecourier_get_invoice_fees
The login page asks for your e-Courier database name, API username and API password.
Optional: Assigned API URL.
The database name is the first part of your e-Courier address (https://yourcompany.e-courier.com). API access is enabled once per account by e-Courier support (submit a ticket if login fails). Use a dedicated e-Courier user for the API: its permissions decide what this server can do. Your username and password are stored encrypted in this connection and used only to log in to e-Courier on your behalf; they are not sent to the LLM. This initial release has 17 read-only tools, including delivery price quotes; creating or updating courier jobs is unavailable. Requested shipment/customer contacts, addresses, driver, manifest and invoice data reaches your chosen AI client and LLM provider. Only connect data you may process with that AI service. No automatic retries or operation replay; a refused cached session is cleared for the next explicit request. Disable the dedicated API user or change its password to stop new logins; already-issued vendor tokens can remain valid until revoked or expired (20 idle days). Usage/billing identity follows database and username; vendor charges are separate. The optional API URL supports the vendor-assigned standard or post-prefixed hostname for the same database.
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 e-Courier database name, API username and API password. 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 e-Courier connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
ecourier_get_order | read | Get order One delivery order with everything e-Courier holds: status (N new, A assigned, X deleted), customer, stops and their pickup/delivery times and POD names, pieces, jobs and drivers, fees, events and notifications. Give exactly one of order_number, order_id, auth (the customer's authorization code) or reference (a piece reference; add customer_code to narrow it). Signature images are not returned. GetJsonOrder. |
ecourier_get_order_fees | read | Get order fees The fee lines (what was charged for the delivery: base rate, fuel, waiting time and so on) of one order, by internal order id. GetOrderFees. |
ecourier_quote_order | read | Quote an order Price and availability for a delivery WITHOUT creating it: e-Courier applies the customer's rates to the stops and pieces and returns the order with the quoted amount. Supply a customer code, pickup/delivery stops and optional pieces. Nothing is saved and nobody is notified. QuoteOrder. |
ecourier_get_customer_by_code | read | Get customer by code A customer (billing account) by its e-Courier customer code: id, name and address. GetCustomerByCode. |
ecourier_get_customer | read | Get customer by id The full customer record by internal customer id: contact, address, credit status and limit, balance, billing settings. Card numbers and passwords are never returned. GetCustomerById. |
ecourier_find_customer_by_phone | read | Find customer by phone Look up a customer by phone number (useful when a caller rings in): id, name and address. GetCustomerInfoFromPhoneNumber. |
ecourier_list_customer_ship_tos | read | List customer ship-to addresses The saved ship-to (stop) addresses of a customer, by internal customer id, or one ship-to by its id. Give exactly one. GetCustomerShipTo. |
ecourier_list_drivers | read | List active drivers Every active driver: id, code, name and site. Optionally only one site (multi-site accounts). GetDrivers. |
ecourier_get_driver | read | Get driver Driver records with their vehicles and file names (never SSN or tax ids). With driver_id or driver_code one driver; with neither, every active and inactive driver. GetDriver. |
ecourier_get_driver_orders | read | Get a driver's current orders What a driver is carrying right now: the open orders on the driver's manifest (customer, pickup and delivery names, delivery zip, ready and due times), found by driver code or by the driver's phone number. Give exactly one. GetDriverInfoFromDriverCode / GetDriverInfoFromDriverPhone. |
ecourier_list_skills | read | List driver skills The master list of active driver skills (for example HAZMAT) with ids. GetSkills. |
ecourier_get_driver_skills | read | Get a driver's skills The skills assigned to one driver, by driver id or driver code (give exactly one). GetDriverSkills. |
ecourier_get_manifest | read | Get manifest One driver manifest (the route a driver runs for a day) with all its job stops: sequence, addresses, status, pieces and weight. GetManifest. |
ecourier_list_driver_manifests | read | List a driver's manifests The manifests of one driver between two dates, with their job stops. Default status filter is active (A). GetManifestsByDriver. |
ecourier_list_invoices | read | List invoices Invoices in an invoice date range (invoice_start_date and invoice_end_date are both required, at most 31 days apart: e-Courier rejects anything else). Optionally narrow by customer code and by a last-changed range. GetInvoice. |
ecourier_get_invoice_fees | read | Get invoice fees The fee lines of one invoice, by invoice id (the id from ecourier_list_invoices). GetInvoiceFees. |
ecourier_list_payments | read | List payments Customer payments received in a payment date range (payment_start_date and payment_end_date are both required, at most 10 days apart: e-Courier rejects anything else). Optionally narrow by customer code, check number or payment id. GetPayment. |
ecourier_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. | |
ecourier_request_feature | Request a missing feature Tell usefulapi that the user needs something the e-Courier 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. | |
ecourier_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on e-Courier (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. | |
ecourier_cancel_subscription | Cancel the Pro subscription Cancel the caller's e-Courier 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 ecourier_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Freeper e-Courier database/user | $0 | 50 tool calls / month |
| Proper e-Courier database/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 e-Courier 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].
Check a delivery order. Quote a delivery. Review a driver’s current work. Find customer shipping addresses. Review invoice details. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by e-Courier. The server calls the e-Courier API with your own e-Courier 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 e-Courier database name, API username and API password. 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 e-Courier database name, API username and API password. 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 e-Courier 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 e-Courier.
All 17 e-Courier tools are marked read-only.
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 e-Courier server only. Cancel any time: Pro then runs to the end of the paid period. Run ecourier_usage_status to see how many calls you used.
Ask the AI to run ecourier_upgrade: it returns a Stripe Checkout link. To cancel, run ecourier_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 ecourier_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.