README

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.

🧪 Continuously Tested With Real LLMs

Every push to main runs a benchmark that has the latest models from Anthropic, OpenAI, Mistral, and Google actually use this MCP to perform real TYPO3 tasks. That's how we stay vendor-independent and prove the tool descriptions convey what they claim across very different prompting styles — your AI assistant of choice should just work, not only ours. Click any badge for the full run-by-run history.

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

🔍 Content Analysis & SEO

• SEO Optimization: "Add meta descriptions to all pages that don't have them" - Automatically generate missing SEO content based on page content
• Tone Analysis: "Review the tone of our product pages and make them more friendly" - Get suggestions for improving content voice and style
• Content Audit: "Find all pages mentioning our old company name" - Quickly locate content that needs updating

🚀 Productivity Boosters

• Template Application: "Apply our standard legal disclaimer to all service pages" - Consistently apply content patterns
• Content Migration: "Copy all news articles from 2023 to the archive folder" - Reorganize content efficiently
• Multi-language Management: "Ensure all German pages have English translations" - Identify and fill translation gaps

All these operations happen safely in workspaces, giving you full control to review before publishing!

💡 Want to know how it works? Check out our Technical Overview for detailed information about the implementation, available tools, and real-world examples with actual tool calls.

Project Status

While there are a lot of automated tests, TYPO3 instances are widely different and Language Models are also widely different. Feel free to create issues here on GitHub or share experiences in the typo3-core-ai channel.

Installation

composer require hn/typo3-mcp-server

Requirements:

• TYPO3 v13.4+
• TYPO3 Workspaces extension (automatically installed as dependency)

Usage

Quick Start

There are two ways to connect AI assistants like Claude Desktop to your TYPO3 installation:

Option 1: OAuth Authentication (Recommended)

For secure remote access with proper authentication:

1. Go to [Username] → MCP Server in your TYPO3 backend
2. Copy the Server URL (and optionally the Integration Name)
3. Add the Integration to whatever MCP Client you are using.

Option 2: Local Command Line Connection

This method gives you admin privileges by default. Add this to your mcp config file of Claude Desktop or whatever client you are using.

{
   "mcpServers": {
      "[your-typo3-name]": {
         "command": "php",
         "args": [
            "vendor/bin/typo3",
            "mcp:server"
         ]
      }
   }
}

Development

Running Tests

# Functional tests (PHPUnit)
composer test

# E2E tests — spins up MySQL, TYPO3, and Playwright in Docker
Build/runTests.sh -s e2e

# E2E without Docker (host PHP + SQLite + local Playwright).
# Auto-selected when Docker is unavailable.
Build/runTests.sh -s e2e --no-docker

# E2E against an existing TYPO3 instance
TYPO3_BASE_URL=https://my.ddev.site Build/runTests.sh -s e2e

# See all options
Build/runTests.sh -h

Adding New Tools

Tools are defined in the Classes/MCP/Tools directory. Each tool follows the MCP tool specification and maps to specific TYPO3 functionality.

Learn More

• 📖 Technical Overview - Comprehensive guide covering architecture, implementation details, and advanced usage
• 🏗️ Architecture Documentation - Deep dives into specific implementation aspects:
  • Workspace Transparency - How workspace complexity is hidden from AI
  • Language Overlays - Multi-language content handling
  • Inline Relations - Managing TYPO3's complex relation types

License

GPL-2.0-or-later