Search by

konradmichalik / typo3-mcp-server-content-planner

konradmichalik

Bridges the TYPO3 MCP Server and Content Planner extensions, exposing content-planner status, assignee and comment workflows as MCP tools for AI assistants.

Package info

github.com/konradmichalik/typo3-mcp-server-content-planner

Type:typo3-cms-extension

pkg:composer/konradmichalik/typo3-mcp-server-content-planner

Statistics

Installs: 20

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

0.2.1 2026-09-09 09:45 UTC

README

Extension icon

TYPO3 extension typo3_mcp_server_content_planner

TYPO3 Coverage CGL Tests License

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 five MCP tools that register automatically once both host extensions are installed.

🔥 Installation

Requirements

Composer

composer require konradmichalik/typo3-mcp-server-content-planner

No further setup is required: the five 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.
UpdateContentPlannerComment write Update an existing comment's text or to-do checklist.

Note

This extension's own write tools (SetContentPlannerStatus, AddContentPlannerComment) always apply immediately to the live workspace, regardless of the acting backend user's current workspace; there is no draft/staging step to publish afterwards. Every tool respects the acting backend user's Content Planner and record permissions.

This does not apply to hn/typo3-mcp-server's generic WriteTable tool: comments live in tx_ximatypo3contentplanner_comment, and status is a column on the record's own table (e.g. pages, tt_content); both are workspace-capable, so WriteTable stages its changes in the acting workspace instead of writing live. Mixing this extension's tools with WriteTable on the same records can therefore produce inconsistent results depending on which tool made the last write.

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.

📜 License

GPL-2.0-or-later