Nembol MCP by usefulapi

它能帮你做什么

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

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

安装

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

你需要

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

你用的是哪个应用？

https://nembol.usefulapi.io/mcp

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

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

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

https://nembol.usefulapi.io/mcp

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

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

它能做什么

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

• nembol_get_store

  Return the store this API key belongs to: name, plan, base currency, mode (live or test) and the key's scopes. Good first call to check the connection. GET /store.

• nembol_list_channel_accounts

  List the connected sales channel accounts (Shopify, eBay, Etsy, Amazon, TikTok Shop and more). Take the channel_account_id from here; a store can have several accounts on one channel. GET /channel_accounts.

• nembol_list_products

  Search products by text, SKU, barcode, status, price or stock range, channel account, listing status or update time. All filters combine. Use updated_after for incremental sync. GET /products.

• nembol_get_product

  Return one product with its variants, images, stock, prices and listing summary. GET /products/{id}.

• nembol_list_listings

  List listings (a product published on one channel account). Use status=error to find failing listings and error_contains to target one failure cause. GET /listings.

• nembol_get_listing

  Return one listing: channel, status, URL on the channel, overrides, issues and the last operation id. GET /listings/{id}.

• nembol_list_orders

  List orders from all channels, newest first by the time they were placed. Each order carries its lines and fulfillment status. Needs the orders:read scope. GET /orders.

• nembol_get_order

  Return one order with its lines, totals, tracking and buyer data the key may read. GET /orders/{id}.

• nembol_get_operation

  Return a background operation (for example a stock update or a publish): status, one result per SKU and channel, and failures. GET /operations/{id}.

• nembol_list_events

  List the store's event log (orders, product and inventory changes, listing status, channel connections). Events are kept 30 days. Use it to catch up after downtime. GET /events.

• nembol_list_actions

  List the changes made through the API and in the dashboard, with the before and after values. Kept 90 days. Use it to see what changed and to find an action id for an undo. GET /actions.

• nembol_create_product

  Create a product in the store. It stays a local draft and is not shown on any channel until nembol_publish_product_to_channel publishes it. POST /products.

• nembol_update_product

  Change a product's texts, brand, category, tags, identifiers or VAT rate. Changes reach every live channel listing that follows the product text. This tool does not change images. PATCH /products/{id}.

• nembol_update_stock_and_prices

  Set the stock quantity and/or the price for up to 100 SKUs in one call. The change is saved in Nembol at once and then sent to every channel the product is live on. Returns an operation to follow with nembol_get_operation. POST /inventory/batch.

• nembol_publish_product_to_channel

  Create a listing: publish a product on one channel account. Publication is queued and runs in the background; follow it with nembol_get_listing or nembol_get_operation. Publishing the same product to the same account twice returns the existing listing. POST /listings.

• nembol_delist_listing

  Remove a listing from its channel. Irreversible: the channel creates a new listing if the product is published again, and reviews and watchers do not return. First call without confirmation_token: Nembol answers with a summary and a token. Show the summary to the user; only if th

• nembol_mark_order_shipped

  Mark a channel order as shipped and/or attach tracking. Applies to the whole order. This is not undoable, and with tracking the source marketplace is notified (once per order) unless notify_channel is false. POST /orders/{id}/fulfillment.

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 11 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

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

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

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

替代选择

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

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

作者的 README

{