Configuration
All settings of the AI Suite MCP are located in the extension configuration under Admin Tools → Settings → Extension Configuration → ai_suite_mcp. They can be edited directly in the backend and take effect immediately.
The most important switch is enableMcp, which activates the MCP endpoint (see Installation). The following options control the ongoing operation.
Main Settings
| Setting | Default | Function |
|---|---|---|
enableMcp | 0 | Main switch for the MCP endpoint. When disabled, TYPO3 responds to all requests to /aisuite-mcp with 404. |
mcpWriteMode | workspace | Determines how writing tools store data (workspace, auto, live). Details see below. |
mcpTokenLifetimeDays | 30 | Validity period of the OAuth access tokens in days. |
mcpSessionTimeoutSeconds | 1800 | Idle timeout for MCP sessions in seconds. 0 = SDK default (3600). |
mcpAllowedOrigins | (empty) |
Write Mode (mcpWriteMode)
The write mode controls how all writing tools store their changes. It can be set globally in the extension configuration and overridden when issuing a token per token. A token-bound workspace always takes precedence.
| Mode | Behavior | Use |
|---|---|---|
| workspace (default) | Forces every write operation into a draft workspace. The standard workspace of the backend user is used, otherwise an existing MCP workspace of this user, otherwise one is automatically created (title AI Suite MCP [#<uid>], user as member). Write operations never go live unnoticed. | The safe default. AI changes are always available as verifiable drafts. |
| auto | If EXT:workspaces is loaded, write operations go into the standard workspace of the backend user. If the user has not chosen one, the first accessible non-live workspace is used, otherwise live. | Mixed installations where a soft fallback to live is acceptable. |
| live | Bypasses workspaces and writes directly into the live records. | Non-critical automation where a review is not worth the effort. |
The extension typo3/cms-workspaces is a mandatory dependency and is installed with the installation. The target workspace is resolved in this order:
- A token-bound workspace, set when issuing the token. It always takes precedence.
- mcpWriteMode = live writes live.
- mcpWriteMode = workspace takes the standard workspace of the user, otherwise an existing MCP workspace, otherwise a newly created draft workspace. Fallback to live only if EXT:workspaces is not available.
- mcpWriteMode = auto with loaded EXT:workspaces takes the standard workspace of the user, otherwise the first accessible non-live workspace.
- If none of this applies, it writes live.
An automatically created workspace is not saved as the TYPO3 standard of the user (be_users.workspace_id remains untouched). It only affects MCP write operations, while the normal backend session remains on the usual workspace. Reading tools automatically follow the resolved workspace, so previews show the state after the write operation.
Two tools are not workspace-capable and write live in every mode, namely uploadMedia and generateImage. They create a sys_file record plus a physical file via FAL, and FAL does not know versioning. No write mode can undo this. Both are therefore tied to their own scope (mcp:media and mcp:image) and their own feature rights, both disabled by default. Also not recoverable are consumed credits of the generate*- and batch*-tools, even if they only return suggestions.