From a brief to a draft in TYPO3
A new event series needs an overview page and three individual event pages. The copy and images have been approved. An editor could ask an agent: “Create these pages under Events, use our existing content elements and add the images supplied in the brief. List any missing information. Do not publish yet.”
The brief spans several connected tasks: finding the right place in the page tree, creating pages, assigning content and attaching media. The aim is a complete draft in TYPO3 that editors can refine in the website preview and approve for publication. This workflow removes the step of copying individual text blocks out of a chat.
How the agent reaches your pages and content
MCP stands for Model Context Protocol. It gives AI applications a standard way to discover and call tools. The language model interprets the brief, the agent coordinates the steps, and an MCP server exposes the connected application’s functions.
A TYPO3 extension connects the agent to the CMS. It reads pages and content as structured data and makes changes through the available tools. The connection uses a TYPO3 user account and its permissions, rather than imitating a person clicking through the backend.
-
Brief & source material
The editor specifies the content, target pages and permitted changes.
-
Agent & MCP
The agent reads the CMS structure and calls the relevant tools.
-
TYPO3 draft
Pages and content elements are created in a workspace.
-
Review & publication
The editorial team checks the preview and publishes the approved changes.
Less manual work on recurring updates
On an established website, the same information often appears on several pages. Editors also have to work through material from specialist teams, new downloads and content maintenance. Three tasks offer a useful focus for an MCP integration:
- Apply approved changes across a set of pages
- A product’s specifications have changed. Ask the agent to identify the affected pages first, then prepare the approved updates as drafts. Some mentions should stay as they are: an older press release may need to retain the details that were accurate at the time.
- Prepare source material for the website
- An approved document supplies the heading, introduction, body copy and downloads. The AI application reads the material, then uses MCP tools to place the content in the appropriate CMS elements. The brief should specify terminology, text lengths and the intended page structure.
- Find and address gaps in the content
- Ask the agent to find product pages without meta descriptions and draft suggestions based on their existing content. Editors then have a specific set of changes to review. On a larger site, the task can be divided by product group or section.
Work with the content elements you already have
The MCP integration described here adds an open-source extension to TYPO3 13.4 or later and uses Workspaces for content changes. It works through the existing field definitions and DataHandler, TYPO3’s record-processing mechanism. The agent does not need to rebuild the website in another system.
A product page, contact panel or event entry already has a defined structure. That structure determines where headings, descriptions, images and relationships belong. Custom records can also be connected when their configuration and workspace support allow it.
For an integration, we focus on that mapping: which content elements should the agent create, which fields and relationships must it handle, and which custom workflows need a dedicated tool? The aim is to fit the assistance to the website the team already works with.
Attach the images and downloads as well
An event brief often includes a lead image, speaker portraits and a PDF programme. Through the MCP connection, the agent can upload these files to TYPO3 and attach them to the appropriate content elements. Files can come from a web address or a local computer.
Uploads add to the file collection without overwriting existing files. New files enter TYPO3 storage immediately; their placement on the page is prepared in the workspace. Access to confidential material therefore needs to be controlled separately at the storage level.
Keep previews and approval in TYPO3
The workspace shows the draft in the website’s layout. Editors can refine headings, assess the image selection, check links and compare the result with the published version. Related changes can be reviewed together before they go live.
Our approach to editorial use keeps responsibilities clear: the agent prepares the changes, and the designated team members review and publish them. A TYPO3 account limits access to the relevant pages and content. OAuth connects that account to the AI application.
Bringing TYPO3 expertise and local AI together
At rudybohrer, years of TYPO3 development sit alongside our own research into local AI. On our DGX Spark, we study coding agents, tool use and tasks that span multiple steps. MCP connects that way of working to a familiar editorial environment: TYPO3’s pages, content elements and approvals.
OpenCode can call MCP tools and use local models through providers such as Ollama. This makes it possible to run the model on your own hardware. Content quality, reliable tool use and data-handling requirements guide the choice of setup.
For a TYPO3 integration, our approach is to cover a complete editorial workflow, from approved source material through pages and media to publication by the team. Working with the editors, we can then assess which manual steps can be removed and where their expertise remains essential.
MCP extends AI assistance into TYPO3’s page structure and content management. Our approach connects editorial tasks with the site’s existing content model, suitable AI tools and its publishing workflow.