TYPO3 MCP use cases: what you can hand to an AI assistant, on one map

Which TYPO3 jobs can an AI assistant take off your hands, and which of them cost nothing? This map of TYPO3 MCP use cases answers both.

MCP, the Model Context Protocol, is how an assistant such as Claude works inside TYPO3 through a set of tools. The map covers nine areas of TYPO3 work, from reading the page tree to redirects, alt text and translation. For each job it shows whether the free AI Foundation handles it or whether it needs a licensed AI Universe extension, and which episode of our series MCP in Practice for TYPO3 shows it on a demo site.

Two terms first, because they sound alike. Your AI assistant means the chat or coding app you work in, such as Claude or Cursor. AI Assistant, with capitals, is our licensed TYPO3 extension for writing, SEO and translation.

Through MCP, an AI assistant works inside TYPO3 with the tools that AI Foundation's MCP server provides. It reads pages, content, files and records and makes changes, and the AI Universe extensions add tools for alt text, SEO, translation, chatbot and search. It acts with the rights of the backend user it signs in as. Ask it to read the current value before a change, check the result on the page, and it can put the old value back. AI Foundation and the extensions together bring 100+ MCP tools.

The Model Context Protocol is an open-source standard for connecting AI applications to other systems. How it works, and how to connect your first assistant, is in our explainer on TYPO3 MCP. This post stays with the scope question: what you can hand over, and what it costs.

The series runs from 7 October 2026 to 5 May 2027, every Wednesday: two new jobs for your AI assistant, each with a one-minute video. There is a pause on 23 and 30 December. Each area below is one chapter of the season, so you can read the map as a list of free and licensed MCP tools for TYPO3, sorted by the work they do. Jobs whose tools still need a check on our demo install are not described yet; the series hub lists those episodes with their number and date.

AI Foundation is free and open source, no licence key, no registration. It adds the MCP server to TYPO3 and a core set of tools that every install has. Your assistant reads their names and descriptions and picks the one a job needs:

• Pages and content: read the page tree (pages_tree), find pages (pages_search), read and change content (content_get, write_table), move elements (content_move), copy a page with its subpages (pages_copy).
• Files and folders: list, rename and move files, import a file from a URL (file_upload_from_url) and check where a file is used (file_reference_list).
• Redirects, scheduler and caches: create and fix redirects (redirect_create, redirect_update), read and adjust scheduler tasks (scheduler_list, scheduler_update), clear caches (cache_clear).
• Access checks: see what a user may do on a page or table (permission_check_page, permission_check_table).
• Your own tables: Table Discovery turns the extension tables you enable into tools. It reaches only the tables you enable, and relation fields such as categories, tags, FAQ items and media fields are not written today.

Developers can also ship tools inside their own extension and give an assistant prompt templates and AI Skills, which the For developers chapter covers.

The MCP tools of the AI Universe for TYPO3 come with licensed extensions. Each one registers its tools on the same MCP server as AI Foundation, and each episode names the extension a job needs. AI Foundation's free status does not carry over to any of them.

• AI Assistant is our extension for writing, SEO and translation in the TYPO3 backend. Its tools cover drafts of pages, blog posts and news, SEO fields and translation, among them t3ai_generate_meta_description and t3ai_translate_content. The episodes that run them through an assistant start on 25 November 2026, and each job is described once it is checked on our demo.
• AI Accessibility finds images without alt text (t3aa_list_files_missing_alt_text). Your assistant describes them, you check the suggestions in the chat, and it saves the texts you approve to the file metadata (t3aa_update_file_metadata). This change is live at once, like every change to file metadata.
• AI Chatbot and AI Search each need their own licence. With either one, your assistant can check which sources your chatbot and AI search learn from, start a refresh and read the training summary. The tools for their settings and suggested questions are covered once their episodes are checked on our demo.

Each AI Universe product has its own page, and our overview of TYPO3 AI extensions links them all.

Nobody needs all nine areas. The season comes with five reading paths of six or seven episodes each, in reading order, and each path ends with a working day that puts its jobs together:

• Editors: first prompts and drafts in a workspace, questions about your site, everyday edits, one change everywhere, alt text for every image, then an editor's working day.
• Marketers: an SEO audit by conversation, a cloned campaign page, what your chatbot and AI search know, redirect maps, then a marketing manager's week.
• Administrators: install and switch on MCP, secure the server, review access, see what your AI does, compare context mode and native mode, then a morning check.
• Developers: install, test with MCP Inspector, ways to connect, Table Discovery, MCP tools in your own extension, skills and prompt templates, then an integrator's sprint.
• Agencies: a cloned campaign page, a content inventory for a relaunch, a weekly content-health report, then an agency's week across several TYPO3 sites.

The hub of MCP in Practice for TYPO3 keeps each path as a checklist in your browser.

An assistant connected through MCP acts as a backend user, so its reach is the reach you give that user. There is no dry run and no undo tool, and a change made on Live is live at once. So every job in this series comes with two things: how to check the change, and how to put it back.

• Keep the old value. Ask the assistant to read what is there before it writes. In our recording the answer shows the old teaser next to the new one, in English and German.
• Check it where readers see it. Open the page on desktop and phone, not only the record in the backend.
• Put it back. Ask the assistant to write the kept text back and to read the element again to confirm, or put it back in the backend. After our recording we put both old teasers back and checked the site again.

Good to know, whatever you hand over:

• Where you want a review step first, AI Foundation can hold changes to pages and content in a TYPO3 draft workspace, but files, file metadata, redirects, scheduler tasks and cache clears act live even there.
• Relation fields are set in the backend. Categories, tags and authors of blog posts, FAQ items and media fields stay a job for the backend, and so does uploading a whole folder at once.
• Your own tables need Table Discovery. The assistant reaches an extension table only after you enable it.

Content your assistant reads through MCP goes to the vendor of that assistant, as with any chat. Which content leaves your server in context mode and in native mode is the subject of episode 13 on 13 January 2027.

The video for this episode is one prompt on our demo TYPO3, recorded on 30 September 2026 through the MCP server of AI Foundation, as an administrator working on Live: Make the hero teaser on our E-Bikes page clearer, in English and German. The assistant searched the page, showed the old and the new teaser and wrote the hero teaser in English and in German, live at once, in 28.5 seconds from the prompt to the finished answer. By hand, the same edit takes five steps in the backend per language, from signing in to checking the page. We checked both heroes on the website and put the old teasers back after the recording. The video also opens the MCP Tools module: the core tools are free with AI Foundation, and each AI Universe extension adds its own tools and needs its own licence.

Everything in the free half of the map starts with one Composer command. Episode 2 on 14 October shows the install and the switch for the MCP server, and helps you pick an assistant. Episode 3 on 21 October brings your first prompts in the Playground. Guides for Claude, Microsoft Copilot, Cursor and VS Code are on the series hub.

The series comes from T3Planet by NITSAN Technologies, a TYPO3 Association Gold Member with more than 15 years of TYPO3 work, and its episodes are written by Jürgen, our AI Consultant for TYPO3. Every episode runs its job on our demo install before it is published.

Get AI Foundation for TYPO3