Loam does not ship an assistant. It gives yours a door: the MCP, with a key per actor and rights per key. Your agent reads the site, stages changes as drafts and publishes when you say so.
Agents that can use a shell work over SSH and git instead. Either way, every change lands in the journal under the name of whoever made it.
Just say it.
- “Set the opening hours on the contact page to 9 to 5.” The text is there, the structured data search engines read matches it, and the change is recorded with exactly what changed. Undoing it is always an option.
- “Write an article about the new coating, in our tone, and add it to the overview.” Page, data, its place in the overview and its findability — handled at once, because the structure is fixed and the tone is on record.
- “Add a page for the branch in Breda.” A new page, in the menu and in the sitemap. No template to pick, no fields to fill in, no forgotten setting that surfaces later.
Full with Claude, and works with the rest.
Every assistant can read a loam site. Managing it just by asking works most fully in Claude today; the others can too, with a detour. And as the owner you always keep full control on the server, with whatever tool you like.
| Claude | ChatGPT | Gemini | Copilot | |
|---|---|---|---|---|
| Read your site and think along | Yes | Yes | Yes | Yes |
| Manage it just by asking | Yes | Partly* | No** | Partly*** |
| From your phone | Yes | Partly* | No | No |
| Without technical know-how | Yes | No* | No | No*** |
| Full control as the owner | Yes | Yes | Yes | Yes |
* ChatGPT reads in the chat; managing goes through a server connection or a business account. ** Gemini has no connection in the consumer app yet; through the command line it works. *** Copilot works from the code editor, built for developers.