Edit your website copy from Claude, Cursor or ChatGPT with MCP

You already ask an AI assistant to rewrite copy. Then you copy the result, open your CMS, find the field and paste it in. With an MCP connector the assistant can do the last part itself: read the live page, propose the change and save it once you say yes.

What MCP is, in one paragraph

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to other tools. A tool publishes a small set of actions — “list my sites”, “read this page”, “save this text” — and any assistant that speaks MCP can use them, with your permission. Claude, Claude Code, Cursor and ChatGPT all support MCP connectors, so one connector works across the assistants your team already uses.

Why connect your website to your assistant

The copy work is already happening in the assistant. What's missing is the last step. With a connector, the assistant can:

For developers it's handy in a different way: in Cursor or Claude Code, the site's copy sits next to the codebase, so you can fix a typo on the live site without switching tools or redeploying.

Connect in a minute

The Vibe Editor connector is a single URL: https://vibe-editor.app/api/mcp. There's no key to copy — the first time you use it, you sign in to Vibe Editor and choose which sites the assistant may reach.

Claude Code

claude mcp add --transport http vibe-editor https://vibe-editor.app/api/mcp

Then run /mcp, pick vibe-editor and choose Authenticate. Approve in the browser and you're connected.

Cursor

{
  "mcpServers": {
    "vibe-editor": { "url": "https://vibe-editor.app/api/mcp" }
  }
}

Put that in .cursor/mcp.json, reload Cursor, and click the login button next to vibe-editor.

Claude and ChatGPT

Add a custom connector and paste the URL. You'll be asked to sign in to Vibe Editor and approve. Tools that can't sign in can send a key from your account page instead. All the options are on the MCP page.

What the assistant can do

The connector works on sites whose edits Vibe Editor keeps on top of the page — such as sites using the one-tag embed. Ask the assistant to run list_sites to see what your connection reaches. It has six tools. Four only read:

Two change what visitors see, and publish immediately — so the assistant is told to confirm the wording with you first:

An example session

You: Make the main heading on my site friendlier.
Assistant: (reads the page) The heading currently says “Quality that lasts — day after day, year after year”. How about “Made for everyday life — every single day”? Shall I publish it?
You: Yes, go ahead.
Assistant: Saved and live.

Prompts that work well: “list the fields on the pricing page and point out anything vague”, “suggest a shorter version of every heading on the home page, don't save yet”, “revert the change you made to the contact page”.

Safety: a key, not the keys

The connector is an extra way in, not a replacement. The edit switch on the page still works as before — use it when you want to see a change in context, and the assistant when you want to work across many pages at once. For tips on the instructions themselves, see how to edit your website with AI.

Keep reading

How to edit your website with AI: a practical guide

What AI editing is good at, the instructions that work, and how to keep a human in charge of what gets published.

5 min read

Add inline content editing to a Next.js site

Give editors click-to-edit on an App Router site while you keep your auth, your database and a strict field allow-list.

4 min read