TYPO3 content inventory for a relaunch: every page, element and plugin in one question
Before a relaunch or a TYPO3 upgrade, an agency needs to know what the site holds: which pages are live, hidden or scheduled, which have a German version, which content element types and plugins are used, and which pages are empty. In the backend that means opening page after page and filling a spreadsheet. With TYPO3 MCP you ask your AI assistant one question and get the inventory.
The prompt
We're planning a relaunch of our Mustermann Outdoor site. Make a content inventory: every page with its status and languages, content elements by type, plugins in use, and pages that are empty. Read only, answer here in the chat.
One question, one inventory: pages, element types, plugins, empty pages and gaps
What does the assistant do?
- Ask once: name the site and what the inventory should list. Say that it is read only.
- The assistant reads the page tree, the languages of the site and every content element with its page, type and language.
- It lists every page with status, German version and element count; on our demo that is 33 English and 22 German page records with 94 content elements.
- It names the element types and the plugins in use, here a news list and AI Search, and the empty pages, such as Events.
- It ends with the gaps to settle first: pages without German, a hidden German page, a missing German element and a sale page with a fixed end date.
How do I check it and put it back?
A question changes nothing: the assistant only reads, so there is nothing to put back. To check the numbers, open Status, Pagetree overview with the type Record overview: it shows the content elements per page, both languages together.
What do I need?
AI Foundation with its MCP server switched on, and an MCP-capable assistant; AI Foundation is free.
What can the assistant not do for you?
- Check the numbers you plan with: on our demo the counts per page matched the backend, but the German totals per element type did not add up. Status, Pagetree overview shows the count per page.
- Plugins are read from the content elements on the pages. The list of installed extensions and their versions is not part of the answer, so an upgrade plan needs that list as well.
- The inventory covers pages and content elements. News records and files are separate: ask for them in their own question.
- The assistant reaches only the tables you enable: extension tables such as news need Table Discovery.
- 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?
One question in Claude on our demo install: a content inventory of the Mustermann Outdoor site before a relaunch, read only. Then the Pagetree overview in the TYPO3 backend, and the empty Events page and the Spring Sale page on the website.
Can I take the inventory into a spreadsheet?
Yes. The answer is a set of tables in the chat; ask your assistant for a CSV or a spreadsheet of the same data. Check the numbers you plan with in the backend first.
Does it cover an upgrade too?
It shows which content element types and plugins the pages use. For an upgrade you also need the list of installed extensions and their versions, which this question does not read.
Transcript of the video
- 0:00MCP in Practice for TYPO3 · Episode 20: TYPO3 content inventory for a relaunch: every page, element and plugin in one question
- 0:03One question: a content inventory of the Mustermann Outdoor site before the relaunch, read only.
- 0:04Claude reads the page tree, the site languages and every content element. It changes nothing.
- 0:06The scope first: 55 page records and 94 content elements in English and German.
- 0:07Every page with status, German version and element count: Tents and its two tents have no German yet.
- 0:09Events is live but empty; Winter Collection 2027 is hidden and a sale page is scheduled.
- 0:11Plugins in use: a news list and AI Search; hero, link list and social links come from the theme.
- 0:12It ends with the gaps to settle before the relaunch, and says what it did not check.
- 0:14Now check it in TYPO3.
- 0:16Status, Pagetree overview: the content count per page matches, both languages together, 7 on the TX-7 page.
- 0:28Further down, Events has no content at all, Winter Collection 2027 is hidden and a sale page is scheduled.
- 0:40On the website, the Events page is live with nothing on it.
- 0:45The Spring Sale page still promises an offer with a fixed end date: content to review before the relaunch.
- 0:50A content inventory from one question, instead of counting page by page.
- 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.
