Get started

One local process, started by your client. It needs PHP 8.2 or newer and a TYPO3 project it can read — no daemon, no database of its own, and no account anywhere.

1.4.0 MIT PHP 8.2+

Three ways in

bash

# in the project the server should read
$ composer require --dev typo3/support-app
✓ registered 8 tools in .mcp.json

What is published

Three files, and two of them are only there so the first can be checked. The hashes are shortened here and in full in checksums.txt.

File	What it is	Size	SHA-256
typo3-support-app.phar	The server, self-contained. PHP 8.2+ and nothing else.	4.1 MB	a3f1…9c2e
typo3-support-app.phar.asc	The signature over the file above.	833 B	—
checksums.txt	Every published file and its hash, signed with the same key.	1.2 kB	7b04…11af

Check what you got

One command, and it answers about the file on your disk rather than about the page you downloaded it from. A signature is worth more than a hash on the same server as the file — the key is published with the releases and changes when it is rotated, never quietly.

Verify

bash

# compare what you got against what was published
$ sha256sum -c checksums.txt
✓ typo3-support-app.phar: OK

When it does not answer

The client starts it and nothing appears

The server writes what it registered to standard error on start. Run php typo3-support-app.phar scope in the project by hand: it prints the same thing without a client in the way.

It starts and every tool says “not booted”

The installation cannot be booted from where the server was started. It answers from package files meanwhile, and ddev start closes the gap for a DDEV project.

Neither of those is a bug worth reporting until the scope has been read — it says which sources were reachable, and that is the answer to both questions.

Read the install guide Report a wrong answer