Download the PHP package konradmichalik/typo3-ai-mate without Composer
On this page you can find all versions of the php package konradmichalik/typo3-ai-mate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download konradmichalik/typo3-ai-mate
More information about konradmichalik/typo3-ai-mate
Files in konradmichalik/typo3-ai-mate
Package typo3-ai-mate
Short Description AI Mate - Dev-only TYPO3 extension and symfony/ai-mate bridge that exposes the resolved runtime state of a TYPO3 installation (TCA, pages, TypoScript, middlewares, logs, request profiles) to AI coding assistants via MCP tools.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package typo3-ai-mate
A dev-only TYPO3 introspection bridge for AI coding assistants. It exposes the resolved runtime state of an installation — TCA, page composition, resolved TypoScript, the PSR-15 middleware order, logs and per-request profiles — to assistants like Claude Code, Cursor or Copilot over MCP, so they reason from facts instead of guessing from source files.
[!WARNING] This package is in early development stage and may change significantly in the future. I am working steadily to release a stable version as soon as possible.
[!IMPORTANT] This package is active only in a Development context (
Environment::getContext()->isDevelopment()).
🤔 Why
AI assistants normally read your raw source and config files and guess at the result. But the state that actually matters — the merged TCA, the resolved TypoScript of a page, the real PSR-15 middleware order, whether a request was cached — is computed at runtime and can't be reliably inferred from files alone.
typo3-ai-mate hands the assistant that already-resolved state instead — see Tools below for the full list of what it exposes. This is often more token-efficient too: a compact resolved summary costs far fewer tokens than having the assistant read and reason over the raw source and config files.
Use cases
- Slow page — "This page is slow — find the performance problem." The assistant reads the profile, spots N+1 queries / cache state / timing, and diagnoses instead of guessing.
- Error page — locate an exception in the logs and tie it back to the page that produced it.
- Major upgrade — surface breaking code, outstanding migrations and runtime deprecations before a major jump.
🔥 Installation
Requirements
- TYPO3 13.4 LTS & 14.3 LTS
- PHP 8.2+
- Composer mode
Composer
[!NOTE] Requiring
typo3-ai-mateautomatically pulls insymfony/ai-mate(the MCP server andmatebinary) andkonradmichalik/typo3-ai-mate(the profile source for thetypo3-profiler-*tools) — no separate installs needed.
TER
Download the zip file from TYPO3 extension repository (TER).
🔌 Connect your assistant
Scaffold the Mate workspace and register the tools once:
mate serve is a single MCP server exposing all typo3-* tools — your assistant (Claude Code, Cursor, Copilot, …) starts it for you once it is registered:
[!NOTE] After updating the package (
composer update), reconnect the MCP server so the assistant picks up new or changed tool schemas — in Claude Code run/mcpand reconnecttypo3-ai-mate. Freshly installed vendor code alone is not enough; without a reconnect the assistant keeps using the previously registered tool definitions.
⚙️ How it works
The MCP tools run in the Mate process (its own Symfony DI container, Configuration/Mate.php). They boot no TYPO3; they reach it by shelling out to vendor/bin/typo3 <command> (TYPO3_CONTEXT=Development, stdout→JSON) via the Typo3CliRunner service, or by reading profile artifacts directly. The console commands run in the TYPO3 process (TYPO3 DI, Configuration/Services.yaml) and emit raw JSON.
Tools
| Area | MCP tool | Purpose |
|---|---|---|
| Profiling | typo3-profiler-latest / -list / -search / -get |
Inspect recorded per-request profiles as compact summaries (timing, N+1, cache, page.id), each linking a typo3-profiler://profile/{token} resource for the full SQL/section detail. |
| Page | typo3-page |
Show a page's composition: content elements, cache signals and USER_INT plugins. |
| Records | typo3-records |
Read-only record query for any table (structured, parameterised — equality filters via uid/pid/where, never raw SQL). Returns compact rows (uid, pid, label/type, enable columns, timestamps; long text truncated) each with a _flags list (hidden/deleted/timed/fe_group). No restrictions by default so hidden/deleted rows are visible — the answer to "why is this record not showing?". Pass fields for specific columns, mode=full for all columns, respectEnableFields=true for the frontend view. Sensitive columns (passwords and password-type TCA fields) are always redacted, and any embedded emails, IPv4 addresses or secrets in text values are redacted too. |
| Logs | typo3-logs-search / -tail / -by-level |
Search, tail or filter the TYPO3 logs. Returns a compact summary (distinct messages with occurrence counts and lastSeen, no stack traces) by default; pass mode=full for individual entries with truncated traces, and since (e.g. 1h, 2d) to scope to recent entries. Emails, IPv4 addresses and secrets embedded in messages/traces are redacted before output. |
| TCA | typo3-tca |
Dump the resolved (merged, trimmed) TCA of a table. |
| TypoScript | typo3-typoscript |
Dump the resolved frontend TypoScript of a page. |
| TSconfig | typo3-tsconfig |
Dump the resolved Page TSconfig (rootline-merged: mod.*, TCEFORM, TCEMAIN, RTE) or User TSconfig — the backend configuration layer that no single file reveals. Scope large output with a dotted path, e.g. mod.web_layout. |
| Fluid | typo3-fluid-resolve |
Resolve the templateRootPaths/partialRootPaths/layoutRootPaths override chain for a plugin/view (e.g. plugin.tx_news_pi1) and report which physical template/partial/layout file wins — ordered candidate directories with exists flags plus the resolved file. |
| Middlewares | typo3-middlewares |
List the resolved PSR-15 middleware order. |
| Events | typo3-events |
List the resolved PSR-14 event listener registry. |
| Upgrade | typo3-upgrade-wizards |
List pending and completed upgrade wizards — outstanding DB/config migrations. |
| Extension scanner | typo3-extension-scanner |
Statically scan an extension — or all non-core extensions — against the core breaking/deprecation matchers. Returns a compact summary by default (matches grouped by message with strong/weak counts and the affected files, plus a per-origin rollup when scanning all); pass mode=full for individual matches with line content, and ownCode=true to skip third-party (vendor) packages. |
| Deprecations | typo3-deprecations |
Report runtime deprecation notices, deduplicated and counted. Each one carries origins — the likely caller in own code. With deprecation logging enabled, a dev-only log processor records the caller's backtrace at log time for a high-confidence file:line; otherwise it falls back to a class-aware static reverse search across own PHP/Fluid files. |
| Rendering | typo3-render-page |
Render a frontend page via an internal HTTP request (no external curl/Playwright) so runtime notices fire, and report the HTTP status plus the log entries written during that request. Requires a running webserver (e.g. DDEV). An explicit --url is only allowed for the installation's configured site hosts (SSRF guard) and the request is capped at 60s. |
💡 Development
Custom typo3-* tools, the Typo3CliRunner recipe and security notes live in DEVELOPMENT.md.
🔗 Related
hauptsacheNet/typo3-mcp-server is a complementary project with a different goal: it gives assistants a native MCP server to create, edit and translate TYPO3 content, safely gated behind workspaces. typo3-ai-mate deliberately does not write anything — it is a dev-only, read-only diagnostics bridge for the resolved runtime state (performance, TypoScript, middlewares, logs). Use the former to edit content, the latter to debug it; they sit happily side by side.
🧑💻 Contributing
Please have a look at CONTRIBUTING.md.
⭐ License
This project is licensed under GNU General Public License 2.0 (or later).
All versions of typo3-ai-mate with dependencies
ext-mbstring Version *
doctrine/dbal Version ^4
helgesverre/toon Version ^3.1
konradmichalik/typo3-request-profiler Version ^0.3
mcp/sdk Version ^0.6
nikic/php-parser Version ^5.8.0
psr/http-server-handler Version ^1.0.2
psr/http-server-middleware Version ^1.0.2
psr/log Version ^3.0.2
symfony/ai-mate Version ^0.10
symfony/console Version ^6.4 || ^7.0 || ^8.0
symfony/dependency-injection Version ^6.4 || ^7.0 || ^8.0
symfony/finder Version ^6.4 || ^7.0 || ^8.0
symfony/process Version ^6.4 || ^7.0 || ^8.0
typo3/cms-backend Version ^13.4 || ^14.3
typo3/cms-core Version ^13.4 || ^14.3
typo3/cms-install Version ^13.4 || ^14.3