** 실험.** 이것은 0.x 포장이고 그것의 표면은 침전되지 않습니다. 더 보기 패키지 이름, 바이너리, namespace 및 환경 변수 모두 2026-08-06에 1개의 커트에서 바뀐. 도구 이름과 모양 그들은 대답 동일한 방법을 이동할 수 있습니다. 당신이 그것에 의존하는 커밋을 Pin.

로컬 MCP 서버 (plain PHP) 코딩 에이전트 구현, 검토 및 TYPO3를 확인합니다. 그것은 그것을하는 3명의 청중을 봉사합니다: 핵심 contributor, 확장 저자 및 사이트 개발자. 그것은 설치 프로젝트 및 설치 에이전트에서 작동, 및 공급 전류, 버전-바운드 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