Sulu MCP Bundle 1.0.0-RC4: No client to create. No session to share.

With Client ID Metadata Documents (CIMD), an assistant identifies itself with a URL instead of a pre-registered client. Sulu looks up the assistant's name there and shows it on the consent page, together with the host it came from.

What this means for you:

• No client to create. You approve the assistant on the consent page, and nobody has to hand out a secret.
• You see who is asking. Assistants from claude.ai and chatgpt.com are shown as they are. Every other one is marked not verified.
• Your server stays in control. Sulu only looks up a client when a signed-in user connects it, and it does so within strict limits.

RC4 works with claude.ai, ChatGPT, Claude Code, Codex, and Mistral Vibe. Assistants that don't use CIMD yet keep connecting the way they did before.

How we made it safe to fetch a URL someone else chose is a story of its own. It follows in this series.

• Choose how assistants register. CIMD and Dynamic Client Registration each have their own switch. Turn off one, or both. Clients you create by hand with sulu:mcp:create-client keep working either way.
• Scopes on every request. Sulu now checks for each request whether the token is allowed to call tools or read resources, not only whether it is valid.

Either way, every assistant still works with the Sulu permissions of the person who connected it. Nothing more.

Assistants on the new protocol revision no longer need a session. This means any server behind your load balancer can answer any request. No sticky routing, no shared session store. Assistants on older revisions keep working as before.

• Safer approvals. Every tool now tells the assistant whether it only reads, changes, or deletes, so assistants that ask before risky actions know when to ask.
• Links to review. Agents can hand you a direct link to the page, article, or media item they worked on in the admin interface.
• More page settings. Agents can set up links and shadow pages, with the same rules as the admin form.
• Products in search. Content search now covers pages, articles, and products in one call. The Product Bundle is in Beta.
• Stricter permissions. Deleting content needs the delete permission in every locale of that content.
• Extension points for bundles that want to add their own content types or risky tools.

1. New database table. CIMD is on by default and needs the table sulu_mcp_cimd_client. Create it before you deploy, or assistants that switch to CIMD can't connect.
2. type is now resourceKey. The content tools take resourceKey with plural values (pages, articles, snippets, products). Assistants pick this up on their own. Update your own prompts and scripts if they send type.
3. Product tools moved to the Product Bundle. The Product Bundle (Beta) brings its MCP tools itself, starting with its first release.
4. Deleting checks every locale. A user who may delete in one locale but not in another can no longer delete the content through MCP.

RC4 is the fourth release candidate on the way to 1.0 and replaces RC3. It requires PHP 8.2 or newer, Symfony 7.3 or 8.x, and Sulu 3.0 or newer. The bundle stays MIT licensed, like Sulu itself, and does not require Sulu.ai.

Then replace type with resourceKey in your own prompts and scripts. All settings and the security setup are in the configuration guide.