Try now
Model Context Protocol

Edit your site from your AI

Point your agent at one URL and it can read and rewrite the copy on your site — the same edits the bubble makes, without opening the page.

✓ One URL, no install ✓ Scoped to one site per key ✓ Every change reversible

Your connector URL

…

Paste it into your AI tool. The first time, it sends you to Vibe Editor to sign in and choose which sites it may reach — there is no key to copy. Tools that can't sign in can send a key from your account page as Authorization: Bearer vibe_….

1

Add the connector

One command. There is no key to copy.

…
2

Sign in

Run /mcp, pick vibe-editor and choose Authenticate. Vibe Editor opens in your browser: approve, and it is connected.

3

Start editing

Ask it to list your sites, then to change some copy. It reads the live page, so it sees what visitors see.

1

Add it to .cursor/mcp.json

Drop this into your project, then reload Cursor.

…
2

Sign in

Cursor shows a login button next to vibe-editor. Click it and approve in the browser.

3

Start editing

The Vibe Editor tools show up in the agent panel alongside your codebase.

1

Add a custom connector

In Claude or ChatGPT, add a custom connector and paste the URL above. You will be asked to sign in to Vibe Editor and approve.

2

Or send a key

Clients that can't sign in can send a key from your account page as a request header.

…
3

If it can't set headers

Some clients only accept a bare URL. Use the option there — it takes the key from the environment instead.

1

Get an API key

Same key as the hosted route — it works for both.

Open my account
2

Run the server locally

A single file from the repo, Node 18 or newer, no dependencies and no build step.

…
3

Same tools either way

Both routes share the same tool code, so behaviour is identical. Running it yourself just keeps the connection on your machine.

The floating bubble still works exactly as before — the MCP is an extra way in, not a replacement.

What your agent can do

Six tools, one API key

Read

Find out what's there

Nothing here changes your site.

  • list_sitesThe sites this key may reach. The usual starting point.
  • list_fieldsReads the live page and lists every editable text with the id that addresses it.
  • get_editsThe edits already saved on top of the page source.
  • suggest_textAsks the AI for a rewrite and shows it — without saving anything.
Write

Change what visitors see

These publish immediately, so agents are told to confirm the wording first.

  • set_textSaves new text for one field, live for every visitor.
  • revert_textDrops a saved edit so the element falls back to the page source.

Edits that survive a redesign

A field is addressed by its text, not its position — so an edit follows the element when a developer moves it later.

How it works

Ask once. It ships.

Your agent
Make the main heading on my site friendlier.

Let me see what's editable there.

list_fields · 119 fields found

The heading currently reads “Kvalitet som tåler hverdagen – dag etter dag, år etter år”. Here's a warmer version — shall I publish it?

Yes, go ahead.
set_text · 1 field

Saved and live.

Result
Before

Kvalitet som tåler hverdagen – dag etter dag, år etter år

After

Laget for skolehverdagen – hver eneste dag

Saved to your site · visible to everyone

Safe by default

Your agent gets a key, not the keys.

  • One site per key. Bind a key to a site and it can reach nothing else. Revoke it any time from your account.
  • The server decides, not the agent. Every call is authorised against that key, so a wrong guess is refused rather than obeyed.
  • It only reads your own pages. The hosted connector will fetch a page only on the site's own domain.
  • AI keys stay server-side. The connector never sees your Claude or OpenAI key.
  • Everything is reversible. Edits are ordinary saves — revert_text puts the original back.

Edit your site from wherever you already work.

Try now See the editor ↓