PHPackages                             typo3/dev-companion - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. typo3/dev-companion

ActiveLibrary

typo3/dev-companion
===================

Local MCP server that guides coding agents through TYPO3 implementation, review and verification with version-bound knowledge and project facts.

20PHPCI passing

Since Aug 14Pushed today1 watchersCompare

[ Source](https://github.com/TYPO3/dev-companion)[ Packagist](https://packagist.org/packages/typo3/dev-companion)[ RSS](/packages/typo3-dev-companion/feed)WikiDiscussions main Synced today

READMEChangelogDependenciesVersions (1)Used By (0)

TYPO3 Dev Companion
===================

[](#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 for the three audiences that do it: the core contributor, the extension author and the site developer. It establishes the project and installation the agent is working in, supplies current, version-bound TYPO3 knowledge, and 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 is never handed 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: nothing is written into the TYPO3 installation it is pointed at, and nothing on the machine is started as a side effect of a lookup.

Quickstart
----------

[](#quickstart)

Requirements: **PHP 8.2+** and Composer. The package works both ways — as a standalone checkout and as a Composer dependency of another project.

```
# standalone: clone, install once, then point a project at it
composer install
/absolute/path/to/typo3-dev-companion/bin/typo3-dev-companion install

# as a dependency: from the consuming project's root
vendor/bin/typo3-dev-companion install
```

`install` writes the `typo3-dev-companion` entry into the project's `.mcp.json`and publishes the task skills to `.agents/skills` — the two locations a client finds without being configured 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 is missing the `references/base.md` the installer writes into each of them, and every skill opens on that file.

Documentation
-------------

[](#documentation)

The manual reads as a site at [typo3.github.io/dev-companion](https://typo3.github.io/dev-companion/), and as files in [documentation/](documentation/readme.rst):

- [Usage](documentation/usage/readme.rst) — every client and layout the install supports, the task workflows it publishes, and what you are agreeing to when it runs.
- [Server](documentation/server/readme.rst) — what it can be asked, one page per tool, and where each answer comes from.
- [Contributing](documentation/contributing/readme.rst) — working on this repository rather than using it.
- [Records](documentation/records/readme.rst) — how feedback from a real session becomes an improvement.

The conventions every session here works under are [AGENTS.md](AGENTS.md).

###  Health Score

22

—

LowBetter than 21% of packages

Maintenance65

Regular maintenance activity

Popularity3

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity11

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/165630?v=4)[Benni Mack](/maintainers/bmack)[@bmack](https://github.com/bmack)

---

Top Contributors

[![benjaminkott](https://avatars.githubusercontent.com/u/3243119?v=4)](https://github.com/benjaminkott "benjaminkott (1392 commits)")

### Embed Badge

![Health badge](/badges/typo3-dev-companion/health.svg)

```
[![Health](https://phpackages.com/badges/typo3-dev-companion/health.svg)](https://phpackages.com/packages/typo3-dev-companion)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)