MCP integration
Connect the editor you already work in and run the CMS by prompt. The agent connects repositories, reads what each client can edit, and stages changes. None of it reaches the live site.
No credit card, cancel anytime.
Benefits
Not at any permission level, and not on either connection. Publishing commits straight to a client's live site, so there is simply nothing for a model to call. It stages the work and stops.
Claude Code, Cursor, Windsurf and Codex. One command finds the ones on your machine, shows you the config before it writes it, and backs up anything it touches.
An agent's edit is resolved against the same field map a client's edit is. A field you locked stays locked, and the model picks from that map rather than writing code.
Each key carries a preset you choose when you mint it, enforced on the server rather than in the client. A key can never do more than the person who created it.
How it works
Pick a preset in the dashboard. The default one makes content edits and cannot publish, so the safe choice is the one you get without thinking about it.
One command writes the config for the clients you have installed. Or paste the hosted address and your key into any client that accepts a header, with nothing to install at all.
Connect this repository. Show me what my client can edit. Change the headline. Five tools cover the whole surface, and the agent picks between them.
The agent's changes wait in the dashboard alongside every other pending edit. You look at them and publish them yourself.
Use cases
Connecting ten repositories by hand is the same three answers, ten times. Describe the set instead and let the agent work through it.
Example
“Connect every repo in this folder and tell me which ones mapped cleanly” comes back with a framework and a field count for each site, and the ones that need a source root.
A client emails a correction while you are deep in something else. Ask for it where you are, and it lands as a draft like any other edit rather than pulling you into a browser.
Example
“Fix the pricing headline on acme” comes back with the field it matched, the wording it wrote, and any warning it raised on the way. The change waits as a draft until you publish it.
Before you hand a site over, ask what is open, what warns, and what waits for you. The answer is the site's real field map, not your memory of how you set it up.
Example
“What can my client edit on the acme homepage?” answers field by field: the wording each one holds today, and whether it is open, warns first, or waits for your review.
The requests your clients sent to your team, listed in the editor where you would do the work anyway.
Example
“What is waiting for me?” lists each request with the site it came from, the client's own words, and the reason it could not be self-served.
Pricing
Everything included. $39 a month for 5 sites, then $10 each.
50% off for 12 months
with code BREW50 for the first 20 customers (11 left)
Billed monthly.
Billed $312 yearly. Save 33%.
FAQ
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call