WebMCP Challenge · browser-native tool calling
eventOS runs live events — 506 meetings, 200 exhibitors, 50 vendors on the floor at IMEX America. This page registers six of its operations as WebMCP tools on document.modelContext. An agent driving this browser discovers them the moment the page loads and calls them in the user’s own session: no API key, no OAuth grant, no server the agent has to be told about.
Open this URL in an agentic browser, then ask: “What tools does this page offer? Check vendor status for IMEX and tell me what’s at risk.” Or run any tool yourself below — the buttons call through the registered surface, exactly as an agent would.
Every tool returns a content block for the model plus structuredContent for hosts that read it, and every payload carries a source field — so an agent can tell a number measured by the live fleet from one produced by the catalog model.
Sentiment breakdown for an eventOS event — positive, neutral and negative signal counts plus the top themes driving them. For the live event this is scored from the eventOS agent fleet's real-time KPIs (meeting confirmation rate, exhibitor readiness, vendor SLA risk); for other events it is modeled from the catalog.
List every upcoming eventOS event with name, dates, venue, attendee count, exhibitor count and lifecycle status. The instrumented event is enriched with live counts from the eventOS agent fleet.
Profit and loss for an eventOS event — revenue lines, cost lines, gross profit, margin, and budget-versus-actual variance per line with the largest overruns called out.
Vendor readiness for an eventOS event — how many vendors are checked in and on track, how many are at risk or already in SLA breach, and how many exhibitor booth approvals are still pending. Live from the eventOS agent fleet's VendorAgent and InsightAgent.
Look up a venue in venueSource, the eventOS venue registry — halls, gross floor area, capacity, loading docks, power and wi-fi headroom, operations contact, and the operational caveat planners need to know.
Search the eventOS partner directory for event planners. Matches on name, agency, city, job title, specialty and language, and returns each match ranked by how well it fits the query.
No configuration step. The browser hands the agent whatever this page registered on document.modelContext during load.
execute() runs in the page, in the user's session. Three tools reach the live eventOS agent fleet over MCP through a same-origin proxy; three answer from the local catalog.
A five-agent fleet on Cloud Run — Booking, Insight, Comms, Vendor, Compliance — exposes 12 MCP tools over JSON-RPC 2.0. The console shows that traffic on the wire.
The same fleet is reachable as a conventional MCP server, and the console drives it directly so you can read every JSON-RPC frame. WebMCP is the layer that removes the setup: the browser is already authenticated, so the page can just offer the tools.