neoblack/webmcp

Declarative WebMCP tool framework for TYPO3: define agent tools server-side, expose them via document.modelContext, with optional first-party usage analytics.

v0.3.0 2026-07-20 13:16 UTC

Requires

• php: ^8.2
• typo3/cms-core: ^14.3
• typo3/cms-frontend: ^14.3

Requires (Dev)

• phpstan/extension-installer: ^1.4
• phpstan/phpstan: ^2.1
• saschaegerer/phpstan-typo3: ^3.0
• typo3/coding-standards: ^0.8
• typo3/testing-framework: ^9.5

GPL-2.0-or-later

• TYPO3 CMS
• agents
• ai
• WebMCP
• modelContext

Published on Packagist.org on 2026-07-20 13:16 UTC

README

Warning

Experimental. This extension is experimental and not yet ready for production use. It is built on top of WebMCP, which is itself an experimental, early-stage proposal. Both the underlying specification and this extension's API may change or break at any time without notice. Use at your own risk.

A declarative WebMCP tool framework for TYPO3. Define agent tools server-side as small PHP providers; the extension collects them into a per-page manifest and a generic JavaScript runtime registers each tool against document.modelContext / navigator.modelContext. Optional, privacy-preserving first-party analytics are included.

• Extension key: neoblack_webmcp
• Composer: neoblack/webmcp
• Requires: TYPO3 v14.3+, PHP 8.2+

Installation

composer require neoblack/webmcp
vendor/bin/typo3 extension:setup --extension neoblack_webmcp

In a nutshell

A tool is a PHP class implementing \Neoblack\Webmcp\Tool\ToolProviderInterface. It returns a Manifest naming one of four behaviour primitives — navigate, search, mailto, static — whose generic interpreters live in webmcp.js. New tools are therefore pure server-side configuration; no JavaScript required. For anything the primitives don't cover, a manifest may point at its own ES module.

#[AutoconfigureTag('webmcp.tool')] // inherited from the interface
final class GreetToolProvider implements ToolProviderInterface
{
    public function name(): string { return 'greet'; }

    public function manifest(ContentObjectRenderer $cObj, array $processedData): ?Manifest
    {
        return new Manifest(
            name: 'greet',
            description: 'Return a greeting.',
            inputSchema: ['type' => 'object', 'properties' => new \stdClass()],
            primitive: Primitive::StaticList,
            data: ['items' => [['text' => 'Hello']], 'resultKey' => 'messages',
                   'text' => ['line' => '{text}']],
        );
    }
}

Wire the ToolManifestProcessor, render its JSON block as <script id="webmcp-config">, and include webmcp.js. See the full documentation under Documentation/.

Analytics

An optional first-party endpoint (/webmcp-event) logs one row per tool call — tool name + coarse client hint only, no PII — visualised in the Web → WebMCP backend module. Disable via the analyticsEnabled extension setting.

License

GPL-2.0-or-later.