Read Sapo store products, orders, customers and stock levels; edit order notes and stock. 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": {
"sapo": {
"url": "https://sapo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"sapo": {
"type": "http",
"url": "https://sapo.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.
The login page asks for your Sapo store, Private app API key and Private app API secret.
Create a private app in the Sapo admin: Cấu hình > Ứng dụng riêng (Private apps), grant it the read (and, if you want edits, write) permissions you need, and copy its API key and secret. The store name is the first part of yourstore.mysapo.net. Your credentials are used only to call the Sapo API on your behalf; they are 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 Sapo store, Private app API key and Private app API secret. 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 Sapo connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
sapo_get_store | read | Get store The Sapo store this login belongs to: name, domain, currency, timezone, plan and other settings. GET /admin/store.json. |
sapo_list_products | read | List products List products with their variants, prices, SKUs and images. Filter by name, vendor, type, collection or created/modified dates. Paged: pass next_page as page. GET /admin/products.json. |
sapo_count_products | read | Count products Number of products matching the filters. GET /admin/products/count.json. |
sapo_get_product | read | Get product One product by id, with variants and images. GET /admin/products/{id}.json. |
sapo_list_product_variants | read | List product variants The variants (size, color, SKU, barcode, price) of one product. Paged. GET /admin/products/{product_id}/variants.json. |
sapo_get_product_variant | read | Get product variant One product variant by id. GET /admin/variants/{id}.json. |
sapo_list_custom_collections | read | List collections List manual product collections (danh mục thủ công). Paged. GET /admin/custom_collections.json. |
sapo_list_orders | read | List orders List orders with line items, customer, totals, payment and fulfillment status. Filter by status, tag, customer or dates. Paged: pass next_page as page. GET /admin/orders.json. |
sapo_count_orders | read | Count orders Number of orders matching the filters. GET /admin/orders/count.json. |
sapo_get_order | read | Get order One order by id with line items, addresses, discounts, payment and shipping. GET /admin/orders/{id}.json. |
sapo_list_order_transactions | read | List order transactions The payment transactions recorded on one order. GET /admin/orders/{order_id}/transactions.json. |
sapo_list_customers | read | List customers List customers with contact details, addresses, order count and total spent. Paged. GET /admin/customers.json. |
sapo_count_customers | read | Count customers Total number of customers. GET /admin/customers/count.json. |
sapo_get_customer | read | Get customer One customer by id. GET /admin/customers/{id}.json. |
sapo_list_locations | read | List locations List branches, stores and warehouses (id, name, address, whether they track stock). Use the ids for stock levels. Paged. GET /admin/locations.json. |
sapo_list_inventory_items | read | List inventory items List inventory items (one per variant) by SKU/barcode search, variant or product ids. The id is what stock levels use as inventory_item_id. Paged. GET /admin/inventory_items.json. |
sapo_list_inventory_levels | read | List inventory levels Stock per item and location: on_hand, available, committed, incoming, reserved. Filter by inventory item or location ids, or by a minimum/maximum available quantity. Sapo documents no paging for this list, so narrow it with ids. GET /admin/inventory_levels.json. |
sapo_list_price_rules | read | List price rules List discount price rules (percentage, fixed amount, fixed price) with validity dates and usage counts. Paged. GET /admin/price_rules.json. |
sapo_update_order | write | Update order note or tags WRITE: set the note and/or the tags of an order (Sapo only lets an order's items and quantities stay fixed after creation). The value REPLACES the existing note or tags: read the order first to keep what is there. PUT /admin/orders/{id}.json. |
sapo_set_inventory_level | write | Set stock quantity WRITE: set the physical stock (on_hand) of one inventory item at one location to an exact quantity, with a reason. This OVERWRITES the current number and is recorded as a stock adjustment: read the level first (sapo_list_inventory_levels). PUT /admin/inventory_levels/set.json. |
sapo_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. | |
sapo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Sapo 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. | |
sapo_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Sapo (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. | |
sapo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Sapo 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 sapo_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 store | $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 Sapo server only. Subscribe with sapo_upgrade (it returns a Stripe Checkout link). Cancel any time with sapo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sapo_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Sapo. The server calls the Sapo API with your own Sapo 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 Sapo store, Private app API key and Private app API secret. See Before you connect for where to find them.
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 Sapo store, Private app API key and Private app API secret. 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 Sapo 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 Sapo.
Yes, if you approve it. 2 of the 20 Sapo tools can create or change data. The other 18 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 Sapo server only. Cancel any time: Pro then runs to the end of the paid period. Run sapo_usage_status to see how many calls you used.
Ask the AI to run sapo_upgrade: it returns a Stripe Checkout link. To cancel, run sapo_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 sapo_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.