Skip to main content
Glama
nanocart-mcp

nanocart-mcp

by ByteBunny-io

nanocart-mcp

Official NanoCart MCP server — run your store from any MCP-capable AI agent (Claude Code, Claude Desktop, Cursor, Codex, and friends). List and update products (with variants and images), manage orders, coupons, categories, subscribers and settings, and pull sales reports — by asking.

39 tools. Reads are marked read-only; destructive tools (archive product, delete coupon) are annotated so your agent asks before acting. Refunds, billing changes, and API-key management are deliberately NOT exposed — do those in your dashboard.

Credentials

From your dashboard: Settings → API Keys (sc_live_..., keep secret) and Settings → Store Information (your store ID). The key grants full admin access to your store — treat it like a password.

Related MCP server: mcp-server-woocommerce

Claude Code:

claude mcp add nanocart --env NANOCART_API_KEY=sc_live_... --env NANOCART_STORE_ID=your-store-id -- npx -y nanocart-mcp

Any client that speaks stdio MCP (JSON config style):

{
  "mcpServers": {
    "nanocart": {
      "command": "npx",
      "args": ["-y", "nanocart-mcp"],
      "env": {
        "NANOCART_API_KEY": "sc_live_...",
        "NANOCART_STORE_ID": "your-store-id"
      }
    }
  }
}

Option B — Hosted (no install)

Endpoint: https://mcp.nanocart.io/mcp?store=your-store-id with header Authorization: Bearer sc_live_... (Streamable HTTP).

Claude Code:

claude mcp add nanocart --transport http "https://mcp.nanocart.io/mcp?store=your-store-id" --header "Authorization: Bearer sc_live_..."

Note: web clients that only support OAuth-based custom connectors (e.g. claude.ai's connector UI) can't send API-key headers yet — use Option A there.

Example prompts

  • "List my draft products and publish the ones with images"

  • "Create a SUMMER20 coupon — 20% off, min order $50, expires end of August"

  • "What did I sell last week? Any orders I still need to ship?"

  • "Mark order NCT-1042 shipped with tracking 9400 1000 0000 0000 0000 00"

  • "Upload the photos in ./shots and create products from them at $24 each"

Safety

  • Secrets are redacted from every response; your key is never echoed or logged.

  • Destructive tools carry MCP destructiveHint annotations — well-behaved clients prompt before running them.

  • Prices are explicit price_cents integers (no dollars/cents ambiguity).

Pairs with the NanoCart skill (integration knowledge for building the cart into websites). Docs: https://docs.nanocart.io/#ai-build · AI-readable: https://docs.nanocart.io/llms-full.txt

MIT · © 2026 NanoCart · a ByteBunny, LLC company

Available Tools

31 tools
analytics_funnelA
Read-only
Inspect

Cart funnel analytics for a date range: sessions that viewed, added to cart, reached checkout, purchased; abandoned value.

Inputs: to, from.

archive_productA
Destructive
Inspect

Archive (soft-delete) a product — it disappears from the store but stays in the database. CONFIRM WITH THE USER before calling; name the product, not just the id.

Inputs: productId (required).

create_categoryBInspect

Create a category. parentId makes it a subcategory.

Inputs: name (required), image, parentId, sortOrder, +1 more.

create_couponBInspect

Create a coupon. value = 1-100 for percent_off, integer cents for fixed_amount, ignored for free_shipping.

Inputs: code (required), type (required), value (required), maxUses, +2 more.

create_productAInspect

Create a product. Defaults to DRAFT (invisible to shoppers) unless status "active". Prices in integer cents. Upload images first with upload_image and pass the returned fileUrls.

Inputs: name (required), price_cents (required), slug, tags, +13 more.

create_vendorAInspect

Create a fulfillment vendor. Requires name and at least one "to" address. Route products to it afterwards via update_product (fulfillment_vendor_id + vendor_sku). Vendor order emails never include prices. Max 10 vendors per store.

Inputs: to (required), name (required), cc, notes, +5 more.

delete_couponA
Destructive
Inspect

Delete a coupon by code. CONFIRM WITH THE USER before calling.

Inputs: code (required).

delete_vendorA
Destructive
Inspect

Delete a fulfillment vendor — its routed products keep selling but orders stop being forwarded. CONFIRM WITH THE USER before calling; name the vendor, not just the id.

Inputs: vendorId (required).

get_settingsA
Read-only
Inspect

Get store settings: shipping_config, tax_config, email_config, order_config.

Inputs: no named parameters.

get_storefrontA
Read-only
Inspect

Get hosted-storefront configuration (template, hero, sections). Only meaningful on hosted plans.

Inputs: no named parameters.

get_store_infoA
Read-only
Inspect

Get the store bound to this API key: name, slug (storeId), tier, domain, currency, configured payment processors, allowed domains. Secrets are never included.

Inputs: no named parameters.

get_tier_usageA
Read-only
Inspect

Current plan tier, its limits, and live usage (active products, coupons, monthly orders). Check this before bulk-creating products.

Inputs: no named parameters.

get_vendorA
Read-only
Inspect

Fetch one fulfillment vendor including its order-sheet templateHtml.

Inputs: vendorId (required).

list_categoriesA
Read-only
Inspect

List the store’s categories (via the public API).

Inputs: no named parameters.

list_couponsA
Read-only
Inspect

List all coupons with usage counts.

Inputs: no named parameters.

list_ordersA
Read-only
Inspect

List orders, newest first. Filter by status and/or ISO date range; paginate with limit/lastKey.

Inputs: to, from, limit, status, +1 more.

list_productsA
Read-only
Inspect

List ALL products including drafts and archived. Optionally filter by status or search by name/slug substring (filtering happens client-side).

Inputs: search, status.

list_subscribersA
Read-only
Inspect

List email subscribers (Product Alerts). Paginate with limit/lastKey.

Inputs: limit, lastKey.

list_vendorsA
Read-only
Inspect

List the store's fulfillment vendors — custom partners (e.g. a local print shop) that get emailed an order sheet when their routed products sell. Metadata only; use get_vendor for the email template HTML. Pro/Expert plans.

Inputs: no named parameters.

list_webhook_deliveriesA
Read-only
Inspect

Recent signed-webhook delivery attempts and results.

Inputs: no named parameters.

resend_order_confirmationBInspect

Resend the order confirmation email to the customer for an order.

Inputs: orderId (required).

sales_reportB
Read-only
Inspect

Sales report for a date range: revenue, orders, AOV, tax collected (total + by state), shipping, discounts, top products.

Inputs: to, from.

send_order_to_vendorAInspect

Manually email an existing order to a vendor — for orders placed before the vendor was set up (items match by the products' CURRENT vendor routing) or deliberate re-sends. Orders with routed items are emailed automatically at payment; this is only for manual sends. Note: while the store's Fulfillment Test Mode is on, the email goes to the merchant with a [TEST] banner.

Inputs: orderId (required), vendorId (required).

send_vendor_testAInspect

Email the MERCHANT (never the vendor) a test order sheet rendered with sample data, so they can see exactly what the vendor will receive.

Inputs: vendorId (required).

update_categoryAInspect

Update a category by categoryId (partial).

Inputs: categoryId (required), name, image, status, +3 more.

update_orderAInspect

Update an order’s status, tracking number, or notes. Status transitions to "shipped" notify the customer webhook. Allowed statuses: pending, confirmed, processing, shipped, delivered, cancelled, refunded. NOTE: to actually refund money, the merchant must use the dashboard — this tool only changes the label.

Inputs: orderId (required), notes, status, trackingNumber.

update_productAInspect

Update any fields of an existing product by productId (partial update). Prices in integer cents.

Inputs: productId (required), name, tags, images, +12 more.

update_settingsAInspect

Update ONE settings key: shipping_config, tax_config, email_config, or order_config. Read get_settings first and send the full desired value for that key. Tier limits apply to shipping methods.

Inputs: value (required), settingKey (required).

update_store_configAInspect

Update store display config: name, domain, brandColor, currency, allowedDomains. Payment credentials can NOT be changed here (dashboard only). Changing allowedDomains affects which sites the widget works on — confirm with the user.

Inputs: name, domain, currency, brandColor, +1 more.

update_vendorAInspect

Update a fulfillment vendor (partial — provide only the fields to change; the rest are preserved, including the saved template). Use status "paused"/"active" to pause or resume order emails.

Inputs: vendorId (required), cc, to, name, +6 more.

upload_imageAInspect

Upload an image (or digital file) to the store’s storage and get back a public fileUrl for product/category images. Provide EITHER file_path (local server only) OR source_url (fetched server-side).

Inputs: file_name, file_path, source_url, upload_type, +1 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Even the get_* tools (get_settings, get_storefront, get_store_info, get_tier_usage) have clearly separated purposes covering configuration, storefront template, store binding, and plan usage. No two tools appear to do the same thing.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (create_, update_, list_, get_, delete_). The only deviations are 'sales_report' and 'analytics_funnel', which are noun phrases rather than verb_noun, but they are still unambiguous and fit the domain as report queries.

    Tool Count3/5

    With 31 tools, the server is on the heavier side, but the count is largely justified by the broad scope of features: products, categories, orders, coupons, settings, vendors, analytics, and storefront. Some consolidation could be possible, but each tool has a distinct role.

    Completeness3/5

    Obvious gaps exist: no delete_category, no update_coupon, no get_order for individual order detail, and no get_product by ID (only list with filters). However, the surface covers the core workflows for product management, order status updates, and vendor fulfillment, so most agent tasks can be accomplished with workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server for managing WooCommerce stores through AI assistants like Claude. Provides 101 tools covering products, orders, customers, coupons, shipping, taxes, webhooks, settings, reports, and more.
      100
      111 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Karrito - the digital catalog builder for WhatsApp sellers in LATAM, enabling AI assistants to manage store operations like products, orders, discounts, reviews, shipping, and analytics.
      30
      20 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Official MCP server for accepting crypto payments through OrcaRail. It enables AI agents to create payment intents, manage subscriptions, handle product catalogs, and get exchange rates via natural language.
      26
      58 npm
      MIT