WebEditor.clickby IndigoStudio.cz CS Try it on TestFlightTestFlight

Point at your site. Say what should change.

A web editor that turns a tap on an element and one sentence into a precise request for your own coding agent, with the selector, the styles, the surroundings and the system the site runs on.

Try it on TestFlight Chrome extension
With the crosshair you mark an element right on the page, then say or type what should happen to it.

One sentence. The rest is read off the page.

You don't need to describe which element you mean or look for it in the source code. Your sentence is passed on exactly as you said it, and the editor adds what it can see on the page and the agent cannot. Anything it cannot confirm from the page is left out, because an uncertain detail costs the agent an extra round.

Sample. Real values are read from the rendered page.
No.What the agent getsExample
1

Sentence

Passed on exactly as you said it. Nobody translates it.

“make the heading bigger”
2

Anchor and selector

Still match the element after the page re-renders.

h1.hero-title
main > section:first-of-type h1
3

Applied styles

Only the ones that actually apply to it.

font-size: 32px
font-weight: 600
line-height: 1.2
4

Surroundings and size

Neighbours, size and position in the viewport.

252 × 32 px, 136 px from top
above p.lead
5

Element crop

An image via the share sheet and in the zip, over MCP as a link.

heading.png
6

The site's system

When it can be identified from the page: WordPress, Shopify, Shoptet, Webflow, Wix.

WordPress 6.6

From pointing to a finished change.

  1. Open your site

    In the editor on the iPhone, or in Chrome with the extension.

  2. Point at an element

    With the crosshair or your finger, right in the page.

  3. Say what to change

    Type or dictate a sentence. The request is added to the list.

  4. Hand it over

    Clipboard, zip, share sheet, or the remote MCP.

  5. Check it

    The agent edits your source code. Reload the page to see the result.

Start with the site address at the top. Then point at an element of the site, select it and write what you want to change. Share the finished request, or download it as a ZIP.
BThe app — how it works

The iPhone app is a browser with the core running inside the page: select an element with your finger, dictate the sentence. Transcription runs on the phone and no audio leaves it.

In Chrome the extension does the same: open the palette with the toolbar icon or ⌘⇧E, pick an element with the crosshair, and Enter adds the request and copies the whole list. You decide how many requests to collect before you hand the list over.

One address. Your agent picks the requests up itself.

The clipboard, the zip and the share sheet work without any setup or consent, and nothing passes through our server.

To send requests to your agent directly, turn on sending in the app's Connections section and copy the MCP address from there. Paste it once into your client (Claude Code, Codex, Cursor, VS Code, Windsurf, Zed, Cline) and the agent reads the requests and ticks them off itself.

Claude Codeclaude mcp add --transport http webeditor <address>
Codexcodex mcp add webeditor --url <address>
Cursor, VS Code and others{ "mcpServers": { "webeditor": { "type": "http", "url": "<address>" } } }

The address starts with https://mcp.webeditor.click/s/ and carries the key to your list. It is a secret, not a login. No account, nothing to install.

You select an element of the site and say what should change. Once sending is on, the request lands in the MCP mailbox. Your agent picks it up, edits and deploys the site. You check the change by reloading the page.
CThe app — sending over MCP

Received a request headed “Request from the browser (WebEditor.click)”? Someone pointed at an element of a page and said what should change. The selector, styles and surroundings are read off the rendered page, not the source code. Verify them in the code.

What the editor never does.

  1. Never writes to your code and never connects to a Git repository.
  2. Never alters the page you are looking at. It only reads it.
  3. Calls no model — you pay for that at your own agent.
  4. Sends nothing on its own. Page content stays on your device.
  5. Never hosts or maintains anyone's website.
The only way data leaves

It goes through the remote MCP, and you switch it on. Only what you sent yourself travels that way, mainly the sentence, the page's address, what the editor read about the element (anchor, styles, surroundings) and the crop. The full list is in the privacy policy. We keep the list for one week after the last change, then it is deleted. Turning the switch off deletes it at once. We do not read it or learn from it.

Privacy policy

Also in Chrome. Manual install, for now.

For Chrome and the other Chromium browsers: Edge, Brave, Arc, Vivaldi. It isn't in the extension store yet, so you load it from an unpacked folder. It takes about a minute.

Download the extension (.zip)
  1. Unpack the zip into a folder you won't delete or move — the browser loads it at every start.
  2. Open chrome://extensions, in Edge edge://extensions, in Brave brave://extensions.
  3. Turn on Developer mode with the switch at the top right.
  4. Click Load unpacked and pick the folder.
  5. Open your website and call up the palette with the icon or ⌘⇧E (Ctrl+Shift+E).

To update: download the zip again, overwrite the folder's contents and click Reload in chrome://extensions. The developer mode warning shown when the browser starts is expected with a manual install. It goes away once the extension is in the store.

Get WebEditor.click.

The app for iPhone, iPad and Mac is awaiting approval in the App Store. Until then, you can try it through TestFlight. The Chrome extension is available right here.

Try it on TestFlightChrome extension

Send questions and feedback to info@indigostudio.cz.