v0.7.0

Agents can translate entries on multilingual sites, and MCP gets its own place in the Control Panel.

Highlights

Translate an entry into another site. entries_localize adds an entry to another site of its collection, the way the Control Panel's Localize action does. The new entry is a draft localization. It inherits every field it doesn't override, data holds its own values such as a translated title and content, and slug defaults to the origin's. On a structured collection it joins the target site's tree under the localization of the origin's parent. It needs the edit permission for the origin entry and access to the target site, and it exists on multisite installs only.

Agents see what each site has. entries_get, entries_create, and entries_localize return localizations, the id and status of the entry in each site you can access, or null where it has none. On multisite, statamic_overview lists each collection's sites, propagate, and origin_behavior, and blueprints_get marks each field localizable or not, so an agent knows what it can translate before it writes. entries_update now refuses a localization's own value for a field that isn't localizable, as the Control Panel does, and names the origin entry to change instead.

Tools → MCP in the Control Panel. MCP has its own item under Tools, with Guidelines and Connections listed under it in the sidebar like the Utilities pages. Connections is the old MCP Access utility, with your tokens and OAuth connections. Guidelines holds the site's voice and tone and the rows on how a collection's entries are put together. Only super admins can open it.

Guidelines move out of Globals. The guidelines global set sat next to the site's content, so editors took it for website content, and any agent acting as a super admin could rewrite it through globals_update. Guidelines now live in Statamic's addon settings, in resources/addons/statamic-mcp.yaml or the database. Agents read them through statamic_overview and blueprints_get as before, a row switched off on the page no longer reaches them, and no tool writes them.

mcp:guidelines moves 0.6.0 guidelines. The command no longer creates a global set. It moves the old one to the Guidelines page, prints the page's URL, and lists the page builder blocks without instructions as before.

The Boost skill sends coding agents to the Guidelines page or its YAML file.

Breaking changes

• Guidelines no longer live in the guidelines global set. Agents read the set only until php please mcp:guidelines moves it, as described below. The guidelines config key is gone, and no tool writes guidelines any more.
• The Guidelines page rejects {{, Antlers and Blade component tags, and @props, @aware, and @cascade, because Statamic runs addon settings through Antlers every time it loads them. Describe such a tag in words.
• The MCP Access utility and its permission are gone. Its page is Tools → MCP → Connections, which needs Access MCP, so a role with Access MCP alone can now issue its own tokens. OAuth mode already let those users connect themselves.
• Published copies of utilities/mcp-tokens.blade.php no longer apply. The page is mcp/connections.blade.php.

Upgrading from 0.6.0

1. Update the package: composer update danielgnh/statamic-mcp
2. Move the guidelines: php please mcp:guidelines. Run it where the content lives, locally on a flat-file site or in production when globals live in a database. It copies the guidelines global set to Tools → MCP → Guidelines, then deletes the set and its blueprint. Until you run it, agents keep reading the set and the Guidelines page shows a notice.
3. On a flat-file site, commit resources/addons/statamic-mcp.yaml and the deleted set files.
4. If the command says the set stays, follow its message. It keeps the set when the Guidelines page already has guidelines, when the set's text holds template code, or when the set's other sites hold text, which 0.6.0 never read.
5. Delete the guidelines key from a published config/statamic/mcp.php.

Full changelog: v0.6.0...v0.7.0