TYPO3 MCP with T3Karma: Build Pages from an AI Assistant

TYPO3 MCP on a T3Karma site: install AI Foundation, switch on the MCP server and let your assistant build pages, with workspaces and undo.

TYPO3 MCP with T3Karma: Build Pages from an AI Assistant

TYPO3 MCP lets an AI assistant read and write your TYPO3 content through a standard connection, while backend rights, workspaces and whole-batch undo stay in control.

  • MCP (Model Context Protocol) is an open standard that lets an AI assistant call tools in another system.
  • AI Foundation adds a built-in MCP server to TYPO3 with 100+ MCP tools. It is free and open source.
  • A T3Karma site is a normal TYPO3 site, so the assistant works on the same pages, content elements and files your editors use.
  • The assistant signs in as a backend user and can only do what that user may do.
  • Setup is three steps: install, switch on the server, connect with OAuth.
  • New pages arrive hidden. You publish them yourself.

TYPO3 MCP means connecting an AI assistant to a TYPO3 website through the Model Context Protocol. Without it, an assistant can only write text that you copy into the backend by hand. With it, the assistant can look up a page, create one, fill the fields and report back, using the same records TYPO3 itself uses.

Three terms in plain language

  • MCP: the shared language between an assistant and a system. It is published as an open standard at modelcontextprotocol.io.
  • MCP server: the part inside TYPO3 that listens for the assistant. In TYPO3 it comes with AI Foundation for TYPO3, the free extension from T3Planet.
  • MCP tool: one named action, for example pages_get to read a page or content_list to list the elements on it.

The assistant never gets a free hand in the database. It can only call the tools the server offers, and each call runs with the rights of the signed-in backend user.

An AI assistant on its own can write the text for a page. It cannot put that text into your TYPO3 backend. You copy it over, pick the content element, choose the column, set the SEO fields and repeat for the next page. The time goes into the clicking, not the thinking.

The T3Karma TYPO3 multipurpose template already removes most of the layout work: it ships with more than 150 content elements and over 40 ready-to-use demos. What is left is filling those elements, page after page.

That is the job TYPO3 MCP takes over. T3Karma holds the design and the elements, and the assistant uses the MCP tools to place content in them. It pays off most where many pages share one layout: agency sites, multi-location sites and microsites. It also helps when you move to one of the other TYPO3 templates later, because the content stays in TYPO3 records.

The best results come from a clear split. The assistant is fast at repetitive work that is quick to check. A person keeps everything where a mistake costs trust.

Editor tip: treat every assistant result like a draft from a new colleague. It is usually good, and it is yours to check before it goes live.

  • T3Karma 14.0.2. Runs on TYPO3 14.0 to 14.5.
  • AI Foundation 2.x. Free and open source (GPL-2.0-or-later). Version 2.0 runs on TYPO3 13.4 and 14.3, with PHP 8.2 or newer. Together with T3Karma, use TYPO3 14.3 or newer. Get it from the TYPO3 Extension Repository or with Composer.
  • An MCP client. An assistant that can connect to a remote MCP server, for example Claude Desktop or Cursor.
  • A backend user for the assistant. It acts with that user's rights, so give it what an editor needs and no more.

Installing with Composer is a one-time job for a developer or administrator. After that, editors work in plain language.

Prefer to see it first? This short tour shows the AI Foundation MCP server, its tools and the controls in a TYPO3 backend.

The AI Foundation for TYPO3 product tour. Self-hosted video, no third-party player.

The full walkthrough is in our TYPO3 MCP setup guide. For a T3Karma site the path is the same as for any TYPO3 site.

1. Install AI Foundation

Run this from your project root, where T3Karma is already installed. For a full rollout checklist, see the free TYPO3 MCP Starter Kit.

composer require nitsan/ns-t3af
vendor/bin/typo3 extension:setup
vendor/bin/typo3 cache:flush

2. Switch on the MCP server

Open AI Foundation > MCP Server > Advanced, tick Enable MCP Server and save. When the header shows Server Status: Online, the server is running. The screen shows the server URL, which ends in /mcp.

3. Connect the assistant with OAuth

Add the server URL as a remote MCP server in your assistant. TYPO3 then asks you to sign in and approve the connection. No password and no token goes into the assistant's settings. The MCP Server screen has a setup guide for Claude Desktop, Cursor, VS Code, Windsurf, Continue, JetBrains and more. Our TYPO3 MCP clients guide helps you choose.

If the server does not show Online

  1. Run extension:setup and cache:flush again and reload the backend.
  2. Check that Enable MCP Server is ticked and saved in the Advanced tab.
  3. Check that the server URL ends in /mcp and opens over HTTPS from the machine where your assistant runs.
  4. Check that the backend user for the assistant exists and is allowed to sign in.

Five minutes of preparation make the first run calm.

  1. Use a dedicated backend user for the assistant, with editor rights and not admin.
  2. Pick the workspace. Use a draft workspace when you can. TYPO3 describes workspaces as a way to change content without affecting the live version, with an optional approval step before publishing (see the TYPO3 workspaces documentation).
  3. Name the area. Tell the assistant where it may work, for example "only under Services".
  4. Start with a read-only prompt before you ask for any change.
  5. Know your way back. Batches can be undone with the batch ID, as long as nothing changed after them.
  6. Remember that files and redirects act live. They are not held back by a draft workspace, so check them straight away.

MCP tools work on TYPO3 records, and everything in a T3Karma site is a record. That gives the assistant these areas:

  • Pages. List the page tree, read a page, create, copy and move pages.
  • Content elements. Read and create the elements on a page, including the elements T3Karma adds.
  • Files. List, upload and rename files, and attach them to records.
  • Redirects and caches. Create redirects and clear the page cache after a change.
  • Languages. Read the site languages. With AI Assistant (T3AI) added, translate pages through MCP.
  • Extension records. Extensions can add their own tools. On our own site the T3Planet Blog extension adds authors, tags and comments. Browse more TYPO3 extensions from T3Planet.

The assistant only gets the tools and fields your backend user is allowed to use. A tool that the user's rights do not cover is not offered.

A good prompt answers five questions. You do not need technical words.

  1. Where? The page or area, for example "under Services".
  2. What? The one thing you want done.
  3. How much? A limit, such as "at most 10 pages".
  4. In what form? Hidden, as a draft, as a dry run.
  5. How do I check it? Ask for a short report of what changed.

Too vague

Make the Services section better.

Better

Under "Services", list the pages with an empty meta description. Do not change anything. Show me the page title and uid for each.

Start small and read the result before you go further. These prompts are starting points, not recorded results. Each comes with a check and a way back.

1. Read first

Show me the page tree under "Services" and list the content elements on the page "Web Design".

Check: compare the answer with your page tree. Way back: nothing changed. It also shows the assistant which element types and columns your T3Karma layout allows, so later pages copy them.

2. Build a draft page

Create a hidden page "Web Design for Agencies" under "Services". Use the same layout and element types as "Web Design", and write the text for a DACH audience.

Check: open the page in the backend and the preview. Way back: undo the batch or delete the hidden page. Nothing goes live until you publish it.

3. Fill the SEO fields

For every page under "Services" with an empty meta description, write one of at most 155 characters and apply it as a dry run first.

Check: a dry run reports what would change without writing anything. Way back: undo the batch ID. For bulk SEO work across a whole site, see the TYPO3 AI Assistant (T3AI).

4. Add alt texts to uploaded images

List the images in "fileadmin/services" without an alt text and suggest one for each. Wait for my approval before you write them.

Check: read the suggestions, then approve. Way back: files act live, so edit a wrong alt text straight away. To audit a whole site, use TYPO3 AI Accessibility.

5. Redirect moved pages

Create 301 redirects from these five old URLs to the new pages under "Services". Show me the list first.

Check: open each old URL in a browser. Way back: redirects act live, so delete or correct a wrong one right away.

6. Replace a phrase on many pages

Replace "Web Studio" with "Web Agency" in the headings of all pages under "Services". Use a dry run first.

Check: preview the result in a draft workspace. Way back: one call undoes the whole batch.

More starting prompts are in TYPO3 MCP prompts (ten starters and the Playground), and real jobs by role are in TYPO3 MCP use cases. The Playground lets you try a single tool by hand before an assistant does.

Letting an assistant write to a live site needs rules. AI Foundation gives you four:

  • Backend rights apply. The assistant can only change what the signed-in backend user can change.
  • Workspaces. Changes go to the workspace selected in the MCP Server module. That is Live unless you select a draft workspace.
  • Dry run and all-or-nothing batches. One call can create, update, delete and move up to 500 records. It either completes or writes nothing.
  • Whole-batch undo. Every batch has an ID, and one call takes the whole batch back, as long as nothing changed after it.

Two habits make this safer on a production site. Build new pages hidden and publish them yourself. And let the assistant read an existing T3Karma page before it writes. Refused and failed requests are logged in AI Usage & Logs, so you can check afterwards what the assistant did.

An assistant is fast at the first version of ten pages. The last ten percent is yours: a sharper headline, a different image, one more card. T3Karma 14.0.2 makes that part easier. Editors can now change the image gallery, modal and text-animation elements directly in the Visual Editor, without opening a backend form.

A workable routine

  1. The assistant reads a finished page (prompt 1).
  2. The assistant drafts the new pages as hidden (prompt 2).
  3. An editor opens each page in the Visual Editor and finishes it in place.
  4. The editor checks facts, links and images, then publishes.

Read what is new in T3Karma v14 for the rest of the release.

AI Foundation is self-hosted. By default it uses your own AI provider key, with no T3Planet proxy in the data path. AI Credits are an optional second path.

Your assistant and your AI provider do receive the text you send them. For client sites, check their terms and, where personal data is involved, your data processing agreement. AI Foundation also has an AI Label setting that records how much AI was involved in a record. Read more about TYPO3 AI from T3Planet.

  • Giving the assistant an admin user. Use an editor user.
  • Asking for too much at once. Start with one section.
  • Skipping the read-first prompt. The assistant then guesses your layout.
  • Publishing without a check. Look at every page first.
  • Forgetting that files and redirects act live. Check them at once.
  • Treating the output as final copy. Facts, prices and legal text stay with a person.
Cover of the MCP Starter Kit for TYPO3: Guide and Rollout Sheet

Free guide: the TYPO3 MCP Starter Kit

A 15-page guide plus an Excel rollout sheet. It walks you through installing AI Foundation, connecting your assistant, setting guard rails and running ten first jobs, each with a check and a way back. With real TYPO3 v14 screens.

Get the free MCP Starter Kit

AI Foundation for TYPO3 product tour

Sovereign TYPO3 AI

AI Foundation icon

AI Foundation for TYPO3T3AF

Free and open source. Switch on the MCP server and let your assistant work on your T3Karma site.

MCP specification: modelcontextprotocol.io. TYPO3 workspaces: docs.typo3.org. AI Foundation facts: T3Planet product page and the AI Foundation MCP Server screen.

TYPO3 MCP connects an AI assistant to a TYPO3 website through the Model Context Protocol. The assistant can then read and write pages, content elements and files through named tools, with the rights of a backend user.

No special T3Karma version is needed. AI Foundation works on the TYPO3 records that T3Karma uses. Use T3Karma 14.0.2 with AI Foundation 2.x on TYPO3 14.3 or newer.

Yes. AI Foundation is free and open source under GPL-2.0-or-later, with no price, no licence key and no domain limit. You pay your AI provider for what the assistant uses, or you use the optional AI Credits balance.

Any assistant that can connect to a remote MCP server. The MCP Server screen has setup guides for Claude Desktop, Cursor, VS Code, Windsurf, Continue, JetBrains and other clients.

Only if you let it. Build new pages hidden, check them, and publish them yourself. Use a draft workspace if you want a review step before Live. Files and redirects are not held back by a workspace, so check them right away.

Use the batch ID to undo the whole batch with one call. Undo works as long as nothing changed after the batch.

AI Foundation is self-hosted and runs on your server with your own API keys, so T3Planet is not in the data path. Your assistant and your AI provider do receive the text you send them, so check their terms for client data.

Installing AI Foundation with Composer is a one-time job for a developer or administrator. After that, editors work in plain language in their assistant, with a backend user and editor rights.

With AI Assistant (T3AI) added, translation tools are available through MCP. Read the site languages first, then translate one page and check it before you run a batch.