Running a site
Assistants
People can work on the site from an AI assistant that speaks MCP. An administrator turns it on under Settings → Integrations → Assistants; the site's address must be https (or localhost while developing), and no page, content type or module may already use /mcp or /oauth.
To connect one, a person adds the address shown there (https://<site>/mcp) to their assistant as a remote MCP connector. The assistant opens the site, the person signs in, and a page asks them what it may do in each area:
| Area | View | Change |
|---|---|---|
| Content | pages, entries, terms, blocks, media, drafts included | write, publish and trash them |
| Structure | content types, taxonomies, templates | make and change them |
| Design | the theme, headers, footers, fonts | change and publish them |
| Settings & people | settings, people, roles, modules, activity | change settings, invite and look after people, set up modules |
| Code | custom CSS, site code, modules' source | write custom CSS, HTML and scripts, site code and modules |
An assistant never does more than its person's account can, and some things are never an assistant's: other assistants, API tokens, ways of signing in, secrets, emptying the trash, restoring backups and updates. Who may connect one is the connect_assistants capability (on for the administrator and editor roles).
- Seeing and ending them: everyone sees their own under Your account → Connected assistants, where they can change an assistant's areas or end it; administrators see every connection on the Assistants card. Turning assistants off ends them all.
- The record: every call an assistant makes is under Activity → Assistant calls (kept 180 days, adjustable on the card), and what it changed is in the activity log like anyone's work.
- Deletes: what an assistant deletes waits in Activity → Trash for 30 days.
- Alongside people: an assistant saves pages, parts, blocks and entries as it always has, even while someone has them open. Their editor is told ("Helper for Sam Jones saved a new version", as the activity log names it), and their next save asks what to keep rather than replacing the assistant's work (see Editing alongside others in Building sites). The assistant is not asked in turn: a page, part or block keeps every save, but an entry's values are simply replaced.
- Without a browser: an API token with assistant areas works at
/mcptoo, for scripts and builds.