feelreef

REEF with MCP

Connect your AI to your site

Connect once and your AI can read and write this site directly — edit posts, change the layout, preview the result. It never needs your password and never touches your money. Whether it goes live is always your click.

https://mcp.feelreef.com/mcp

That one line is the whole thing. Below is where to paste it.

Adding it in an AI with connectors

Claude, Cursor, Codex, Antigravity and the rest all support remote MCP servers — they just each put it somewhere different. Find "add remote server" or "custom connector" and paste the line above. Nothing to install, and no GitHub account.

The older family (Gemini, Antigravity) speaks a different transport; there you fill in https://mcp.feelreef.com/sseinstead — same server, same tools.

After you paste it, your AI gets turned away once and a consent screen appears. That is normal, not an error. Read which sites are listed, press allow, and you are connected.

Adding it in Claude Code

One line, if you prefer the command:

claude mcp add --transport http feelreef https://mcp.feelreef.com/mcp

If you are on another machine, or connected over SSH, a browser cannot open there. Use this instead:

claude mcp login feelreef --no-browser

It prints a URL. Open it on your phone or any device, press allow, and feelreef gives you a link — copy that back into the terminal and you are done.

Once it is connected

Build a site, write posts, change the layout, swap the theme, upload images — then make a preview only you can see. It can also check its own work: measure the real layout, catch links pointing at pages that do not exist, confirm that what it is reading is the version it just built.

And where its limits are

  • It cannot spend your money.
  • It can retire a page, but never quietly: it has to say what happens to the address (a redirect, or an honest 404), and the content stays in your history — one call brings it back.
  • It cannot reach your payments, your domain or your other accounts. Site content only.
  • Every change is a version, so anything broken can be rolled back.

These three moments stay yours

Not a limitation — these were always yours to decide. Your AI can prepare each one; you are the one who presses it.

Authorizing
The first time it connects you see a consent screen listing which sites this AI may touch. Read it, then allow.
Paying
The card is yours. Prices live on /store; your AI will not and cannot charge it for you.
Your domain
DNS changes and the registrar's confirmation email land in your inbox. You are the one who clicks.

Hand this page to your AI

Everything above was written for you. /for/agents is the same thing written for it: the full tool list, how it should verify its own work, and which things it has to come back and ask you about. Hand it that address and it will know what to do.

You can remove this connection from your AI at any time. Your site and its content live in your own repo and are unaffected.