Nanocart Mcp

io.github.ByteBunny-ioPublished by GitHub account ByteBunny-iov1.2.0Updated Oct 24, 2026

Manage your NanoCart store from any AI agent: products, orders, coupons, subscribers, reports.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Official NanoCart MCP server that lets an AI assistant manage a NanoCart store: products, orders, coupons, subscribers and sales reports.

What you can do
  • List, create and update products, including variants and images
  • Manage orders, including marking them shipped with tracking
  • Create and manage coupons, categories, subscribers and store settings
  • Pull sales reports and review recent orders
When to use it
Useful when you run a NanoCart store and want to handle catalog updates, order status, coupons and sales questions conversationally from an MCP-capable agent instead of the dashboard.
Requirements
A NanoCart store with an admin API key (NANOCART_API_KEY, sc_live_ prefix) and store ID (NANOCART_STORE_ID). Runs locally via npx nanocart-mcp with Node.js, or as a hosted Streamable HTTP endpoint using an Authorization bearer header and store ID in the URL or X-Store-Id header.
Before you install
The API key grants full admin access to the store and should be treated like a password. Tools can change store data: products, orders, coupons and settings can be created, updated or archived, and destructive tools are only flagged by annotations that clients may ignore. Refunds, billing and API-key management are not exposed. Web clients that only support OAuth connectors cannot send the API-key header.

Installation

In SourceWeft

  1. Open Nanocart Mcp in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ByteBunny-io%2Fnanocart-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nanocart": {
      "type": "http",
      "url": "https://mcp.nanocart.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

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.

Option A — Local (recommended)

Claude Code:

bash
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):

json
{  "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:

bash
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

Source: README.md at commit c967982

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts