AI + Total CMS vs Just AI
A coding agent can edit any file you point it at, and for some sites that genuinely is all the CMS you need. The question isn't whether to use AI — it's what your agent works against. It can read loose files and infer how the site works, or it can read a system that says exactly what exists and what it's allowed to change. Same agent either way. What sits underneath is what changes.
- Choose Just AI if you built the site yourself, edit it alone, and review every change.
- Choose Total CMS if someone other than you will edit the site after it ships.
The short answer: an agent with Total CMS beats an agent alone on any site that someone other than you will edit, that reuses content across pages, or that you won't review change by change. For a small site you built yourself and edit alone, an agent and plain files are enough.
The difference is what the agent has to work from.
Pointed at a folder of files, an agent has to guess. It reads the markup, works out the structure, and usually guesses well — but when it's wrong, it's wrong with full confidence, and nothing in the files pushes back.
Connected to Total CMS, an agent doesn't have to guess. The built-in MCP server tells it this install's real schemas and content, plus documentation matched to the exact version running, down to every Twig function's signature. Agent writes go through the same validation as the admin, each one is kept in undo history, and an agent connected through a user's account gets only what that user's access groups allow. Writes need Pro, and every Pro feature is free while you build on a local development domain.
That matters most at handoff. Your client won't be prompting an agent and approving diffs; they need an admin with clear fields and a design they can't accidentally undo. A rule like "don't touch the layout" in a prompt is a request. In Total CMS, you decide what's editable, and access groups enforce it, for your client in the admin and for any agent connected through their account.
AI alone is the simpler setup, and for the right site that simplicity wins. But the better your agent gets, the more it benefits from something real to read. And nothing about ownership changes: your content stays plain files on your own server, with no database and no subscription. It's just files. Your agent can read them, and nobody can take them.
Which to choose
Where each one wins.
When to choose Just AI instead
Plenty of sites don't need a CMS, and an agent working on plain files is a perfectly good way to run them. Choose AI alone if:
- You built the site and you're the only one who edits it. Nobody else needs an admin, so there's no reason to have one.
- The site is small and mostly static. A handful of pages with little repeated content gives an agent very little to get wrong.
- You review every change. If you read each diff before it ships, you are the validation layer, and that works.
- You want zero setup. No install, no license, nothing to configure. Describe the change, check it, publish.
When Total CMS fits better
An agent with Total CMS is the better fit when:
- Someone other than you will edit the site. Your client gets an admin with clear fields; your agent gets the same content over MCP. Both work on one source of truth.
- Your design needs to survive the handoff. You decide what's editable, and access groups enforce it, for your client in the admin and for any agent connected through their account.
- Content appears in more than one place. Structured objects are written once and rendered everywhere, so nothing drifts out of sync.
- You want your agent reading facts, not inferring them. Real schemas, real content, and Twig signatures for the exact version you're running come straight from the install.
- You want ownership without giving up structure. Content stays plain JSON on your own server, with no database and no subscription.
Feature by feature
Total CMS vs Just AI, row by row.
| Feature | Total CMS | Just AI |
|---|---|---|
| More | ||
| How the agent learns the site | Reads live schemas, content, and version-matched docs over MCP | Infers structure from the files it can see |
| An agent working from files is reconstructing intent from markup. Total CMS reports what this install actually contains, and its bundled docs tools return the exact Twig signatures for the version installed, so there is nothing to reconstruct. | ||
| MCP server for AI agents | Built in — public read (Standard), full access (Pro) | None needed; the agent edits files directly |
| On Standard, an anonymous agent can read the collections you mark public. Admin access — schemas, the bundled docs tools, and writes — uses an API key or OAuth, both Pro. Every Pro feature is free on local development domains, so your agent gets full access while you build. | ||
| Who can edit after launch | Clients and staff in the admin; agents over MCP | Whoever can run the agent and review its changes |
| The files-only approach assumes the person editing is comfortable prompting an agent and reading a diff. Most clients aren't. | ||
| Admin interface | Included, server-rendered (HTMX) | None |
| Permissions | Access groups, for people and for agents connected as a user | Whatever the prompt asks; the agent can change any file it can reach |
| Instructions in a prompt are followed most of the time. An agent connected through a user's account can do exactly what that user's access groups allow, every time. A developer's admin API key has full access, just as an admin login does. | ||
| Content modeling | JSON schemas | None; content lives in page markup |
| Without a model, content shown in several places — a price, a bio, an address — exists as several copies, and an agent updates the copies it finds. | ||
| Validation | Enforced on every write, human or agent | Applied when the agent remembers to |
| Required fields, image dimensions, and allowed file types are checked by the system, not left to judgment. | ||
| Undoing a bad change | Undo history on every save, human or agent | Version control, if the site is in a repo |
| Both can roll back a bad edit. Total CMS keeps recent versions of every record automatically, restored with tcms backup:restore, with nothing to commit first. | ||
| Content storage | JSON or Markdown files on disk | HTML and other files on disk |
| A tie on ownership: both keep content as plain files on a server you control. | ||
| Database | None, ever | None |
| Setup | Drop the tcms folder on any PHP host | Nothing to install |
| AI alone genuinely wins on setup. There is nothing to configure because there is nothing there. | ||
| Price | $195 Standard / $395 Pro (one-time) | Your agent subscription only |
| You pay for your agent either way. Total CMS adds a one-time license per domain, not another subscription. | ||
Questions
Common questions.
If I use a coding agent, do I still need a CMS?
Not always. If you built the site yourself, edit it alone, and review every change, an agent and plain files can be enough. A CMS earns its place when other people edit the site, when content repeats across pages, or when you want rules enforced rather than requested.
What if the client wants to log in and make updates?
Some developers simply say no, and for some clients that holds. But most clients eventually want to fix a typo or swap a photo without filing a request, and a site they can't touch is a reason to look for another developer. Total CMS gives them an admin showing only the fields you choose to expose, so they can edit content without ever reaching the layout.
Can't I just build a simple login page for them?
You can, but why reinvent the wheel? An agent will write the first version in an afternoon. Every version after that is yours to maintain: auth, password resets, uploads, validation, and security fixes, on every client site you've shipped one to. A CMS that already does the job means someone else carries that work.
What about letting clients send change requests to an AI agent?
That works, and it's exactly where structure matters most: a bot that ships changes without a person reviewing each one needs limits it can't talk itself past. With Total CMS Pro, a client can connect Claude to the site through their own login. The agent gets only what that client's access groups allow, every write is validated, and every change is kept in undo history. There's no request queue to build, and no bot with access to every file.
Wouldn't a lighter CMS than WordPress be enough?
Often, yes, and that's the right comparison to make. Total CMS is that kind of lightweight: no database, just a folder on any PHP host, with content stored as plain files you own. Sanity keeps your content in its hosted service, and EmDash is a database-backed CMS for Astro. Our EmDash and WordPress comparisons cover those tradeoffs in detail.
Does Total CMS replace my coding agent?
No. It gives your agent something real to work against. Connect Claude Code, Cursor, or Windsurf to the built-in MCP server, and your agent reads your actual schemas, content, and the Twig signatures for your installed version instead of guessing.
Which edition do I need for agents?
Standard lets anonymous agents read the collections you mark public. Pro adds API keys and OAuth, which give an agent admin access or a specific user's access, including writes. Writes go through the same validation as the admin, and an agent connected as a user gets only what that user's access groups allow. Every Pro feature is free on local development domains such as localhost and .test.
Does adding a CMS mean giving up control of my content?
Not with Total CMS. Content is stored as JSON or Markdown files on your own server, with no database and no service that has to stay reachable for your site to work. The license is one-time per domain.
How can I try it with my agent?
Total CMS is free with every Pro feature on local development domains such as localhost and .test, and there is a 45-day trial with full Pro features and no credit card.
Sources
Where these facts come from.
Just AI facts checked .
This page compares an approach — a coding agent editing site files directly — rather than a specific product, so there are no competitor claims to source.
- Total CMS MCP server — what agents can read and write, by edition
- Model Context Protocol — the open standard the MCP server implements
If you think we've represented the agent-only approach unfairly, tell us and we'll correct it.
Keep comparing
Weighing something else?
- Hosted vs self-hosted Before you choose between Squarespace and Webflow, or between Kirby and Craft, there is a bigger question underneath: do you want to rent a website platform or own the software that runs it? Here is how to decide, from someone with an obvious stake in the answer.
- The best flat-file CMS in 2026 Five flat-file content management systems worth your time, what each is genuinely good at, and where each one will frustrate you.
- A PHP CMS without a database Running a CMS with no MySQL sounds like a corner-cutting exercise.
- WordPress alternatives for freelancers If you build client sites for a living, the CMS decision is really a decision about the next three years of your evenings.
- Making a PHP app legible to AI agents Coding agents invent functions that don't exist because the app can't describe itself.
Try it against Just AI on a site of your own.
45 days, every Pro feature, no credit card.