TYPO3 MCP Server & AI Connector
The Model Context Protocol is the open standard assistants use to reach outside tools. TYPO3 AI Agent acts as an MCP server for your TYPO3 site: the assistant asks it for a capability, it checks what you have authorised, and only then does it touch your site. This page covers the technical side for TYPO3.
Where this one stands
TYPO3 has no general-purpose content write API in its core. Work would begin with an extension of our own, and until one exists there is nothing to connect.
Authentication and permissions
The assistant authorises through OAuth 2.1 with PKCE, and is granted scopes rather than an open door. Your TYPO3 credential is encrypted at rest, tied to the one website it belongs to, and never sent to the assistant. Every operation is recorded, and an operation outside what you granted is refused before it reaches your site.
Common questions
What is an MCP server, in plain terms?
A service an AI assistant can call to do real work. Rather than describing a change to you, the assistant asks the server to make it. TYPO3 AI Agent is that server for TYPO3, and the boundary of what it will do is set by what you authorised.
Does the assistant see my TYPO3 password or token?
No. The credential is encrypted and bound to the single website it was given for, so a copy of it elsewhere is useless. The assistant asks for an action; it never receives the way in.
Is this an official TYPO3 product?
No. TYPO3 AI Agent is an independent product that uses TYPO3’s own published interfaces. It is not affiliated with or endorsed by TYPO3.
Getting started with TYPO3 AI Agent
TYPO3 AI Agent is not on sale yet. The product page tracks where it stands, and nothing is advertised before it works.