MCP is the standard way AI apps connect to other software. ContentForge runs an MCP server, so you can work on your clients from inside your own AI assistant (such as Claude or ChatGPT). You type what you want in plain words, and your assistant does it in ContentForge for you.
For example: "List my clients", "Add Acme Gutters in Austin as a client and start a blank site for it", "Add a Roof Repair page to Smith Roofing's site", "On Smith Roofing's home page, change the hero heading and add a call button under it", "Draft a blog post about storm damage", "Run a map scan for 'roof repair'", or "How did Search Console look for Smith Roofing over the last 28 days?".
Set it up
Pick the app you use. Each article has the exact steps:
- Claude.ai (custom connector, sign in with your ContentForge login)
- Claude Desktop
- ChatGPT
- Claude Code and other command-line tools
- Cursor and other apps that use an API key
Everything starts at Settings → API & MCP. Copy the MCP server URL from the Connect your AI card. Apps that can sign in use that URL and your normal ContentForge login. Apps that can't sign in use the URL plus an API key.
What it can do
- Read your clients, sites, pages, blog posts, collection items, social posts, press releases and reporting (Search Console, GA4, map scans, Zeus recommendations, backlinks, citations and keywords).
- Add a client, the same as Clients → Add client.
- Start a blank Mount Olympus site for a client, the same as Websites → New site → Start blank. It never designs or writes a whole site; Create with Zeus is only in ContentForge.
- Add a page to a site, like + Add page in the editor: its name, address, place in the menu, blank or a copy of another page, and its SEO title and description.
- Edit Mount Olympus site drafts: pages, widgets, header and footer, menu, popups and theme, with undo.
- Write blog post drafts, add collection items, and save social posts and press releases as drafts.
- Add images to a site's media library.
- Mark a Zeus recommendation in progress, executed or defied, and tick its steps done. Work marked executed this way is measured at 30, 60 and 90 days, just like work marked on the client's Zeus tab.
- Start Zeus and SEO tools (they cost credits, see below).
- Publish, but only if you allow it when you connect.
Site edits go to the draft, with undo. Nothing goes live until something is published. See Things you can do with MCP for example prompts for each job, and Example MCP workflows for longer jobs from start to finish.
Zeus and SEO tools (these cost credits)
Your AI assistant can start the same runs as the buttons in ContentForge, charged the same credits:
- Summon Zeus for a client (a Zeus scan with new recommendations)
- Zeus Ads Review (needs the client's Google Ads account linked)
- GBP Optimizer (Zeus reviews the client's Google Business Profile)
- Keyword research
- Local SEO audit of a website
- Backlink analysis of a client's domain
- Local map scan (charged per keyword)
- Citation audit
- Competitor check for one of the client's saved competitors
Every run asks first. Your AI assistant tells you what will run and what it costs, for example "This costs 3 credits", and only starts it once you agree. If there aren't enough credits it says so and nothing runs. Scans and audits that take a few minutes keep going in the background; ask your assistant how it's going and it gives you the results when they're ready. You can also ask it for your credit balance and the prices.
Everything else your AI assistant does is free. Only your agency can start these runs: client connections never get Zeus or anything that costs credits.
If the site has other languages that are live but not fully translated, publishing still happens, and your AI assistant tells you which ones, for example "Spanish is 80% translated — 3 pages still have English text".
Watch it work in the editor
Open the site in the Mount Olympus editor while your AI assistant works on it and you'll see each change appear as it's made. You don't need to refresh.
- The changed section lights up for a moment, and a note says who changed it, for example "Claude updated 'Our services'". When the app's name isn't known it says "A connected AI app".
- New, renamed or deleted pages, popups and blog posts show up in the editor's lists too. So do changes to the header, footer, menu, theme and collection items.
- Preview updates too. A shared preview link needs a reload.
- If you're in the middle of editing the same section, your edits stay. A small Updated elsewhere note appears on that section: Review shows both choices, Keep mine keeps your version.
- Undo in the editor only steps back through your own edits. To put back something your AI assistant changed, ask it to undo that change.
Who can do what
Your AI assistant acts as you. It only reaches the clients and tools your role allows, and only does what you ticked when you connected: Read, Write (drafts) and Publish. See MCP permissions explained.
Your clients can connect their own AI assistant to their own sites too, if you turn it on for them. See Client MCP access.
See and disconnect apps
On Settings → API & MCP, Connected apps (sign-in) lists every app you connected by signing in, with what it can do and when it was last used. Click Disconnect, then Yes. It stops working at once. Owners and Admins see every team member's connected apps and keys and can disconnect them.
Keys are listed in the keys table above it, with Revoke.