Purpose
The MCP Tools screen lists every tool an AI agent can call against your TYPO3 instance. Core tools ship with T3AF. Child extensions can register additional tools. Path: T3AF → MCP ToolsWhat you see
- Tool catalog — All registered MCP tools with descriptions
- Playground — Test a tool call without leaving the backend
- Extension cards — Tools contributed by installed T3Planet AI extensions
Core tools (v1)
These tools are available when the MCP Server is enabled:table_schema— Field metadata for any database tablepages_get— Read a single page recordcontent_list— List content elements on a pagewrite_table— Create, update, or delete records (permission-controlled)
0.
Extension-registered tools
When T3AI, T3AC, T3AS, or other connected extensions are installed, their MCP tools appear automatically in the catalog. Each card shows:- Tool name and description
- Required permissions
- Link to the extension documentation
Playground workflow
- Open T3AF → MCP Tools in the TYPO3 backend.
- Select a tool from the catalog (start with read-only tools like
pages_get). - Fill in required fields (page UID, table name, and so on).
- Run the tool and inspect the JSON response before connecting external agents.
Why use the playground
- Verify MCP is online before configuring Cursor
- Debug permission errors with a known backend user
- Show stakeholders what agents can access without installing client software
Security
- Tools respect backend user permissions and workspace context
- OAuth and URL tokens are configured on the MCP Server screen
- Limit which admin users may authorize external agents
- Use draft workspaces for
write_tabletests
When to use MCP Tools vs MCP Server
- MCP Server — Enable connectivity, OAuth, and client configuration
- MCP Tools — Browse tools, test calls, see extension contributions