Skip to main content
Glama

sapo-mcp

npm version License: MIT Node 20+

Model Context Protocol server for Sapo.vn POS & e-commerce platform.

Features

  • 4 modes, 105 unique tools: pos-online (51), web (31), pos-counter (15), analytics (10) — 2 read tools shared between pos-online and web

  • Two transports: stdio (Claude Desktop, Cursor) and Streamable HTTP (Docker, GoClaw)

  • Safe by default: destructive ops gated via SAPO_ALLOW_OPS (default: none); all destructive calls also require confirm: true

  • Single-tenant: one shop per server instance via Private App credentials

  • Pre-1.0: tool names and schemas may shift on minor bumps. See Post-1.0 roadmap.

Related MCP server: Saleor MCP Server

Installation

Requires Node.js 20 or newer. Verify with node --version.

Option A — npx (no install)

Recommended for MCP clients (Claude Desktop, Cursor). Always pulls the latest published version:

npx -y sapo-mcp@latest --version

Option B — global install

npm install -g sapo-mcp
sapo-mcp --version
sapo-mcp --help

Option C — local project dependency

npm install sapo-mcp
npx sapo-mcp --mode=pos-online

Quick Start

1. Get Credentials

Create a Private App at developers.sapo.vn:

  • Store name: mystorename → mystorename.mysapo.net

  • API Key + Secret

2. Configure your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "sapo": {
      "command": "npx",
      "args": ["-y", "sapo-mcp", "--mode=pos-online,web,analytics"],
      "env": {
        "SAPO_STORE": "mystorename",
        "SAPO_API_KEY": "xxx",
        "SAPO_API_SECRET": "yyy"
      }
    }
  }
}

Restart Claude Desktop. Tools appear under the 🔌 plug icon.

Cursor

Edit ~/.cursor/mcp.json or per-workspace .cursor/mcp.json:

{
  "mcpServers": {
    "sapo": {
      "command": "npx",
      "args": ["-y", "sapo-mcp", "--mode=pos-online,web"],
      "env": {
        "SAPO_STORE": "mystorename",
        "SAPO_API_KEY": "xxx",
        "SAPO_API_SECRET": "yyy"
      }
    }
  }
}

MCP Inspector (test/debug)

npx @modelcontextprotocol/inspector \
  -e SAPO_STORE=mystorename \
  -e SAPO_API_KEY=xxx \
  -e SAPO_API_SECRET=yyy \
  npx -y sapo-mcp --mode=pos-online

Open the printed URL in a browser to inspect/invoke registered tools.

Use --mode=pos-online,web,analytics to register multiple modes (union of tools; shared tools registered once).

3. CLI Flags

Flag

Default

Description

--mode=<modes>

pos-online

Comma-separated list of modes to activate

--transport=<t>

stdio

Transport type (stdio or http)

--port=<port>

3333

HTTP port (ignored for stdio)

--help

—

Print usage and exit

--version

—

Print version and exit

Environment Variables

Variable

Required

Default

Description

SAPO_STORE

Yes

—

Store subdomain

SAPO_API_KEY

Yes

—

Private App API Key

SAPO_API_SECRET

Yes*

—

Private App API Secret

SAPO_API_SECRET_FILE

Yes*

—

Path to file containing secret (takes precedence)

SAPO_ALLOW_OPS

No

""

CSV of allowed destructive categories

SAPO_MAX_AUTO_PAGES

No

10

Max auto-pagination pages

SAPO_RETRY_MAX

No

3

HTTP retry attempts

SAPO_LOG_LEVEL

No

info

Log level (error/warn/info/debug/trace)

SAPO_HTTP_HOST

No†

127.0.0.1

HTTP bind host (loopback by default)

SAPO_HTTP_PORT

No

3333

HTTP port

SAPO_HTTP_MAX_SESSIONS

No

100

Max concurrent MCP sessions

SAPO_HTTP_SESSION_IDLE_MS

No

1800000

Idle session GC threshold (30 min)

SAPO_MCP_AUTH_TOKEN

No†

—

Bearer token. Required if host is non-loopback

SAPO_HTTP_CORS_ORIGINS

No

—

CSV of allowed CORS origins (default: disabled)

*One of SAPO_API_SECRET or SAPO_API_SECRET_FILE is required. †HTTP-only. Token is enforced when SAPO_HTTP_HOST is not 127.0.0.1/localhost/::1.

Modes

Mode

Status

Description

pos-online

0.5.0

Online orders, customers, fulfillment (51 tools)

web

0.5.0

Storefront, collections, articles, SEO (31 tools)

pos-counter

0.5.0

POS counter: locations, inventory write, suppliers, shifts, stock transfers (15 tools)

analytics

0.5.0

Composed reports: revenue, top products/customers, LTV, tax, channel breakdown, discount usage, shift report (10 tools)

Note: pos-counter excludes 5 internal-only endpoints (purchase_orders, purchase_returns, stock_adjustments, cash_transactions, cashbook) — these return HTTP 403 for Private App credentials and require an OAuth Partner App (post-1.0 roadmap).

Analytics tools auto-paginate up to SAPO_MAX_AUTO_PAGES; results carry truncated: true when the cap is hit.

Tool Verification Status

Verification levels for the 105 unique tools (last updated 2026-04-30):

Symbol

Level

What it means

✅

Canary-monitored

Endpoint + schema verified live; daily nightly probe via .github/workflows/canary.yml

🟢

Live-verified

Endpoint hit during development, schema captured to fixture, not in daily canary

🟡

Docs-only

Schema from docs/sapo-api-reference.md (Sapo official); mock tests only, no live probe

🔵

Composed

Not a Sapo endpoint — internal aggregation logic, logic-tested via unit tests

🚨

Broken

Known non-functional, see notes

Canary-monitored endpoints (drift detected within 24h)

Resource

Mode(s)

Endpoint

store

all

/admin/store.json

products (read)

pos-online, pos-counter

/admin/products.json

orders

pos-online, pos-counter

/admin/orders.json

customers

pos-online, pos-counter

/admin/customers.json

inventory_levels

pos-online, pos-counter

/admin/inventory_levels.json

locations

pos-counter

/admin/locations.json

draft_orders

pos-online

/admin/draft_orders.json

price_rules

pos-online

/admin/price_rules.json

pages

web

/admin/pages.json

suppliers

pos-counter

/admin/suppliers.json

stock_transfers

pos-counter

/admin/stock_transfers.json

payment_methods

pos-counter

/admin/payment_methods.json

🚨 Broken — needs investigation

Tool

Resource

Issue

list_pos_shifts

pos_shifts

/admin/pos_shifts.json returns Content-Type: text/html (Sapo POS web app shell), not JSON.

get_pos_shift

pos_shifts

Same as above. JSON API endpoint not yet located.

These 2 tools may fail at runtime. POS shift management currently requires admin UI.

Per-tool status

Click each section to expand the full tool list with status icons.

Customers (7)

  • ✅ list_customers, get_customer, search_customers, count_customers, list_customer_orders

  • 🟢 create_customer, update_customer

Customer Addresses (4)

  • 🟡 list_customer_addresses, add_customer_address, update_customer_address, set_default_customer_address

Products (read) (4)

  • ✅ list_products, get_product, search_products, count_products

Variants (read) (2)

  • 🟡 list_variants_for_product, get_variant

Inventory (read) (1)

  • ✅ get_inventory_levels

Orders (4)

  • ✅ list_orders, get_order, count_orders, search_orders

Order Transactions (2)

  • 🟢 list_order_transactions, create_order_transaction

Fulfillments (4)

  • 🟢 list_fulfillments_for_order, get_fulfillment

  • 🟡 create_fulfillment, update_fulfillment_tracking

Refunds (3)

  • 🟢 list_refunds, get_refund, create_refund (create_refund destructive: SAPO_ALLOW_OPS=refund)

Draft Orders (7)

  • ✅ list_draft_orders, get_draft_order

  • 🟡 create_draft_order, update_draft_order, complete_draft_order, send_draft_order_invoice, delete_draft_order (destructive: delete)

Price Rules (5)

  • ✅ list_price_rules, get_price_rule

  • 🟡 create_price_rule, update_price_rule, delete_price_rule (destructive: delete)

Discount Codes (3)

  • 🟡 list_discount_codes, create_discount_code, delete_discount_code (destructive: delete)

Destructive (cancel/delete-strict) (4)

  • 🟡 cancel_order, close_order, cancel_fulfillment (destructive: cancel)

  • 🟡 delete_customer, delete_variant (destructive: delete_strict)

Store (1)

  • ✅ get_store_info

Articles (5)

  • 🟡 list_articles, get_article, create_article, update_article, delete_article (destructive: delete)

Blogs (5)

  • 🟡 list_blogs, get_blog, create_blog, update_blog, delete_blog (destructive: delete)

Pages (4)

  • ✅ list_pages, get_page

  • 🟡 update_page_seo, delete_page (destructive: delete)

Collections (10)

  • 🟡 list_custom_collections, get_custom_collection, create_custom_collection, update_custom_collection, delete_custom_collection (destructive: delete)

  • 🟡 list_smart_collections, get_smart_collection

  • 🟡 list_collects, create_collect, delete_collect (destructive: delete)

Script Tags (3)

  • 🟡 list_script_tags, create_script_tag, delete_script_tag (destructive: delete)

Products SEO (1)

  • 🟡 update_product_seo

Variants (read, shared) (2)

  • 🟡 list_variants_for_product, get_variant

Locations (2)

  • ✅ list_locations, get_location

Payment Methods (1)

  • ✅ list_payment_methods

Inventory (write) (3)

  • 🟡 adjust_inventory_level, connect_inventory_level

  • 🟡 set_inventory_level (destructive: inventory_set)

Variants (write) (1)

  • 🟡 update_variant

POS Orders (2)

  • ✅ list_pos_orders, get_pos_order (uses /admin/orders?source_name=pos)

Suppliers (2)

  • ✅ list_suppliers, get_supplier

Stock Transfers (2)

  • ✅ list_stock_transfers, get_stock_transfer

POS Shifts (2)

  • 🚨 list_pos_shifts, get_pos_shift (see Broken section above — endpoint returns HTML)

All 10 are 🔵 composed (aggregate from multiple Sapo endpoints, no single endpoint to verify):

revenue_summary, top_products, top_customers, customer_ltv, tax_summary, online_vs_counter_breakdown, discount_usage_report, shift_report, inventory_low_stock, inventory_value

Destructive Operations

Destructive tools (cancel, delete, bulk-delete) are blocked by default. To enable specific categories:

# Allow order cancellation and standard deletes only
SAPO_ALLOW_OPS=cancel,delete npx sapo-mcp --mode=pos-online

Supported categories: cancel, delete, delete_strict, inventory_set, refund, shift_close, cashbook_write.

All destructive tool calls also require confirm: true in the tool arguments — this prevents accidental execution when an LLM calls the tool without explicit intent.

Security

ENV credentials are visible to other processes via ps / /proc/<pid>/environ on shared hosts. Use SAPO_API_SECRET_FILE to pass the secret via a file instead of an env var where possible.

Note: full secret-file isolation (reading the secret only at startup, then clearing) is tracked for the post-1.0 roadmap.

Probing

Verify which Sapo API endpoints are available on your store before configuring tools.

# Read-only probe — safe to run against any store (GET only)
SAPO_STORE=mystore SAPO_API_KEY=xxx SAPO_API_SECRET=yyy npm run probe

# Schema drift check — same probe + Zod validation against fixtures
npm run canary

Write-probe (npm run probe:write) refuses to run unless SAPO_STORE contains test, dev, or sandbox — never against production.

HTTP Transport (Remote / Docker)

Run as an HTTP server for remote MCP clients (e.g. GoClaw) or self-hosted Docker:

# Local-only (no auth required)
sapo-mcp --mode=pos-online --transport=http --port=3333

# Public bind (auth token required)
SAPO_HTTP_HOST=0.0.0.0 \
SAPO_MCP_AUTH_TOKEN=$(openssl rand -hex 32) \
sapo-mcp --mode=pos-online --transport=http

Endpoints:

Method

Path

Description

GET

/health

Liveness probe — returns { status, version, modes, sessions }

POST

/mcp

JSON-RPC over Streamable HTTP (creates a session on initialize)

GET

/mcp

SSE long-poll for an existing session (mcp-session-id header)

DELETE

/mcp

Terminate a session

Session model: Each MCP client gets a UUID session, isolated by an McpServer instance. Idle sessions (SAPO_HTTP_SESSION_IDLE_MS) are evicted automatically. Concurrent sessions cap at SAPO_HTTP_MAX_SESSIONS (503 returned when full).

Security:

  • Defaults to 127.0.0.1 — loopback only. Token optional.

  • Setting SAPO_HTTP_HOST=0.0.0.0 (or any non-loopback) requires SAPO_MCP_AUTH_TOKEN. The server refuses to start otherwise.

  • CORS is off by default. Enable per-origin via SAPO_HTTP_CORS_ORIGINS (CSV of origins, or * for all). Only enable when serving browser-based agents.

Docker

See examples/Dockerfile and examples/docker-compose.yml.

docker build -f examples/Dockerfile -t sapo-mcp:local .
docker run --rm -p 3333:3333 \
  -e SAPO_STORE=mystore \
  -e SAPO_API_KEY=xxx -e SAPO_API_SECRET=yyy \
  -e SAPO_HTTP_HOST=0.0.0.0 \
  -e SAPO_MCP_AUTH_TOKEN=$(openssl rand -hex 32) \
  sapo-mcp:local

Development

npm install
npm run typecheck   # Type check
npm run lint        # Lint
npm run test        # Run tests
npm run build       # Build for release

Post-1.0 roadmap

The 1.0.0 stable cut is gated on the following items, deferred from this release:

  • MCP Resources — sapo://shop/info, sapo://orders/today, sapo://orders/pending, sapo://inventory/low-stock. Read-heavy data is more efficient as a Resource than repeated tool calls.

  • MCP Prompts — templated workflows (respond_to_complaint, weekly_report, seo_optimize_product, customer_followup).

  • Webhook receiver — sub-package surfacing Sapo webhooks as MCP events.

  • OAuth 2.0 Partner App — multi-tenant SaaS deployments. Unlocks the 5 internal-only endpoints currently excluded from pos-counter and 4 deferred finance/PO reports (cashflow_summary, pnl_summary, supplier_purchase_summary, daily_pos_report).

  • Storefront GraphQL module — verify Private App access; scope tools if available.

Changelog

See CHANGELOG.md for the per-version history.

License

MIT — See LICENSE

Available Tools

46 tools
add_customer_addressA

Add a new address to a customer. Required: address1, city, country. Province handling: pass either province (text — fuzzy-matched, e.g. "Hồ Chí Minh", "HCM", "TPHCM" all resolve to canonical "TP Hồ Chí Minh") OR province_code (1–63). The tool fills the missing field from the canonical Sapo dataset. For district/ward: pass BOTH text name AND code together (use list_districts / list_wards). NOTE: Sapo write API only accepts the pre-2025 3-tier schema. Post-2025 codes (province_code 2001+, district_code "-1") are rejected pre-flight.

Inputs: city (required), country (required), address1 (required), customer_id (required), +13 more.

complete_draft_orderA

Complete a draft order and convert it into a real order. Side effect: creates an Order from the draft; draft status becomes "completed". Use payment_pending=true if payment not yet collected.

Inputs: draft_order_id (required), payment_pending.

count_customersA

Count total customers in the store, optionally filtered by creation date.

Inputs: created_on_max, created_on_min.

count_ordersA

Count total orders, optionally filtered by status, financial_status, or date range. Returns { count: N }.

Inputs: status, created_on_max, created_on_min, financial_status.

count_productsA

Count total products in the store, optionally filtered by status, vendor, or product_type.

Inputs: status, vendor, product_type.

create_customerA

Create a new customer. Must provide either email OR phone (or both). Optionally include addresses array for inline address creation. Returns the created customer including auto-generated id.

Inputs: dob, note, tags, email, +7 more.

create_discount_codeA

Create a discount code for a price rule. Side effect: creates a DiscountCode that customers can apply at checkout. Code must be unique across the store.

Inputs: code (required), price_rule_id (required).

create_draft_orderA

Create a new draft order. Side effect: creates a DraftOrder in "open" status. Requires at least one line_item with variant_id or title+price for custom items.

Inputs: line_items (required), note, tags, email, +4 more.

create_fulfillmentA

Create a fulfillment for an order, optionally specifying line items and tracking info. Side effect: creates a Fulfillment record and marks specified line_items as fulfilled.

Inputs: order_id (required), line_items, tracking_url, notify_customer, +2 more.

create_order_transactionA

Create a transaction for an order (e.g. capture, sale, refund). Side effect: creates a Transaction record and may change order financial_status. kind: authorization | capture | sale | void | refund.

Inputs: kind (required), amount (required), order_id (required), gateway, +2 more.

create_price_ruleA

Create a new price rule (discount rule). Side effect: creates a PriceRule record. value must be a STRING (e.g. "-10.0" for 10% off). title, value_type, value, target_type, allocation_method, customer_selection, target_selection are required.

Inputs: title (required), value (required), value_type (required), target_type (required), +7 more.

get_customerA

Get a single customer by ID, including their address list and order count.

Inputs: customer_id (required).

get_draft_orderA

Get a single draft order by ID. Returns full draft order including line_items, customer, address, and applied discounts.

Inputs: draft_order_id (required).

get_fulfillmentA

Get a single fulfillment by ID. Returns full fulfillment with tracking info, line_items, and origin address.

Inputs: fulfillment_id (required).

get_inventory_levelsA

Get inventory levels (available + committed quantities) for specific variants at specific locations. Filter by location_id, inventory_item_id, or both.

Inputs: page, limit, location_id, inventory_item_id.

get_orderA

Get a single order by ID. Returns full order including line_items, fulfillments, customer, billing/shipping address, and financial details.

Inputs: order_id (required).

get_price_ruleA

Get a single price rule by ID. Returns full price rule including value_type, value (string), entitled/prerequisite IDs, and usage stats.

Inputs: price_rule_id (required).

get_productB

Get a single product by ID, including its variants, options, and images.

Inputs: product_id (required).

get_refundA

Get a single refund by ID. Returns full refund record.

Inputs: order_id (required), refund_id (required).

get_variantA

Get a single product variant by ID. Returns price (VND, float with 4 decimals), SKU, barcode, inventory quantity, and option values.

Inputs: variant_id (required).

list_customer_addressesA

List all saved addresses for a customer, including default address flag and Vietnamese province/district/ward fields.

Inputs: customer_id (required), limit.

list_customer_ordersA

List all orders placed by a specific customer. Returns paginated results via since_id cursor.

Inputs: customer_id (required), limit, since_id.

list_customersA

List customers with optional filters. Returns paginated results via since_id cursor. If has_more=true, call again with next_since_id.

Inputs: limit, since_id, created_on_max, created_on_min, +2 more.

list_discount_codesA

List discount codes for a specific price rule. Returns paginated results via since_id cursor. Must provide price_rule_id.

Inputs: price_rule_id (required), limit, since_id.

list_districtsA

List districts (Quận/Huyện) within a province. Only meaningful for level=3 (pre-2025 3-tier schema, default). With level=2 the response is empty because the district level was abolished on 2025-07-01.

Inputs: province_code (required), level.

list_draft_ordersA

List draft orders with optional filters. Returns paginated results via since_id cursor. Filter by status. If has_more=true, call again with next_since_id.

Inputs: limit, status, since_id.

list_fulfillments_for_orderA

List all fulfillments for a specific order. Returns fulfillment records with tracking info, line_items, and delivery status.

Inputs: order_id (required).

list_ordersA

List orders with optional filters. Returns paginated results via since_id cursor. Filter by status, financial_status, fulfillment_status, or source_name (facebook, web, pos). If has_more=true, call again with next_since_id.

Inputs: limit, status, since_id, source_name, +4 more.

list_order_transactionsA

List all transactions for a specific order. Returns payment attempts, captures, refunds, and voids linked to the order.

Inputs: order_id (required).

list_price_rulesA

List price rules (discount rules) with optional filters. Returns paginated results via since_id cursor. Filter by status (active, archived, scheduled).

Inputs: limit, status, since_id.

list_productsA

List products with optional filters (status, vendor, product_type). Returns paginated results via since_id cursor. If has_more=true, call again with next_since_id.

Inputs: limit, status, vendor, since_id, +3 more.

list_provincesA

List Vietnamese provinces. Default (omit level) = level=3 = pre-2025 63 tỉnh, 3-tier. Use level=2 for post-2025 34 tỉnh, 2-tier (after merger). Province codes differ between schemas: level=3 codes are "1"–"63"; level=2 codes start at "2001". WORKFLOW: For new schema → list_provinces({level:2}) then list_wards({level:2, province_code}). For old schema → list_provinces() → list_districts({province_code}) → list_wards({district_code}). NOTE: Sapo write endpoints (add/update_customer_address) currently accept ONLY level=3 codes; level=2 is read-only as of 2026-05.

Inputs: level.

list_refundsA

List refunds for a specific order. Returns full refund records with associated transactions, refund line items, and order adjustments.

Inputs: order_id (required).

list_variants_for_productA

List all variants for a product (SKUs, prices in VND, inventory quantities). Returns paginated results via since_id cursor.

Inputs: product_id (required), limit, since_id.

list_wardsA

List wards (Phường/Xã). For level=3 (default, 3-tier) pass district_code obtained from list_districts. For level=2 (2-tier post-reform) pass province_code obtained from list_provinces({level:2}). Post-reform wards attach directly to province — their district_code is the sentinel "-1".

Inputs: level, district_code, province_code.

search_customersA

Search customers by query string (matches email, phone, name). Returns paginated list.

Inputs: query (required), limit.

search_ordersA

Search orders by name (order #), customer email, or customer phone. Uses filter params on the orders list endpoint. Returns paginated results.

Inputs: name, email, limit, phone.

search_productsA

Search products by title substring. Uses the title filter on the list endpoint. Returns paginated results.

Inputs: title (required), limit, status.

send_draft_order_invoiceA

Send an invoice email for a draft order. Side effect: sends email to customer; draft status becomes "invoice_sent". Requires customer email on the draft or provide via to param.

Inputs: draft_order_id (required), to, from, subject, +1 more.

set_default_customer_addressA

Set a customer's default address via Sapo's dedicated endpoint (PUT /customers/{id}/addresses/{addr_id}/default.json). Returns the address now marked default.

Inputs: address_id (required), customer_id (required).

update_customerA

Update an existing customer. Only provided fields are modified. Use add_customer_address / update_customer_address tools for address management.

Inputs: customer_id (required), dob, note, tags, +7 more.

update_customer_addressA

Update an existing customer address. Only provided fields are modified. To set this address as default, use set_default_customer_address (Sapo dedicated endpoint). IMPORTANT: When changing subdivision fields, pass BOTH the text name AND the code (e.g. province + province_code together) — codes alone are silently dropped. Sapo write API only accepts the pre-2025 3-tier schema; new 2-tier addresses cannot be written via this endpoint (returns 422 "Ward is not supported").

Inputs: address_id (required), customer_id (required), zip, city, +14 more.

update_draft_orderA

Update a draft order in "open" status. Side effect: modifies draft order fields. Cannot update completed or cancelled drafts.

Inputs: draft_order_id (required), note, tags, email, +5 more.

update_fulfillment_trackingA

Update tracking information for an existing fulfillment. Side effect: modifies the Fulfillment tracking_company, tracking_number, or tracking_url.

Inputs: fulfillment_id (required), tracking_url, notify_customer, tracking_number, +1 more.

update_orderA

Update an existing order via PUT /admin/orders/{id}.json. Supports: tags, note, note_attributes, email, buyer_accepts_marketing. Verified live 2026-05-01. NOTE: The customer link CANNOT be changed via Private App — Sapo silently ignores customer/customer_id fields on update (no error, no effect). Workarounds for tracking customer on a completed order: (a) tag it — tags: "customer:<id>" (searchable via search_orders); (b) set email — email: <customer.email> (Sapo may auto-match in some reports). For a true DB-level link, use the Sapo admin web UI or wait for OAuth Partner App support. Do NOT cancel + recreate via draft_order to "fix" the link — that loses transaction history, refunds, and inventory state.

Inputs: order_id (required), note, tags, email, +2 more.

update_price_ruleA

Update an existing price rule. Side effect: modifies the price rule. Only provided fields are updated. value must remain a string if updating.

Inputs: price_rule_id (required), title, value, status, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 46 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between list, search, count, and get variants. Even similar tools like search_products vs list_products are differentiated by their query parameters.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, including compound nouns like customer_address and order_transaction. There is no mixing of camelCase or other styles.

    Tool Count2/5

    With 46 tools, this exceeds the 25-tool threshold for 'too many,' even though the tools are organized by domain. The count is inflated by multiple list/search/count variants and separate address/province helpers, but the sheer volume makes it heavy.

    Completeness3/5

    The set covers many workflows (customers, orders, fulfillments, draft orders, discounts), but product management lacks create/update/delete, and there are no delete operations for customers or addresses, or create for refunds. These are notable gaps for a commerce platform.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides comprehensive tools for managing CS-Cart e-commerce stores, enabling product management, order handling, and sales analytics.
      12
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Saleor e-commerce data including products, orders, customers, and more.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server wrapping the Pancake POS REST API, enabling AI assistants like Claude to manage Vietnamese e-commerce POS operations with 23 specialized tools and 7 reference resources.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enhanced Model Context Protocol (MCP) server for Odoo ERP with advanced tools for sales, purchases, inventory and accounting.
      MIT