Twice Commerce MCP by usefulapi

它能帮你做什么

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

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

安装

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

你需要

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

你用的是哪个应用？

https://twice-commerce.usefulapi.io/mcp

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

{
  "mcpServers": {
    "twice-commerce": {
      "url": "https://twice-commerce.usefulapi.io/mcp"
    }
  }
}

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

https://twice-commerce.usefulapi.io/mcp

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

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

它能做什么

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

• twicecommerce_get_merchant

  Get the merchant account: name, country, currency, timezone, languages, plan and enabled features. Good first call. Admin API: GET /v1/admin/merchant.

• twicecommerce_list_service_locations

  List pickup and return locations (service locations). Use the ids to filter orders and stock items. Admin API: GET /v1/admin/service-locations/.

• twicecommerce_list_taxes

  List the tax rates set up for the merchant. Admin API: GET /v1/admin/taxes/.

• twicecommerce_list_tags

  List tags used on inventory, catalog, customers or orders. Admin API: GET /v1/admin/tags.

• twicecommerce_list_orders

  List orders with status, customers, line items, totals and dates. The API does not paginate this list, so the result is cut to `limit` rows (newest as returned by the API); the full count is in totalCount. Narrow it with location_ids. Admin API: GET /v1/admin/orders.

• twicecommerce_get_order

  Get one order by id: status, customers, line items, stock items, comments, totals and pricing. Admin API: GET /v1/admin/orders/{orderId}.

• twicecommerce_get_order_payments

  List the payment transactions of one order (needs a key with the Payments area). Admin API: GET /v1/admin/orders/{orderId}/payments.

• twicecommerce_get_order_invoices

  List the invoices of one order, optionally with the upcoming scheduled subscription invoices (needs a key with the Payments area). Admin API: GET /v1/admin/orders/{orderId}/invoices.

• twicecommerce_list_customers

  List customers, with an optional text search over name and email and paging. Admin API: GET /v1/admin/customers.

• twicecommerce_get_customer

  Get one customer by id: contact details, addresses and type. Admin API: GET /v1/admin/customers/{customerId}.

• twicecommerce_get_customer_orders

  List the orders of one customer. Admin API: GET /v1/admin/customers/{customerId}/orders.

• twicecommerce_list_catalog_items

  List catalog items (the listings customers rent, buy or subscribe to), with an optional name search and paging. Admin API: GET /v1/admin/catalog/.

• twicecommerce_get_catalog_item

  Get one catalog item by id: name, status, variants, rules and pricing links. Admin API: GET /v1/admin/catalog/{id}.

• twicecommerce_check_availability

  Check whether one catalog item can be booked for a date-time window (before you create an order). Dates are ISO 8601 date-times in UTC, for example 2026-11-05T09:00:00Z. Admin API: GET /v1/admin/availability/{catalogItemId}/period.

• twicecommerce_list_discount_codes

  List discount codes with usage and validity, with paging. Admin API: GET /v1/admin/discount-codes.

• twicecommerce_list_stock_items

  List stock items (the physical units, called articles in the API), with paging. Narrow by location ids. Admin API: GET /v1/admin/articles/.

• twicecommerce_get_stock_item

  Get one stock item by id: SKU, condition, quantity, location and status. Admin API: GET /v1/admin/articles/{id}.

• twicecommerce_list_skus

  List SKUs (the product definitions that stock items belong to), with paging. Admin API: GET /v1/admin/skus.

• twicecommerce_get_sku

  Get one SKU by id. Admin API: GET /v1/admin/skus/{skuId}.

• twicecommerce_add_order_comment

  WRITE: add a comment to an order (needs a key with Write access to Order details). Each call adds a new comment; do not repeat a call that succeeded. Admin API: POST /v1/admin/orders/{orderId}/comments.

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 12 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

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

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

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

替代选择

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

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

作者的 README

{