Apilo MCP by usefulapi

它能帮你做什么

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

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

安装

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

你需要

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

你用的是哪个应用？

https://apilo.usefulapi.io/mcp

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

{
  "mcpServers": {
    "apilo": {
      "url": "https://apilo.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "apilo": {
      "type": "http",
      "url": "https://apilo.usefulapi.io/mcp"
    }
  }
}

https://apilo.usefulapi.io/mcp

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

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

它能做什么

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

• apilo_whoami

  The Apilo API key (application) this connection uses: client id, name and the date it is valid to. GET /rest/api/whoami/.

• apilo_get_map

  Apilo's id lookup tables, each a list of { id, key, name, description }: `status` (order statuses, for apilo_list_orders and apilo_update_order_status), `payment` (payment types), `carrier`, `carrier_account`, `platform` (sales channels and their accounts), `tag`, `document` (doc

• apilo_list_orders

  List or search orders (all connected marketplaces and shops), with items, customer address and totals. Filter by date, status, payment, sales channel, carrier, email or phone. Status, payment, carrier and platform ids come from apilo_get_map. Page with limit/offset (reply has tot

• apilo_get_order

  One order in full: status, payment, items (SKU, EAN, price, quantity), customer/delivery/invoice addresses, payments, notes, discounts, carrier and sales channel. GET /rest/api/orders/{id}/.

• apilo_list_order_notes

  The notes of an order (internal notes and customer messages), with type 1 = customer message, 2 = internal note. GET /rest/api/orders/{id}/note/.

• apilo_list_order_documents

  The documents attached to an order (invoices, receipts, labels). GET /rest/api/orders/{id}/documents/.

• apilo_list_order_shipments

  The shipments created for an order (Apilo id and carrier's id). GET /rest/api/orders/{id}/shipment/.

• apilo_get_shipment

  One shipment of an order with its details. GET /rest/api/orders/{id}/shipment/{shipment}/.

• apilo_list_shipment_tracking

  Tracking status of shipments (status, status date and description, received date and days in transit), filtered by carrier account, post date, received date or status. Page with limit/offset (reply has totalCount and next_offset). GET /rest/api/shipping/shipment/tracking/.

• apilo_list_products

  List warehouse products with SKU, EAN, name, stock quantity, prices, tax and location. Filter by id, SKU, name, EAN or status. GET /rest/api/warehouse/product/.

• apilo_get_product

  One warehouse product by Apilo id. GET /rest/api/warehouse/product/{id}/.

• apilo_list_categories

  Product categories with id, name and parent ids. GET /rest/api/warehouse/category/.

• apilo_list_locations

  Warehouse locations (shelves, bins) with id, name and code. GET /rest/api/warehouse/location/.

• apilo_list_finance_documents

  Accounting documents (invoices, receipts, corrections) with number, amounts, currency and dates. Filter by type and invoice date. GET /rest/api/finance/documents/.

• apilo_update_order_status

  WRITE: set an order's status (id from apilo_get_map status). Apilo may run its own automations on a status change (emails, marketplace updates, shipping). Setting the current status changes nothing. PUT /rest/api/orders/{id}/status/.

• apilo_add_order_note

  WRITE: add an INTERNAL note to an order (never a message to the customer). Not idempotent: calling twice adds two notes. POST /rest/api/orders/{id}/note/.

• apilo_set_product_stock

  WRITE: set the stock quantity of one warehouse product to an absolute number (it replaces the current quantity, so read it with apilo_get_product first if unsure). Apilo may push the new quantity to connected marketplaces. PATCH /rest/api/warehouse/product/.

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 10 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

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

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

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

替代选择

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

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

作者的 README

{