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.
WebMCP tool for TYPO3
- Extension key
-
neoblack_webmcp
- Package name
-
neoblack/webmcp
- Version
-
0.4
- Language
-
en
- Author
-
Frank NΓ€gler & contributors
- License
-
This document is published under the Creative Commons BY 4.0 license.
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 individually via
document. (with an optional, switchable
fallback to the deprecated
navigator.). Optional, privacy-preserving first-party analytics
are included.
Warning
Experimental. Both the underlying WebMCP proposal and this extension's API may change or break at any time. See Introduction for details.
Getting started
β¨ Introduction
What WebMCP is, what this extension adds, and how everything degrades gracefully for regular visitors.
π Quickstart
From a fresh install to a working tool an agent can call β in three steps, no JavaScript required.
β¬οΈ Installation
Composer and requirements. What the extension does β and does not β do out of the box.
π οΈ Writing tools
The provider interface, the four behaviour primitives and the ES-module escape hatch.
βοΈ Configuration
Extension settings and how to wire the manifest, JSON block and runtime into your site.
π§ Architecture
The two request flows β emitting tools and ingesting usage events β and the classes behind them.
π Analytics
What the first-party usage log records, how long it is kept and how the public endpoint is protected.
π Standards and browser support
Where the WebMCP specification stands, which browsers and agents support it, and what is still open.
π‘οΈ Security considerations
Threats named by the specification, how the extension mitigates them and what remains your responsibility.
π§ Troubleshooting
Why tools might not register, providers not fire, or events not land β and how to check each.
β« Upgrading
What changes between versions and whether you need to act.