Schedule TYPO3 pages and short-lived redirects from chat
A campaign page should go live at a set time and come down again when the offer ends, and its short link should only work in between. In TYPO3 that means two modules and four time fields. With TYPO3 MCP your AI assistant sets all of it from one request.
The prompts
Put our Winter Collection page live in a few minutes and take it down again ten minutes later. Add a short link /winter that points to it only for that time. Dry run first.
A dry run, then one batch: the page with a start and end time, and a 302 redirect with the same windowTake it all back. Dry run first.
One undo by batch ID: the page hidden again, the times cleared, the short link removed
What does the assistant do?
- Ask once: the page, the start and end time, and a short link for the same window. Ask for a dry run first.
- The dry run tests the whole batch and rolls it back. If a field cannot be written, nothing is written and the assistant names the field.
- The assistant writes the page times and a temporary 302 redirect in one batch and gives you its batch ID.
- It reads both back: Publish Date and Expiration Date under Access, and the short link with the same times in the redirect list.
- At the start time the page and the short link go live; at the end time both stop. Clear the page cache once the start time has passed, so menus on cached pages show the new page.
How do I check it and put it back?
Keep the batch ID. records_undo with that ID, after a dry run of the undo, hides the page again, clears both times and removes the short link in one step. Redirects act live: a draft workspace does not hold them back, only their own start and end time.
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?
- Menus on pages cached before the start time kept the old menu until the page cache was cleared.
- Redirects act live: a draft workspace does not hold them back, only their own start and end time.
- A field your backend user may not write stops the whole batch; on our demo that was the note field of the redirect.
- 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 request in Claude on our demo install: put the Winter Collection page live at 13:02 and take it down at 13:12, with a short link /winter for the same window, dry run first. The first dry run is rejected and nothing is written, then the change is applied. Then the video shows the timer icon in the page tree, the Access tab of the page properties, Redirect Management and the website before and at 13:02.
Why is the redirect a 302?
The short link is temporary. A 302 tells browsers and search engines not to treat the move as permanent.
Why did the menu not show the page at once?
Pages cached before the start time kept their old menu. A page cache clear after the start time brought the new page into the menu.
Transcript of the video
- 0:00MCP in Practice for TYPO3 · Episode 13: Schedule TYPO3 pages and short-lived redirects from chat
- 0:02The request: Winter Collection live at 13:02, down at 13:12, plus a /winter short link. Dry run first.
- 0:05The step list names the connector: AI Universe Demo.
- 0:07The first dry run is rejected, nothing is written. Claude retries, then applies.
- 0:09Read back: the page is visible 13:02 to 13:12, with the short link /winter.
- 0:12A temporary 302; the hidden flag is off, the end time expires the page.
- 0:14Now check it in TYPO3.
- 0:15The page tree: Winter Collection now carries a timer icon.
- 0:24Access tab: Publish Date and Expiration Date are set, Page visible is on.
- 0:32Redirect Management: /winter with status code 302 and a timer icon.
- 0:40On the website before the start, the page answers Page Not Found.
- 0:45At 13:02, /winter leads to the Winter Collection page.
- 0:50Schedule and short link, from prompt to answer, instead of setting start and end times and a redirect by hand.
- 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.
Want to go further? See all TYPO3 extensions from T3Planet.

