File & Image Support for the TYPO3 MCP Server - Enabling AI-Powered Media Management (Alexander Bernhardt)

philippstranghoener · January 6, 2026, 10:19am

Idea Title
File & Image Support for the TYPO3 MCP Server - Enabling AI-Powered Media Management

What is my idea about?

github.com/hauptsacheNet/typo3-mcp-server

README.md

main

# TYPO3 MCP Server Extension

**⚠️ This extension is a work in progress and under active development.**

This extension provides a Model Context Protocol (MCP) server implementation for TYPO3 that allows
AI assistants to safely view and manipulate TYPO3 pages and records through TYPO3's workspace system.

## 🔒 Safe AI Content Management with Workspaces

**All content changes are automatically queued in TYPO3 workspaces**, making it completely safe for AI assistants to create, update, and modify content without immediately affecting your live website. Changes require explicit publishing to become visible to site visitors.

## What Can You Do?

With the TYPO3 MCP Server, your AI assistant can help you:

### 📝 **Content Management**
- **Translate Pages**: "Translate the /about-us page to German" - The AI reads your content, translates it, and creates proper language versions
- **Import Documents**: "Create a news article from this Word document" - Transform external documents into TYPO3 content with proper structure
- **Bulk Updates**: "Update all product descriptions to include our new sustainability message" - Make consistent changes across multiple pages

This file has been truncated. show original

The TYPO3 MCP Server enables AI assistants to manage TYPO3 content, but currently lacks file/image support. This is a significant gap:

AI assistants can create and edit content but cannot attach images to content elements
When editors ask “Add an image to this news article,” the AI must respond that it cannot
Existing media in FAL (File Abstraction Layer) is invisible to AI assistants
This breaks the seamless content management experience and requires manual intervention

The problem is documented in the project’s technical overview as a key missing feature. Without image support, AI-assisted content management remains incomplete - like having an assistant who can write but cannot handle attachments.

What do you want to achieve by 30th of April 2026?
Concrete deliverables:

FAL Integration Tools - MCP tools to browse, search, and select files from TYPO3’s fileadmin
Image Metadata Search - AI can find relevant images by searching titles, descriptions, alt-texts, and metadata
File Reference Management - AI can attach existing files to content elements (news images, content element media, etc.)
Integration with existing AI extensions - Compatibility with ai_image_alt and similar extensions for AI-generated descriptions
Documentation & Examples - User guide and practical examples for AI-assisted media workflows
Full Test Coverage - All new tools covered by functional tests following project standards

What is the potential impact of your idea for the overall goal?
For the TYPO3 Community:

Completes the MCP Server’s content management capabilities, making it production-ready for real editorial workflows
Enables agencies to offer AI-assisted content services with full media handling
Reduces manual work for editors - AI handles both text AND images in one workflow
Showcases TYPO3 as an AI-ready CMS, attracting developers exploring AI integrations

Broader Impact:

The MCP Server is already open source and benefits any TYPO3 user with MCP-compatible AI tools (Claude Desktop, VS Code extensions, custom implementations)
Image support addresses the #1 requested feature based on community feedback
Makes AI assistants genuinely useful for complete content creation, not just text editing

How does your Idea align with the strategic goals for TYPO3 v14.
This aligns with TYPO3’s “Interfaces Instead of Integration” philosophy:

The MCP Server exposes TYPO3’s native FAL capabilities through a standardized interface (MCP protocol)
No specific AI provider is bundled - works with Claude, ChatGPT, and any MCP-compatible client
Respects TYPO3’s existing permission system and workspace workflow
Uses TYPO3 core APIs (FAL, DataHandler) rather than bypassing them

It also supports the GenAI toolbox initiative by providing the infrastructure for AI-powered media workflows while keeping TYPO3 as the source of truth for content and assets.

Which budget do we need for this idea?
10000 Euro

My Name
Alexander Bernhardt

just2b · January 7, 2026, 11:16am

IMO for AI & MCP we should concentrate on v14 only as there is something coming - https://review.typo3.org/c/Packages/TYPO3.CMS/+/92224 as WIP and it doesn’t really make sense to have 2 implementations paid by the community

benrhardt · January 7, 2026, 4:51pm

I don’t know anything about the core strategy for an MCP. I haven’t been able to find out anything in the last few months, even though I explicitly sought feedback on this at several conferences.

Benjamin’s project is not very documented, so maybe he can say something about it directly?

benrhardt · January 9, 2026, 2:26pm

@ischmittis just used the MCP for Updating Links to the TYPO3 Sites after the last updates. You can read his post here (in german): TYPO3 + MCP + Claude Desktop – funktioniert erstaunlich gut Zur TYPO3 Conference hat die TYPO3 GmbH und die TYPO3 Association die Webseiten grundlegend überarbeitet. Neue Inhaltsstruktur, neue URLs… | Ingo Schmitt | 10 comments

philippstranghoener · January 12, 2026, 10:49am

Hi everyone,
I just wanted to clarify this comment:

From the BCC perspective:
There is currently no plan to deliver or integrate an MCP server in the v14 Core. The MR from Benjamin is, as described, a demo/test basis for the Action API.
Work is ongoing in the same area, but there are not two parallel MCP implementations being built.

This is the current situation and the correct information to avoid misunderstandings.

benrhardt · January 15, 2026, 4:58pm

I’ve also written an article to help people get their bearings regarding MCP: