Webround Commerce MCP

The commerce server gives Claude the operations of the Commerce API as tools: 269 of them, in 31 groups. Whatever you can do with the API, Claude can do by being asked.

https://ai-api.webround.com/mcp

It speaks Streamable HTTP, without sessions.

Connect

Every request carries three headers:

Header	Value
Authorization	Bearer <API key>: a key of the store, with the scopes you want Claude to have. See API Keys.
store-id	The ID of the store. It is the same as the draft's ID.
user-id	The ID of the store's owner or of one of its collaborators, as for the Commerce API.

With Claude Code:

claude mcp add --transport http webround-commerce "https://ai-api.webround.com/mcp?toolsets=catalog" \
  --header "Authorization: Bearer <API key>" \
  --header "store-id: <store id>" \
  --header "user-id: <user id>"

Choose the tools

269 tools are too many for an assistant to read every time, and most conversations need a part of them. A tool belongs to a toolset, one for each area of the API (products, orders, promotions…). You choose which ones to load with the toolsets parameter of the address:

https://ai-api.webround.com/mcp?toolsets=products,orders

Beside single toolsets you can use a preset, a named pack of toolsets that belong together, so you do not have to know what depends on what (a collection needs filters, a filter needs conditions):

Preset	What it is for
catalog	Products, variants, options, tags, attributes, collections, filters, assets, tax zones, shipping zones and methods, warehouses. This is what you get when you do not ask for anything.
orders	Orders, order items, return requests, subscriptions, customers.
marketing	Promotions, conditions, feeds, reviews, cart analytics.
store-settings	Store settings, checkout hooks, webhooks.
team	Collaborators, roles, API keys, apps.

Presets and single toolsets mix: ?toolsets=catalog,orders,promotions. A name that does not exist is answered with a 400 that lists the ones that do. Every tool is in Commerce tools, with what it does and the endpoint behind it.

When Claude connects, the server tells it which toolsets and presets exist and how to ask for them, so it can tell you when it needs one you did not load.

What a tool is

Each tool is one operation of the API, with the same name and the same parameters. Two things are not parameters, because Claude never chooses them: the store (it is the store-id you connected with) and the user.

The server marks every tool for the client:

• Read tools change nothing.
• Write tools add or update, without removing what was there.
• Replace tools overwrite what was there. For example, the tool that syncs the assets of a product replaces the whole list.
• Delete tools remove data.

A client uses the marks to decide what to ask you about before it acts.

How Claude creates a product

A product with sizes and colors is made in one operation, so it is complete or it does not exist. Claude does it in three steps:

1. It lists the options (the axes, such as Size and Color) and the tag values (the values, such as S, M, red) the store already has.
2. It creates what is missing: the option, the tag and the tag values.
3. It creates the product with a single call (create_product_aggregate): the product, the option values it uses, and one variant for each combination, each with its price, its stock and its own combination of values.

If a variant names a combination that the product does not have, the whole call fails and nothing is created.

Permissions

The tools use the key you connected with: a request the key is not allowed to make is answered by the API with an error, and Claude tells you. The server does not widen what a key can do. For the same reason, a key for an assistant that only reads products should have only the read scopes of products.

What is not there

• Uploading files. Images and videos are uploaded with the Core API. Claude can use an asset that is already uploaded.
• The storefront. Cart, customer login, addresses, wishlist and the customer's orders are for your customers' browsers, not for an administrator.
• Old operations. The v1 checkout hooks and /cart/total are deprecated and are not offered.