Quickstart 

Prerequisites 

• The extension is installed and set up (see Installation).
• You have a site package where you can add PHP classes and TypoScript.

Step 1 – Write a tool provider 

Create a small PHP class in your site package (or any extension). Because the ToolProviderInterface carries the #[AutoconfigureTag('webmcp.tool')] attribute, an autoconfigured service implementing it is picked up automatically — no Services.yaml entry is needed as long as your extension enables autoconfiguration.

<?php

declare(strict_types=1);

namespace Vendor\SitePackage\Tool;

use Neoblack\Webmcp\Tool\Manifest;
use Neoblack\Webmcp\Tool\Primitive;
use Neoblack\Webmcp\Tool\ToolProviderInterface;
use TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer;

final class ServicesToolProvider implements ToolProviderInterface
{
    public function name(): string
    {
        return 'list_services';
    }

    public function manifest(ContentObjectRenderer $cObj, array $processedData): ?Manifest
    {
        return new Manifest(
            name: 'list_services',
            description: 'List the services this company offers.',
            inputSchema: ['type' => 'object', 'properties' => new \stdClass()],
            primitive: Primitive::StaticList,
            data: [
                'items' => [
                    ['title' => 'Consulting', 'url' => 'https://example.org/consulting'],
                    ['title' => 'Development', 'url' => 'https://example.org/development'],
                ],
                'resultKey' => 'services',
                'text' => [
                    'heading' => 'Our services:',
                    'line' => '{n}. {title} – {url}',
                ],
            ],
        );
    }
}

Vendor\SitePackage\Tool\ServicesToolProvider:
  tags:
    - name: webmcp.tool

Step 2 – Wire the manifest into the page 

Add the three pieces described in Configuration to your site package. In short:

page.10.dataProcessing {
    40 = Neoblack\Webmcp\DataProcessing\ToolManifestProcessor
    40 {
        endpoint = /webmcp-event
        as = webmcpConfigJson
    }
}

page.includeJSFooter {
    webmcp = EXT:neoblack_webmcp/Resources/Public/JavaScript/webmcp.js
    webmcp.defer = 1
}

Render the JSON block once in your page template:

<f:if condition="{webmcpConfigJson}">
    <script type="application/json" id="webmcp-config"><f:format.raw>{webmcpConfigJson}</f:format.raw></script>
</f:if>

Step 3 – Verify it in the browser 

Reload a frontend page and open the browser's developer console.

1. Confirm the manifest is on the page:

   JSON.parse(document.getElementById('webmcp-config').textContent).tools

   Copied!

   You should see your list_services tool in the returned array.

2. Confirm the runtime registered it against the ModelContext. A ModelContext implementation is only present in agent-capable browsers (or Chrome with the origin trial enabled); if document.modelContext and navigator.modelContext are both undefined, the page is fine — there is simply no agent surface to register against. See Troubleshooting if the tool is missing where you do expect it.

Once an agent operates the page, it can discover list_services and call it; the runtime returns the curated list and (unless disabled) records one anonymous usage row visible in the backend module.

Next steps 

• Swap static for another primitive — search, navigate or mailto — see Writing tools.
• Return null from manifest() to hide a tool on pages where it does not apply.
• Inspect usage in the System > WebMCP backend module (see Analytics).