Installing AI Suite MCP

AI Suite MCP also runs in TYPO3 installations without Composer (classic mode) under TYPO3 14.x/13.x/12.x. The extension itself ships the only library that TYPO3 does not bring along, the MCP SDK. You do not have to copy anything by hand. You can find the extension in the TYPO3 Extension Repository (TER).

1. Activate the system extensions workspaces and reports.
2. In the Extension Manager, first install and activate ai_suite and then ai_suite_mcp, each from the TER or by upload. Keep to this order.
3. Open the “Status report” under System → Reports (TYPO3 14: Administration → Reports). The section “AI Suite MCP Environment” reports missing PHP extensions and an MCP SDK that cannot be loaded. Both point to an incomplete upload.
4. Where the documentation mentions vendor/bin/typo3, you call typo3/sysext/core/bin/typo3 from the TYPO3 root directory. Without a system cron, you run ai-suite-mcp:cleanup via the scheduler task for executing console commands.

Differences from the installation with Composer:

• Paths: Instead of var/, TYPO3 uses typo3temp/var/. Sessions are then stored in typo3temp/var/aisuite_mcp_sessions/, task results in typo3temp/var/mcp_tasks/ and the logs in typo3temp/var/log/. Under Apache, the TYPO3 .htaccess blocks this directory. Under Nginx, you add a rule yourself, for example location ^~ /typo3temp/var/ { deny all; }, otherwise the session files are publicly readable.
• Host root only: The MCP endpoint, the OAuth endpoints and the documents under /.well-known/ are answered at the root of the host. A TYPO3 in a subdirectory (such as example.com/cms/) is not supported.
• Web server: The rules for the Authorization header from Production Operation apply unchanged.

Right after installation, the MCP server is deliberately disabled. The endpoint at /aisuite-mcp only becomes available once the switch enableMcp has been activated in the extension configuration. As long as it is disabled, TYPO3 answers all requests under /aisuite-mcp as well as the OAuth documents under /.well-known/ with 404 (mcp_disabled), only the interstitial page /aisuite-mcp/open for backend links that have already been issued remains reachable.

You can find the extension configuration in the backend under Admin Tools → Settings (TYPO3 14: System → Settings) → Extension Configuration → ai_suite_mcp. The individual options are described under Configuration.

In addition, the section “AI Suite MCP Security” in the status report under System → Reports (TYPO3 14: Administration → Reports) checks the most important settings after setup.