Get started

Model Context Protocol

The shop is an API.
Your agent is the interface.

ShopDango ships an MCP server, so the assistant you already use can run the store: change products, edit the site, take an order, block rental dates, and answer the questions you would otherwise open four screens to answer.

Start freeHow to connect

What it can do

Twenty-nine tools, grouped by what you are trying to get done. Nothing here needs a browser, a screenshot, or a human clicking.

Catalog

Add products, change prices, replace photos, retire what sold out.

  • products_list
  • products_get
  • products_create
  • products_update
  • products_set_images
  • products_delete
  • media_upload_from_url

Storefront

Edit the site the same way the builder does: sections, copy, media, publish, undo.

  • site_get
  • site_get_section
  • site_add_section
  • site_update_section
  • site_replace_text
  • site_move_section
  • site_remove_section
  • site_publish
  • site_undo

Orders & customers

Take an order on the phone, change it afterwards, and get the link the customer pays on.

  • orders_create
  • orders_list
  • orders_get
  • orders_update
  • orders_stats

Rentals & bookings

Block a vehicle for a morning or a hall for a season - hours, days, weeks or months.

  • rentals_list_blackouts
  • rentals_add_blackout
  • rentals_update_blackout
  • rentals_remove_blackout

Settings

Read and change store settings across every tab, including plugin configuration.

  • settings_list_sections
  • settings_get
  • settings_update

Plus shopdango_whoami, which tells the agent which store it is connected to and which scopes it holds.

Try saying: “Add two new hoodies at $48, put the kayak on blackout 12–14 November, and tell me last month's revenue.” The agent calls the tools; you see the result in the admin.

Works with the harness you already use

  • Claude Codeclaude mcp add
  • Claude DesktopmcpServers config
  • Codex CLI~/.codex/config.toml
  • CursorMCP settings
  • HermesMCP config
  • Any MCP clientstdio or HTTP

Connecting takes three minutes

  1. 1

    Open Settings → MCP access

    In your merchant admin, pick the scopes this client should have. Read-only, catalog, site publishing, orders - separately.

  2. 2

    Create the token

    Copy it once. It is not shown again, and it cannot be recovered from us.

  3. 3

    Point your harness at it

    Install the ShopDango MCP server, or use the hosted endpoint. Both speak the same tools.

claude mcp add --transport http shopdango \
  https://mcp.shopdango.com/mcp \
  --header "Authorization: Bearer sd_mcp_..."

Hosted, so there is nothing to install. Your admin writes this command for the harness you use - Claude Code, Claude Desktop, Codex, Cursor, or Hermes - with the token already in it, and lists every connected client with its scopes and last use.

Safe by default

Merchant-scoped tokens

A token belongs to one store. It cannot reach another merchant's catalog, orders, or site.

Hashed at rest

Only a SHA-256 hash is stored, plus the first characters so you can recognise a client in the list. The token itself is shown once.

Every capability is a scope

Issue catalog-only access to an inventory agent and storefront-only access to a designer. Each tool refuses outside its scope, server-side.

Revocable, and audited

Revoke a client from the admin in one click. Tokens record who minted them, when, and when they were last used.

Bring your own agent

Every plan includes MCP access. Building a storefront is free; you only pay when you publish and sell.

Create a storeSee pricing