Download the PHP package balatd/typo3-dev-mcp without Composer

On this page you can find all versions of the php package balatd/typo3-dev-mcp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of balatd/typo3-dev-mcp

Informations about the package typo3-dev-mcp

typo3-dev-mcp — AI development helper for TYPO3

typo3-dev-mcp gives Claude Code (and any MCP client) live insight into your TYPO3 v13/v14 installation: instead of guessing versions, TCA columns, CTypes or config keys from files, the AI reads them from the running application. Inspired by laravel/boost.

Development-only tooling. Do not install or enable in production.

Does it actually help?

Measured, not asserted. 170 benchmark runs on claude-opus-5 against a real TYPO3 13.4 installation, comparing a plain Claude Code session against the same session after devmcp:install:

Task family Baseline With typo3-dev-mcp
Live-state questions (TCA, compiled TypoScript, FlexForm, site sets) $0.208 · 10 turns $0.097 · 4 turns
Code changes $0.236 · 13 turns $0.212 · 13 turns
Debugging a seeded fault $0.164 · 8 turns · 7% hallucination $0.205 · 9 turns · 0% hallucination
Control (pure refactoring, no live state) $0.107 · 5.5 turns $0.088 · 4 turns

On questions about the running installation: 53% cheaper, 60% fewer turns. The largest single case was resolving lib.contentElement.templateRootPaths after site-set merging — a value that exists in no single file — where the baseline burned 458,000 more tokens reconstructing it by reading across extensions.

Two things this benchmark does not show, stated plainly:

Full methodology, per-task results, per-tool usage and limitations: Tests/Benchmark/README.md.

Installation

Also published in the TER as dev_mcp, though Composer is the supported path for a --dev dependency.

devmcp:install

Then restart your AI assistant (or run /mcp in Claude Code).

Claude Code is supported out of the box via the project-scoped .mcp.json. Support for other AI CLIs (Codex, Gemini CLI, …) is coming. Meanwhile any MCP client can be pointed at vendor/bin/typo3 devmcp:serve manually — and the composed guidelines already land in AGENTS.md, which most agents read.

Tools

Application and data

Tool What it does
application_info TYPO3/PHP version, context, DB platform, active extensions, composer packages
database_schema Live schema: tables, columns, indexes, foreign keys
database_query Run a single SQL query (read-only unless DEV_MCP_ALLOW_WRITE=1)
site_info Sites, base URLs, root pages, languages, error handling
tca_schema The TCA: tables, columns, types, relations, record types, palettes
content_elements Registered CTypes (+ legacy list_type plugins where present)
content_blocks Registered Content Blocks with type name, table and YAML field definitions

Resolved configuration

The backend-module-only corners of TYPO3 — core ships no CLI for any of these.

Tool What it does
typoscript Compiled frontend TypoScript for a page (setup / constants / config)
page_tsconfig Resolved Page TSconfig for a page — mod.*, TCEFORM, TCEMAIN
site_sets Site sets, dependency order, settings definitions, effective site settings
flexform_schema Resolved FlexForm data structures: sheets, fields, per-field TCA
middleware_stack PSR-15 stacks in execution order with package and before/after
get_config TYPO3_CONF_VARS subtrees, feature toggles, extension configuration (secrets masked)

API discovery

Tool What it does
viewhelper_lookup Every available ViewHelper with its exact arguments, types and defaults
list_events PSR-14 events and the listeners actually registered for them
backend_modules Registered backend modules: identifier, parent, path, access, routes
list_commands All vendor/bin/typo3 console commands with synopsis

Documentation and diagnostics

Tool What it does
search_docs Search docs.typo3.org, pinned to the installed major version
search_changelog Search the core changelog (Breaking/Deprecation/Feature/Important) of the installed version — offline and exact
extension_info An extension here vs. in the TER and on Packagist — including TYPO3 compatibility
read_log_entries Recent log entries — file logs, deprecation log or sys_log
last_error The most recent error-level log entry
flush_cache Flush all caches or a cache group

content_blocks is only announced when friendsoftypo3/content-blocks is installed. Because the DI container is cached, installing that package later needs a vendor/bin/typo3 cache:flush before the tool appears.

Safety model

Extending

Custom tools from your extension or sitepackage

Implement BalatD\DevMcp\Mcp\ToolInterface — that's it. With standard autoconfiguration (autoconfigure: true in your Services.yaml, the default in every modern extension) the service is tagged and announced automatically:

Constructor injection works as in any TYPO3 service. Throw a \RuntimeException with an actionable message on failure — it reaches the AI as a readable error. After adding a tool, flush the DI cache (vendor/bin/typo3 cache:flush) and restart the MCP server.

PSR-14 events

Event Dispatched Use it to
CollectToolsEvent once at server start add, remove or replace tools before they are announced
BeforeToolExecutionEvent before every tool call adjust arguments, short-circuit with your own result, or veto by throwing
AfterToolExecutionEvent after every successful call post-process results (extra masking, audit logging)

Requirements

Versioning

Semantic versioning, with a deliberately narrow promise. Covered — break these and the major version goes up:

Not covered — these may change in any minor release:

Two tools read core APIs that core itself marks @internal — typoscript (FrontendTypoScriptFactory) and list_events (ListenerProvider) — because no public equivalent exists. Both degrade to an explanatory error rather than a stack trace, but a core minor can require a patch release here.

Development

The repository ships a DDEV harness with TYPO3 v13 and v14 side by side:

Backends: https://v13.typo3-dev-mcp.ddev.site/typo3/ / https://v14.typo3-dev-mcp.ddev.site/typo3/ (admin / Joh316!!).

The functional suite is a smoke matrix: it executes all 23 tools against a booted TYPO3 and asserts the announced roster, the input schemas and each documented top-level shape. It deliberately does not pin payload contents — see Versioning. Protocol smoke test without an MCP client:

Benchmark

Tests/Benchmark/ holds the A/B harness behind the numbers above — a separate, host-mounted TYPO3 project, a fixture extension seeding the live state the tasks interrogate, 17 graded tasks, and a blind judge. See Tests/Benchmark/README.md.

License

MIT

All versions of typo3-dev-mcp with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
mcp/sdk Version ^0.7.1 || ^0.8
symfony/process Version ^7.1.3 || ^8.0
typo3/cms-core Version ^13.4 || ^14.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package balatd/typo3-dev-mcp contains the following files

Loading the files please wait ...