TYPO3 MCP clients compared: which AI assistant works with your TYPO3?
Which AI assistant should your team use with TYPO3? It depends on the plan your vendor offers, how the assistant signs in and what your admin can control. This episode compares eight assistants as MCP clients for AI Foundation, so you can pick one before you set anything up.
The prompt
Which pages are under Service on our website, and when was each one last changed?
Read-only. Ask it in two assistants: the same MCP tools, the same rights
What does the assistant do?
- Check that your assistant's plan includes remote MCP servers; the vendor names the plan.
- See how it signs in: most use OAuth, PhpStorm uses a token URL.
- Look at what your admin controls on the assistant's side and in AI Foundation's OAuth Tokens.
- Pick the setup guide for your assistant: Claude, Microsoft Copilot, Cursor or VS Code; ChatGPT, Claude Code, Gemini and PhpStorm were checked on our demo.
- Start with a question that only reads, such as which pages are under Service.
How do I check it and put it back?
Choosing an assistant changes nothing in TYPO3. A connected assistant can be signed out at any time under OAuth Tokens in AI Foundation, and it only writes what your backend user may write.
What do I need?
AI Foundation (free) and a plan from your assistant's vendor that includes remote MCP servers.
What can the assistant not do for you?
- Which plan includes remote MCP servers, and whether it includes write actions, is up to each vendor and changes often: check your plan on the vendor's own page.
- JetBrains AI Assistant documents no OAuth sign-in for MCP servers; PhpStorm connects through a token URL and mcp-remote, and a token URL works like a password.
- 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.
- 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?
How eight AI assistants connect to the one MCP server of AI Foundation in TYPO3: Claude, ChatGPT, Gemini, Microsoft Copilot, Cursor, VS Code and Claude Code sign in with OAuth, PhpStorm through a token URL.
Which plan do I need?
Which plan includes remote MCP servers is up to each vendor and changes often. Check your plan on the vendor's own page; the setup guide for your assistant names it.
Is a token URL as safe as OAuth?
A token URL works like a password: keep it private and end it in AI Foundation when you no longer need it. Assistants that sign in with OAuth do not need one.
Transcript of the video
- 0:00MCP in Practice for TYPO3 · Episode 4: TYPO3 MCP clients compared: which AI assistant works with your TYPO3?
- 0:00Which AI assistant can talk to your TYPO3? One MCP server, many assistants.
- 0:03Eight AI assistants can connect to your TYPO3 through one MCP server.
- 0:08They all use one server URL, ending in /mcp.
- 0:11The assistant acts as the backend user who approved its sign-in.
- 0:14Two routes into the same server.
- 0:15Route 1, OAuth: Claude, ChatGPT, Gemini, Microsoft Copilot, Cursor, VS Code and Claude Code.
- 0:24Route 2, token URL: PhpStorm, because JetBrains documents no OAuth sign-in for MCP servers yet.
- 0:28With OAuth, the sign-in opens in your browser and you approve it in TYPO3.
- 0:32A token URL works like a password: keep it out of Git, screenshots and chats.
- 0:37In AI Foundation, the Connect tab shows the server URL and a setup guide per client.
- 0:43OAuth Tokens: one token per assistant. Revoke one, and the others keep working.
- 0:50Pick yours, connect in minutes, see our guides.
- 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