Webround Editor MCP

Every draft is a site made of real code (a React and Vite project) that the editor and Claude work on together. The editor MCP gives Claude the same operations the editor uses, so it can read a page, change a section, write the English version of a text, set the SEO or the theme, and check the result in a browser. Every change goes through the same guardrails as the editor's: it is the code that changes, and the editor shows it.

Each draft is an MCP server of its own, at the address of its site:

https://<draftId>-render-v2.webround.net/__wr/mcp

It speaks Streamable HTTP, without sessions.

Connect

You need an API key of the store with the site:update scope. A key with only site:read is not enough: every tool of this server, even those that only read, needs site:update. Create the key from the dashboard (see API Keys).

With Claude Code:

claude mcp add --transport http webround-editor "https://<draftId>-render-v2.webround.net/__wr/mcp" \
  --header "Authorization: Bearer <API key>"

The server asks the Webround core who the key belongs to and whether it may work on that draft, exactly as it does for the editor. Nothing else is needed: no other headers.

A few rules of the server:

• A request that carries an Origin header is refused: this endpoint is for tools, not for web pages.
• A message can weigh up to 64 KB.
• If the draft's container is asleep, the first request wakes it and waits for it, up to 90 seconds; after that the answer is a 503 with Retry-After.

What Claude can do

The tools are in Editor tools, with the parameters of each. In short:

Area	What it is
Pages and content	List, create, delete and update pages. Read a page as a tree of elements, and everything on it that is translated, with the languages that are missing.
Elements	Read, change, insert, delete and move an element of a page. Insert ready-made blocks from the editor's catalog or your own markup, and duplicate an element by reading its source.
Languages	The languages of the site, and each text in each language.
SEO	Title, description, pictures and social texts of every page and of the whole site; a title and description suggested from what the page says; robots.txt and the sitemaps; the pages a build prerenders for search engines.
Theme	Colors, spacing, Google and custom fonts, and the dark theme.
Styles	Read and set the style of an element for each screen size and state (hover, focus…); copy a style between screens; shared styles you can apply to many elements.
Comments	The comments the editor shows on elements. Claude can read the open ones as its to-do list, act on them and mark them resolved.
Files and packages	Read and write the site's files, and add or remove the packages it depends on.
Kits	Start from a ready-made set of pages, such as the shop.
Checks	Check the code (accessibility, headings, links), open a page in a browser to see the errors a visitor would hit, take a screenshot, and get everything that is wrong in one answer.

What to ask

• "Make the hero of the home page shorter and put the call to action on the right."
• "Translate the whole About page into English and French."
• "Write the title and the description of every page for SEO."
• "Change the primary color to a dark green and check that the buttons are still readable."
• "Open the shop on a phone and tell me what is broken."

Claude can check its own work: after a change it can look at the page and read the errors. Ask it to.

Good to know

• Comments are the easy way to ask. Leave comments on the elements you want changed, in the editor, and ask Claude to work on the open ones: it reads them, does what they ask and marks them resolved.
• A tool that takes something away says so. The server marks deletions (destructiveHint), so your client can ask before it deletes a file, a page or an element.
• One connector for each draft. Add a server for every site you want Claude to work on.