Read products, listings and orders; update stock, publish listings, mark orders shipped in Nembol. For online sellers who publish one product catalogue to Shopify, eBay, Etsy and Amazon from Nembol. 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": {
"nembol": {
"url": "https://nembol.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"nembol": {
"type": "http",
"url": "https://nembol.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.
List the channel accounts, then search products and listings. Filter listings by status error to see each failure cause.
nembol_list_channel_accounts nembol_list_products nembol_list_listings
List the newest orders, then open one to read its lines, totals and fulfillment status.
nembol_list_orders nembol_get_order
Set the stock or price of up to 100 SKUs in one call. Follow the returned operation to see one result per SKU and channel.
Changes data · nembol_update_stock_and_prices nembol_get_operation
Publish one product to one channel account. Publishing runs in the background, so follow it with the listing status.
Changes data · nembol_publish_product_to_channel nembol_get_listing
Read the order first, then mark it shipped with tracking. This cannot be undone. With tracking, the source marketplace is notified once per order.
Changes data · nembol_get_order nembol_mark_order_shipped
The login page asks for your Nembol API key.
Create the key in Nembol under Settings → Developers (store owner). The API needs the Enterprise+ plan. A test key (nbl_test_) is simulated and never reaches a sales channel, so try writes with it first. Your key is used only to call the API on your behalf; it is never shown to anyone.
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 Nembol API key. 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 Nembol connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
nembol_get_store | read | Get the 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 | read | 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 | read | List and search 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 | read | Get a product Return one product with its variants, images, stock, prices and listing summary. GET /products/{id}. |
nembol_list_listings | read | 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 | read | Get a listing Return one listing: channel, status, URL on the channel, overrides, issues and the last operation id. GET /listings/{id}. |
nembol_list_orders | read | 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 | read | Get an order Return one order with its lines, totals, tracking and buyer data the key may read. GET /orders/{id}. |
nembol_get_operation | read | Get an 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 | read | 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 | read | List the action log 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 | write | Create a 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 | write | Update a 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 | write | Update stock and prices by SKU 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 | write | Publish a product to a 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 | write | Delist a 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 they agree, call again with the same listing_id and the token. DELETE /listings/{id}. |
nembol_mark_order_shipped | write | Mark an 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. |
nembol_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. | |
nembol_request_feature | Request a missing feature Tell usefulapi that the user needs something the Nembol 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. | |
nembol_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Nembol (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. | |
nembol_cancel_subscription | Cancel the Pro subscription Cancel the caller's Nembol 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 nembol_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper 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 Nembol server only. Subscribe with nembol_upgrade (it returns a Stripe Checkout link). Cancel any time with nembol_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running nembol_upgrade before then undoes the cancel. Or write to [email protected].
Find products that are not listed on a channel. Read orders waiting for shipment. Set stock and prices for many SKUs. Publish a product to one sales channel. Mark an order shipped with tracking. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Nembol. The server calls the Nembol API with your own Nembol 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 Nembol API key. See Before you connect for where to find it.
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 Nembol API key. 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 Nembol 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 Nembol.
Yes, if you approve it. 6 of the 17 Nembol tools can create or change data. The other 11 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
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 Nembol server only. Cancel any time: Pro then runs to the end of the paid period. Run nembol_usage_status to see how many calls you used.
Ask the AI to run nembol_upgrade: it returns a Stripe Checkout link. To cancel, run nembol_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 nembol_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.