ChEddi
ChEddi is an AI assistant that lives inside the TYPO3 backend. On every backend page a chat area can be opened through a floating button. Editors describe there in plain language what they need, for instance “translate this page into English” or “which pages have no image?”.
ChEddi works with the permissions of the logged-in user. All changes made land in a draft workspace by default, so they stay invisible to visitors until you publish them.
Beta version
ChEddi is in active development and currently at beta stage (version 0.2.2). The feature set and the internal interface are settling down, but smaller changes between minor versions are still possible. Pin a fixed version and review the changelog before an update.
Connection to AI Suite and MCP
ChEddi is not a standalone extension, it builds on two others. Composer installs both along with it:
- AI Suite provides the infrastructure, the permission model for backend groups, the TYPO3 compatibility layer and the shared services. See AI Suite.
- AI Suite MCP provides the tool registry. ChEddi drives the same tools an external MCP client would use, only from inside the backend rather than from outside. See TYPO3 MCP + AI Suite.
One point that matters for understanding it: the chat never talks to an AI provider directly. Every turn goes to the AI Suite Server, which holds the credentials and runs the model.
MCP straight in the backend
Driving TYPO3 through the MCP server and using the AI Suite features while doing so has been possible for a while. Until now it took an external client though: Claude Desktop, Claude Code or another tool that connects to your TYPO3 instance. That means setting up a client, creating a token, and switching between two programs all day.
ChEddi brings exactly that functionality into the backend. Same tools, same permission checks and same write paths as with the MCP server, only without the detour through a second program. No client, no token, no window switching. You stay in TYPO3 and have the chat right where you are working anyway.
Typical tasks
- find, read and have pages, content elements and files explained
- create and change content, page trees and metadata
- translate pages and content into the languages of this website
- create content from an attached document, for example from a PDF
- search your records and answer questions about them, such as which pages have no meta description yet
- look things up on the web when needed and supply the sources used, provided your backend group may use web research
Because ChEddi uses the tools of the MCP server, it can essentially do everything an external AI client can do on your instance. The list of tools is under Available Tools.