TYPO3 MCP setup: install AI Foundation and switch on the MCP server
The setup is three steps: install AI Foundation with Composer, switch on its MCP server, and connect your AI assistant with an OAuth sign-in. This episode runs them on our demo install and shows how to check each one before the first real job.
The prompt
Give me a quick overview of the pages on our website and the languages they exist in.
Read-only. A first check that the connection works
What does the assistant do?
- Install AI Foundation with one Composer command. No licence key, no registration.
- In the AI Foundation module, switch on the MCP server and look for the status Online.
- Copy the server URL ending in /mcp into your assistant and sign in with OAuth.
- Check the connection: the endpoint answers 401 without a sign-in, and OAuth Tokens lists your assistant.
- Ask a first question that only reads, such as an overview of your pages and languages.
How do I check it and put it back?
Nothing is written during the setup, so there is nothing to put back. To disconnect an assistant, revoke its entry under OAuth Tokens; to stop all access, switch the MCP server off again.
What do I need?
Composer access, a TYPO3 admin account and an MCP-capable assistant; AI Foundation is free.
What can the assistant not do for you?
- Ask the assistant to read the current value first, check the change on the page, and have it write the old value back; a records_apply batch can run as a dry run first and be taken back with records_undo.
- The assistant works with the rights of the backend user who signed in: on Live, its changes are live at once.
- What your assistant reads through MCP goes to the vendor of that assistant, as with any chat.
Questions about this episode
What does this video show?
The four steps of the setup on our demo install: install AI Foundation with Composer, switch on its MCP server, connect an AI assistant with an OAuth sign-in, and check that it answers.
How do I know the connection works?
The endpoint answers 401 before sign-in, OAuth Tokens in the module lists the connection afterwards, and a first read-only question gets an answer: 23.7 seconds on our demo install.
Who does the assistant act as?
As the backend user who signed in. On Live its changes are live at once, so pick that user's rights with care and end a connection under OAuth Tokens when you no longer want it.
Transcript of the video
- 0:00MCP in Practice for TYPO3 · Episode 3: TYPO3 MCP setup: install AI Foundation and switch on the MCP server
- 0:02One prompt, in your own words: the pages of our site and their languages.
- 0:04MCP gives the assistant tools. The row names the connector: AI Universe Demo.
- 0:07It read the page tree and the site languages. Nothing was changed.
- 0:10Two sites, English and German, with the pages that have no German version.
- 0:12Tents is one of them. We check it on the website.
- 0:14Now check the connection in TYPO3.
- 0:15MCP Server: status Online, the server URL, and Remote (OAuth) as the way to connect.
- 0:24A first connection opens a sign-in in your browser. You approve as a backend user.
- 0:32OAuth Tokens lists the assistant's connection, and you can revoke it.
- 0:34The core tools are free with AI Foundation. Extensions add licensed tools.
- 0:40English site: the menu has a Tents category.
- 0:45German site: no Tents category, as the assistant said.
- 0:5023.7 seconds from prompt to answer: the connection works.
- 0:52All episodes: t3planet.de/en/blog/typo3-mcp-in-practice/
Sovereign TYPO3 AI
AI Foundation for TYPO3T3AF
The base every extension runs on. Manage providers, prompts, permissions and costs in one place.
AI Assistant
AI Chatbot
AI Search
AI Accessibility
AI Localization
AI Builder