Potsdam • Berlin • Germany

16-18 October 2026

The proof of concept works. An AI client can talk to Joomla, read system information and purge the cache. Impressive for a demo, thin for a feature.

The MCP server sits in core, speaks Streamable HTTP and is written in PHP so it drags in no extra dependencies. What it can do today is deliberately small: one resource, one tool. The groundwork is done. The roadmap is not.

Next up is the part that makes it genuinely useful. An OAuth server for Joomla with proper MCP scopes, so the temporary token handling can go. A generic plugin wrapping the existing web services to expose articles, categories and users as CRUD operations. Plugins for everything that is not CRUD. Plus the unglamorous rest: backend cleanup, an installation script, automated tests.

We go through that list, decide what lands first and split it between the people in the room. Bring opinions about permissions. What an assistant must never be allowed to touch is the question that decides how far any of this can go.

Target Audience

Developers and integrators, plus everyone with a strong opinion on giving an AI write access to a CMS. Both camps are needed here.

Make it Happen Goals

A prioritised list of next steps for the MCP server, with names against them.