konradmichalik / typo3-mcp-server-content-planner
Bridges the TYPO3 MCP Server and Content Planner extensions, exposing content-planner status, assignee and comment workflows as MCP tools for AI assistants.
Maintainers
Package info
github.com/konradmichalik/typo3-mcp-server-content-planner
Type:typo3-cms-extension
pkg:composer/konradmichalik/typo3-mcp-server-content-planner
Requires
- php: ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0
- hn/typo3-mcp-server: ^0.5.0
- logiscape/mcp-sdk-php: ^1.2
- typo3/cms-core: ^13.4 || ^14.3
- xima/xima-typo3-content-planner: ^2.4
Requires (Dev)
- composer/class-map-generator: ^1.7.3
- phpunit/phpunit: ^11.0 || ^12.0 || ^13.0
- typo3/cms-base-distribution: ^13.4 || ^14.3
- typo3/testing-framework: ^8.2 || ^9.5
This package is auto-updated.
Last update: 2026-08-20 13:52:44 UTC
README
TYPO3 extension typo3_mcp_server_content_planner
This TYPO3 extension bridges hn/typo3-mcp-server
and xima/xima-typo3-content-planner:
it exposes Content Planner's status, assignee and comment workflow as MCP tools, so an AI
assistant connected to your TYPO3 backend can read and leave editorial status updates and
comments on records.
Note
Ideal for AI-assisted editorial workflows, e.g. having an assistant flag pages that need review, or reply to open to-dos left by an editor.
It ships no own database schema, backend module or configuration: just four MCP tools that register automatically once both host extensions are installed.
🔥 Installation
Requirements
- TYPO3 13.4 LTS & 14.3+
- PHP 8.2 – 8.5
hn/typo3-mcp-server^0.5xima/xima-typo3-content-planner^2.4
Composer
composer require konradmichalik/typo3-mcp-server-content-planner
No further setup is required: the four tools register automatically as soon as both host extensions are installed and configured.
💡 Usage
| Tool | Type | Description |
|---|---|---|
ListContentPlannerStatuses |
read | List all available statuses. |
GetContentPlannerInfo |
read | Get status, assignee and comments (with threads) of a record. |
SetContentPlannerStatus |
write | Set a record's status and optionally reassign it (defaults to the current backend user). |
AddContentPlannerComment |
write | Leave a comment (optionally with to-dos), or a threaded reply via parentCommentUid, on a record. |
Note
All write tools apply immediately to the live workspace; there is no draft/staging step to publish afterwards. Every tool respects the acting backend user's Content Planner and record permissions.
Example prompts
Show me all pages with the status "Needs Review" and summarize any open comments.
Set the status of the "Pricing" page to "Done", assign it to me, and reply to Jane's comment to let her know it's ready.
🧑💻 Contributing
Please have a look at CONTRIBUTING.md.
💎 Credits
Thanks to Marco Pfeiffer for building and open-sourcing
typo3-mcp-server.