Add WebMCP integration to boost Agentic Browsing score
Author: vincangerCreated May 18, 2026Updated May 18, 2026
Labelsenhancement
Background
A Lighthouse audit of the template app shows a low Agentic Browsing score. Two of the three weighted audits have been addressed:
- ✅
agent-accessibility-tree— fixed by labeling the dark-mode toggle on theAI-crawling-improvementsbranch. - ⏳
llms-txt— still missing at site root (separate follow-up). - ✅
cumulative-layout-shift— already passing.
That gets us to ~65/100. To push the score higher and signal that the site is actively agent-friendly, we can adopt WebMCP, which Lighthouse measures via three currently-N/A audits:
webmcp-registered-tools— Lists the WebMCP tools registered at the time of analysis.webmcp-form-coverage— Annotates forms so AI agents can identify and interact with them reliably.webmcp-schema-validity— Validates the registered WebMCP schemas.
What to do
- Decide which user actions in the template app are worth exposing as WebMCP tools (likely candidates: create demo task, generate AI schedule, upload file, navigate to pricing/checkout).
- Register those tools with valid JSON schemas.
- Annotate the main forms (login, signup, demo task input, file upload, contact) with WebMCP metadata.
- Re-run Lighthouse and confirm the three WebMCP audits move from N/A → PASS, lifting the Agentic Browsing score.
References
- https://llmstxt.org/
- https://developer.chrome.com/docs/lighthouse/agentic-browsing (Lighthouse Agentic Browsing category)
- WebMCP spec / browser tooling docs (TBD — link from the audit "Learn more" URLs)
Scope
Lift only — does not block the existing AI-crawling-improvements work. Best handled as a standalone PR after the dark-mode + llms.txt fixes land.
Source: wasp-lang/open-saas