AI development helper for TYPO3 v13/v14 — an MCP server exposing TCA, database schema, sites, TypoScript, logs and the core changelog to Claude Code and other MCP clients.
TYPO3 Dev MCP demonstrates solid definition quality across 8 well-structured tools. All tools have explicit descriptions (194 - 320 chars, well within 10 - 1024 baseline), proper JSON Schema input definitions with typed parameters, and clear use cases. Naming follows verb_noun conventions (application_info, backend_modules, database_query). However, several gaps prevent an A-grade: (1) parameter descriptions vary in specificity, some lack constraint details (e.g., 'query' in database_query lacks SQL dialect hints); (2) no output schemas documented in source code visibility, we can infer structured returns but cannot verify field contracts; (3) error handling guidance is minimal (database_query mentions 'Read-only' but no recovery guidance for permission errors); (4) tool annotations missing entirely (no readOnlyHint, destructiveHint, idempotentHint flags); (5) no evidence of per-tool permission scoping. The benchmark fixture and multi-version DDEV environment suggest production intent, but documentation of downstream field mappings and error taxonomies is absent. Per-tool evaluation follows.
TYPO3 and PHP version, application context, database platform and active extensions of this installation. "packages" adds every installed Composer package.
Registered backend modules with identifier, parent, path, access level and routes. "identifier" for one module in detail, "search" to find one. Identifiers changed in TYPO3 v14 — resolve them here rather than from memory.
Registered Content Blocks with vendor/name, generated type name, table, host extension and field definitions. "name" for one block in full detail. The YAML field identifiers here are what ends up in TCA and in the database.
Registered content element types (tt_content CTypes) with label and group, plus legacy list_type plugins where present (removed in TYPO3 v14).
Execute one SQL query against the TYPO3 database and get the result rows. Read-only: only SELECT/SHOW/EXPLAIN/DESCRIBE/WITH are accepted (set DEV_MCP_ALLOW_WRITE=1 to allow writes). TYPO3 soft-delete semantics are not applied for you: filter deleted=0 (and hidden=0 for live records) yourself.
The live database schema. No arguments: all table names with their column count. "table": columns, indexes and foreign keys. "filter": only tables matching a substring. For relations, enable-fields and record types use tca_schema instead.
No output schemas documented. Source code shows parameter schemas (input) but tool descriptions lack explicit field contracts for responses. Downstream tools cannot reliably chain calls without API trial-and-error.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). While descriptions state 'Read-only', MCP protocol tools should declare hints formally. database_query with DEV_MCP_ALLOW_WRITE=1 becomes destructive but has no destructiveHint flag or confirmation pattern.
Error handling guidance absent. Tools return success/failure but lack recovery hints. E.g., database_query with invalid SQL returns error but no suggestion to call database_schema first; extension_info failing on unresolved key offers no 'try application_info to find valid keys' hint.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Look up a TYPO3 extension: the version installed here plus the latest TER and Packagist releases, including which TYPO3 majors they support.
Resolve the FlexForm data structure of a TCA field into sheets and fields with their TCA configuration — the field names a plugin actually stores in its FlexForm XML. Defaults to tt_content.pi_flexform; "type" selects the structure (the CType, or on TYPO3 v13 the list_type of the plugin).
Parameter constraints underspecified. 'query' parameter in database_query lacks SQL dialect, query length limits, or timeout guidance. 'filter' in database_schema does not document case-sensitivity or substring vs regex. 'record' object in flexform_schema has no shape specification.
Mutually exclusive parameters not formally declared. backend_modules (identifier vs search), extension_info (key vs composerName) mention alternatives in descriptions but schema does not enforce it. LLMs may pass both, causing ambiguous behavior.
No permission scoping visible. Tools read/write sensitive TYPO3 state (database, configuration, extensions) but descriptions do not declare required permissions (e.g., 'read:database', 'write:database'). No audit trail mechanism mentioned.