e-Courier MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 网店与支付

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://e-courier.usefulapi.io/mcp

claude mcp add --transport http e-courier https://e-courier.usefulapi.io/mcp

{
  "mcpServers": {
    "e-courier": {
      "url": "https://e-courier.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "e-courier": {
      "type": "http",
      "url": "https://e-courier.usefulapi.io/mcp"
    }
  }
}

https://e-courier.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• ecourier_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 aut

• ecourier_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

  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. Quot

• ecourier_get_customer_by_code

  A customer (billing account) by its e-Courier customer code: id, name and address. GetCustomerByCode.

• ecourier_get_customer

  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

  Look up a customer by phone number (useful when a caller rings in): id, name and address. GetCustomerInfoFromPhoneNumber.

• ecourier_list_customer_ship_tos

  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

  Every active driver: id, code, name and site. Optionally only one site (multi-site accounts). GetDrivers.

• ecourier_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

  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 / GetDriverInfoFromDriverPho

• ecourier_list_skills

  The master list of active driver skills (for example HAZMAT) with ids. GetSkills.

• ecourier_get_driver_skills

  The skills assigned to one driver, by driver id or driver code (give exactly one). GetDriverSkills.

• ecourier_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

  The manifests of one driver between two dates, with their job stops. Default status filter is active (A). GetManifestsByDriver.

• ecourier_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

  The fee lines of one invoice, by invoice id (the id from ecourier_list_invoices). GetInvoiceFees.

• ecourier_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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 11 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 17 个工具描述，未发现针对 AI 的隐藏指令

与“网店与支付”中的其他服务器比较i

• 星标数多于此分类中其他 1743 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1743 个服务器的 96% 更新
• 基础检查结果等于或优于此分类中其他 1743 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{