Connect Claude to Webround

MCP (Model Context Protocol) lets an AI assistant such as Claude use a service through a set of tools. Webround has two MCP servers, one for what you sell and one for the site itself. Connect Claude to either and ask it for what you want in plain language: it calls the same operations the dashboard and the editor use, with the permissions of the key you give it.

Server	What Claude can do	Address
Commerce	Products, variants, collections, orders, promotions, shipping, taxes, store settings, and more: the store	https://ai-api.webround.com/mcp
Editor	The code and content of a site: pages, sections, texts, SEO, theme, styles, comments, files	https://<draftId>-render-v2.webround.net/__wr/mcp

You can connect both at the same time. They are independent: each has its own key.

What you need

• An API key with the permissions you want Claude to have. Create it from the dashboard (see API Keys). Claude can do exactly what the key allows and nothing more, so give it only what the task needs.
• A client that talks to a remote MCP server (Streamable HTTP) and lets you set request headers. Claude Code does.

Both servers authenticate with the same kind of header on every request:

Authorization: Bearer <your API key>

Connect with Claude Code

Add a server with claude mcp add. Each server's page has the exact command for it:

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

To share the setup with a team, put it in the project's .mcp.json file instead, and keep the key in an environment variable:

{
  "mcpServers": {
    "webround-commerce": {
      "type": "http",
      "url": "https://ai-api.webround.com/mcp",
      "headers": {
        "Authorization": "Bearer ${WEBROUND_API_KEY}",
        "store-id": "<your store id>",
        "user-id": "<your user id>"
      }
    }
  }
}

Never commit a key. Anyone who has it has the permissions you gave it.

What to ask

• "Create a product 'Nike sport T-shirt' at 19.99 €, sizes S, M and L, colors red, blue, green and black, with 10 pieces in stock for each variant."
• "Which orders from this week are paid but not shipped?"
• "Add a 15% promotion on the 'Summer' collection until the end of the month."
• "On the home page, change the title of the first section to 'New arrivals' and write the English version."
• "Check the SEO of every page and fix what is missing."

Claude reads before it writes. The servers tell the client which tools only read and which take something away, so a good client asks you before it deletes or replaces something.

Good to know

• Permissions are the key's. If the key cannot do something, the API answers with an error and Claude tells you. Create another key with the scope it needs.
• Nothing is remembered between requests. The servers keep no session: every call stands alone.
• One server, one store. The commerce server works on the store whose store-id you send, the editor server on the draft in its address. A draft and its store share the same ID.