Sapo MCP by usefulapi
io.usefulapi/sapo · v1.2.0 · MCP 2025-06-18
Read Sapo store products, orders, customers and stock levels; edit order notes and stock.
Reachability
reachable
checked 2026-10-26 05:30 UTC
Registry status active
Tools pinned 20
5a824daa5624
Tools last changed
unchanged since first capture 2026-10-26
Repo last push 2026-10-26
as of 2026-10-26
GitHub stars 0
as of 2026-10-26
Provenance
Registry namespace io.usefulapi
(domain verified by the official registry)
Repository
github.com/m190/usefulapi-mcp
Website
https://usefulapi.io/sapo/
Remote endpoints
https://sapo.usefulapi.io/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-10-26 05:30 | first capture | 20 tools pinned |
Pinned tool definitions (20)
| Tool | Description |
|---|---|
| sapo_get_store | The Sapo store this login belongs to: name, domain, currency, timezone, plan and other settings. GET /admin/store.json. |
| sapo_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 | Number of products matching the filters. GET /admin/products/count.json. |
| sapo_get_product | One product by id, with variants and images. GET /admin/products/{id}.json. |
| sapo_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 | One product variant by id. GET /admin/variants/{id}.json. |
| sapo_list_custom_collections | List manual product collections (danh mục thủ công). Paged. GET /admin/custom_collections.json. |
| sapo_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 | Number of orders matching the filters. GET /admin/orders/count.json. |
| sapo_get_order | One order by id with line items, addresses, discounts, payment and shipping. GET /admin/orders/{id}.json. |
| sapo_list_order_transactions | The payment transactions recorded on one order. GET /admin/orders/{order_id}/transactions.json. |
| sapo_list_customers | List customers with contact details, addresses, order count and total spent. Paged. GET /admin/customers.json. |
| sapo_count_customers | Total number of customers. GET /admin/customers/count.json. |
| sapo_get_customer | One customer by id. GET /admin/customers/{id}.json. |
| sapo_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 | 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 | 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... |
| sapo_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: 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 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... |
Get alerted when this changes.
Email the moment io.usefulapi/sapo drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/io.usefulapi/sapo)
Maintain this server? Add the badge to your README. It links your users to this live status page.