{
"mcpServers": {
"typo3-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
GPL-2.0. View license →
Is it maintained?
Last commit 0 days ago. 71 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Typo3 Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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.
With the TYPO3 MCP Server, your AI assistant can help you:
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.
| Feature | Status | Notes | |----------------------------|-----------------|---------------------------------------------------------------------------------------------------------------| | MCP Connection | ✅ Ready | HTTP and stdin/stdout protocols (thanks to logiscape/mcp-sdk-php) | | Authentication | ✅ Ready | OAuth for Backend Users | | Page Tree Navigation | ✅ Ready | Page tree view similar to the TYPO3 backend | | Page Content Discovery | ✅ Ready | Similar to the List or Page module with backend layout support | | Record Reading/Writing | ✅ Ready | Read and write any workspace-capable TYPO3 table (core & extensions) with full schema inspection | | Content Translation | ⚠️ Experimental | Implemented, needs real-world testing | | Fileadmin Support | ❌ Missing | Not yet implemented | | Workspace Selection | ❌ Missing | Currently uses the first writable workspace of the user |
While there are a lot of automated tests, and even some LLM test, TYPO3 instances are wide