**实验性。**这是一个0.x封包，其表面尚未确定。该 包名、二进制文件、命名空间和环境变量 在2026-08-06的一次切割中发生了变化。工具名称和它们回答的形状 也可以用同样的方式移动。在你依赖的提交位置钉住它。

一个本地MCP服务器（纯PHP），帮助编码代理实现、审查和 验证TYPO3的工作。它服务于三个用户群体：核心 贡献者、扩展作者和网站开发者。它建立了 项目与安装：代理工作并提供当前的版本绑定 TYPO3 知识。它将任务特定的工作流程交给拥有这些工作流程的技能。

它回答TYPO3 12.4、13.4、14.3和main。一个命题 它并不包含所有的名称。所以LTS永远不会有 只有开发线才有的惯例。

MCP客户端通过stdio作为子进程启动，因此没有服务器 主机，无需网络暴露，也无需授权来配置。进程边界为 信任边界。它读取。它在TYPO3安装时什么都写不入

TYPO3 Dev Companion

Experimental. This is a 0.x package and its surface is not settled. The package name, the binary, the namespace and the environment variables all changed in one cut on 2026-08-06. The tool names and the shapes they answer in can move the same way. Pin a commit where you depend on it.

A local MCP server (plain PHP) that helps coding agents implement, review and verify TYPO3 work. It serves the three audiences that do it: the core contributor, the extension author and the site developer. It establishes the project and installation the agent works in, and supplies current, version-bound TYPO3 knowledge. It hands task-specific workflows to the skills that own them.

It answers for TYPO3 12.4, 13.4, 14.3 and main. A statement that does not hold on all of them names the ones it does. So an LTS never gets a convention that only the development line has.

The MCP client launches it as a subprocess over stdio, so there is no server to host, no network exposure and no auth to configure. The process boundary is the trust boundary. It reads. It writes nothing into the TYPO3 installation it points at, and it starts nothing on the machine as a side effect of a lookup.

Quickstart

Requirements: PHP 8.2+ with the extensions composer.json requires, and Composer. composer check-platform-reqs names one that is missing. One standalone checkout serves every project on the machine and stays out of each project’s dependencies:

git clone https://github.com/TYPO3/dev-companion.git typo3-dev-companion
composer install --working-dir=typo3-dev-companion
cd /path/to/your/project
/absolute/path/to/typo3-dev-companion/bin/typo3-dev-companion install

install writes into the directory it runs in, so the last two lines run from the root of the project the agent works in. A project can require the package instead, composer require "typo3/dev-companion:@dev", and run vendor/bin/typo3-dev-companion install; the manual has that case.

install writes the typo3-dev-companion entry into the project’s .mcp.json and publishes the task skills to .agents/skills. Those are the two locations a client finds without configuration for it. --agent= writes them where that client actually reads them instead.

It is also the only supported way to get the skills. A copy of skills/ taken out of this repository by hand lacks the references/base.md the installer writes into each of them. Every skill opens on that file.

Documentation

The manual reads as a site at typo3.github.io/dev-companion, and as files in documentation/:

• Usage — the path from the install to the first answered question. Behind it every client the install supports and the task workflows it publishes.
• Server — what a caller can ask it, one page