---
title: "WebMCP on Who's In: Seven Read-Only Tools for AI Agents"
description: "Who's In registers 7 read-only WebMCP tools, so an AI agent in a WebMCP-enabled browser can search events, check places left and get the RSVP link."
canonical: "https://whos-in.app/blog/webmcp-event-platform"
generated: ssg-capture
---
<!-- GENERATED from the SSG capture of this page by frontend/scripts/content-markdown.mjs. Do not edit by hand. -->

Compatible with all major AI agents

AI-NativeAI Reviews28 Feb 2026 · 11 min read

# WebMCP on Who's In: Seven Read-Only Tools for AI Agents

WebMCP, a W3C Community Group draft that Chrome is trialling, lets AI agents call a page's tools instead of scraping its HTML. Who's In registers seven, all read-only.

Try It FreeNo sign-up required for guests · Every feature free forever

TL;DR

-   WebMCP is a W3C Community Group draft that lets a web page give AI agents callable tools, so they need not scrape HTML.
-   Who's In ships 7 read-only tools: search\_events, get\_event\_details, check\_availability, get\_rsvp\_link, get\_popular\_events, list\_categories, and get\_club\_info.
-   Chrome is trialling WebMCP behind a flag and an origin trial; other browsers have not shipped it.
-   All write actions (RSVP, event creation) still require explicit human confirmation — agents present links, users click.

## What is WebMCP?

The **Web Model Context Protocol (WebMCP)** is a draft from the W3C Web Machine Learning Community Group, proposed by engineers at Google and Microsoft. It is not a W3C standard. It introduces `document.modelContext` — a browser-native JavaScript API that lets websites declare structured, callable tools for AI agents.

Before WebMCP, browser-based AI agents had to take a screenshot, run visual recognition, guess at UI elements, and simulate clicks — a fragile, token-hungry approach. With WebMCP, agents call tools directly using structured JSON schemas. The result: structured answers instead of scraped HTML, and no brittle CSS selectors.

**Browser support:** Chrome, behind a flag. Other browsers have not shipped WebMCP. In any browser, the same seven functions are on `window.__whosin`, and the REST API serves agents outside a browser.

**Update, 25 October 2026:** our first version declared the tools in a shape browsers do not read, so they did not register. They do now, and every release checks in Chrome that all seven register before it ships.

## Before WebMCP vs. After

Before WebMCP— Screenshot agents

// Agent guesses at the DOM

screenshot(page)

→ ocr\_text("Find search bar")

→ click(x=312, y=204)

→ type("yoga london")

→ screenshot(page)

→ parse\_html(DOM)

→ guess\_selector(".event-card")

// Result: brittle, slow, costly

~3,200 tokens · 8–12 steps

After WebMCP— Direct tool calls

// Agent calls tools directly

search\_events({

query: "yoga",

location: "London"

})

→ { events: \[...\], count: 4 }

check\_availability("event-id")

→ { available: 3, isFull: false }

// Result: structured, fast, cheap

~350 tokens · 2 steps

## The 7 WebMCP Tools

All tools are read-only. Write actions (RSVP, event creation) require explicit human confirmation.

`search_events`

BrowseRead-only

Search upcoming public Who's In events by keyword, category, location, or date range.

param: query (string)

param: category (string)

param: location (string)

param: from (ISO date)

param: to (ISO date)

param: limit (number, max 50)

`get_event_details`

ReadRead-only

Retrieve full details for a specific event — title, date/time, location, description, capacity, host, and direct URL.

param: id (string, required) — event ID or URL slug

`check_availability`

StatusRead-only

Check remaining capacity and waitlist status. Returns confirmed count, available spots, isFull flag, and a suggested next action (rsvp, join\_waitlist, full or closed).

param: id (string, required) — event ID or URL slug

`get_rsvp_link`

LinkRead-only

Get the direct RSVP or booking URL for an event. For paid events, returns price and currency too.

param: id (string, required) — event ID or URL slug

`get_popular_events`

TrendingRead-only

Browse events sorted by attendance — most popular first. Optionally filter by category. Ideal for discovery and recommendations.

param: limit (number, default 10, max 50)

param: category (string, optional) — e.g. "yoga", "hiking"

`list_categories`

StaticRead-only

List every event category on Who's In. Returns values (for use as filters in search\_events and get\_popular\_events), labels, and emoji icons.

param: (no parameters)

`get_club_info`

ClubsRead-only

Retrieve public information about a Who's In club by ID or URL slug. Returns name, type, description, and direct link. Returns null for private clubs.

param: id (string, required) — club ID or URL slug

Human-in-the-loop — always

The `get_rsvp_link` response includes an `agentInstruction` field that explicitly tells the agent: _"Present this URL to the user and ask them to confirm — do not click or submit on their behalf."_No agent can RSVP without you clicking the link yourself.

## Complete Agent Workflow

How all 4 tools chain together in a real session — from search to booking link, end-to-end.

1

User asks the agent

"Find me yoga events in London this weekend with spots available."

2

Agent searches

`search_events`

{ query: "yoga", location: "London", from: "2026-03-07", to: "2026-03-08" }

3

Agent fetches full info

`get_event_details`

Retrieves title, description, host, price, and URL for the best match.

4

Agent confirms spots

`check_availability`

→ { available: 3, isFull: false, suggestedAction: "rsvp" }

5

Agent presents booking URL

`get_rsvp_link`

"Here's your RSVP link — click to confirm your spot:" → whos-in.app/event/...

## Why WebMCP Matters

Structured answers

Direct tool calls vs. screenshot-based browsing. Agents get structured JSON, not raw HTML.

No brittle selectors

Semantic tool declarations never break when the UI updates — the API contract is stable.

Model-agnostic

Any agent in a WebMCP-enabled browser can call them. Other agents use window.\_\_whosin or the REST API.

Zero setup for users

The page registers its tools as it loads. Open Who's In in a WebMCP-enabled browser and all seven are there.

### One link. Automatic everything.

Who's In handles RSVPs, waitlists, payments, and reminders automatically — starting with a free link you can create in 90 seconds.

Get Started Free

Every feature free forever · No credit card

## Other Event Platforms

Public APIs as each platform's own documentation describes them. A cross under WebMCP means no WebMCP tools that we know of; a dash means we have not checked.

| Platform | WebMCP | Public REST API | AI Readiness |
| --- | --- | --- | --- |
| Who's In | Yes | Yes | WebMCP (7 tools) + REST API + llms.txt |
| Eventbrite | No | Yes | OAuth REST API with webhooks |
| Luma | No | Yes | Public REST API and an MCP server (help.luma.com/p/mcp) |
| Partiful | No | Not checked | Not checked |
| RSVPify | No | Not checked | Not checked |

## How to Use It

1

Open Who's In in a browser-based AI agent

Use Chrome with the WebMCP flag turned on and an agent that can call a page's tools.

2

All 7 tools register as the page loads

No setup. The page registers search\_events, get\_event\_details, check\_availability, get\_rsvp\_link, get\_popular\_events, list\_categories and get\_club\_info through document.modelContext.

3

Agent calls tools directly

The agent can now search events, retrieve details, check capacity, and get a booking link — all without taking screenshots or guessing at DOM structure.

4

You confirm any write actions

The agent presents the RSVP link from get\_rsvp\_link and asks you to confirm. You always click the final button — agents cannot act on your behalf without your explicit approval.

Using a non-browser agent?

The same data is available via REST. Our OpenAPI 3.1 spec covers all public endpoints: no auth needed to read, and each IP gets 100 reads and 60 searches an hour.

[View API Reference](/api-docs)

## For Developers

Integrate Who's In into your own AI agent or automation pipeline. Three access paths — pick whichever fits your stack.

Path 1 — WebMCP (Chrome, behind a flag)Auto-discovered

// The page registers its tools as it loads; the browser lists them

const tools = await document.modelContext.getTools();

// → \[{ name: "search\_events", … }, { name: "get\_event\_details", … }, …\]

// The agent calls search\_events with { query: "yoga", location: "London" }

// → { events: \[...\], count: 4, hasMore: false }

Path 2 — window.\_\_whosin (any browser)Global namespace

// Available on all browsers, no flag needed

const events = await window.\_\_whosin.searchEvents({ query: "yoga" });

const link = await window.\_\_whosin.getRsvpLink('event-id');

// link.agentInstruction tells your agent not to auto-submit

Path 3 — REST API (any HTTP client)100 reads/hour

\# Base: https://whos-in.app/api/v1 — no auth needed for reads

GET /api/v1/events/browse

GET /api/v1/events/search?q=yoga

GET /api/v1/events/:id/status

\# OpenAPI 3.1 spec → https://whos-in.app/openapi.yaml

## Key Takeaways

Who's In registers seven WebMCP tools, giving AI agents structured access to public event data.

All seven tools are read-only. They work in Chrome with WebMCP turned on; any other client can use window.\_\_whosin or the REST API.

Write actions (RSVP, event creation) always require explicit human confirmation — get\_rsvp\_link returns a URL for the user to click, never auto-submits.

## FAQ

What is WebMCP?

WebMCP (Web Model Context Protocol) is a draft from the W3C Web Machine Learning Community Group, not a W3C standard. It adds document.modelContext, a browser API that lets a website register callable tools for AI agents. Instead of scraping HTML, an agent calls the tools with structured JSON.

Which AI agents can use Who's In WebMCP tools?

Any agent running in a browser with WebMCP turned on (today that is Chrome, behind a flag) that can call a page's registered tools. Any other agent can call the same seven functions on window.\_\_whosin in the page, or use the REST API.

Can an AI agent RSVP to an event on my behalf?

No. The WebMCP tools are intentionally read-only: search, view, check availability, and get a booking link. Any RSVP or event creation requires explicit human action — the get\_rsvp\_link tool returns the URL for you to click yourself. Agents cannot submit forms or make bookings without your direct confirmation.

Is payment information safe when an agent uses get\_rsvp\_link?

Yes. get\_rsvp\_link returns only the booking URL, event price, and currency — never card details, account credentials, or payment tokens. The agent presents the URL to you; you handle all payment steps yourself on the Who's In page. The agentInstruction field in the response explicitly tells agents not to click or submit on your behalf.

## Related Reading

[

### AI-Agent-Ready: The Future of Event Discovery

How structured data and open APIs make events discoverable by AI agents.

](/blog/ai-agent-ready-future-of-event-discovery)[

### Four AI Giants Reviewed Our Architecture

How ChatGPT, Claude, Gemini and Grok rated Who's In on 8 accuracy claims.

](/blog/four-ai-giants-reviewed-whosin-architecture)[

### Future of Event Technology 2026

Trends shaping the next generation of event platforms.

](/blog/future-event-technology-2026)

[AI Trust & Citations](/ai-trust) [API Reference](/api-docs)

By [Craig Pollard](/about)Last updated: March 20, 2026

[Who's In](/) is an event management platform that scales from a free RSVP link to automated waitlists, Stripe payments, email reminders, QR check-in, recurring events, and membership management. Free forever for community events. [Create your first event at whos-in.app](/create).

[Sell tickets](/sell-tickets)[Pricing](/pricing)[Compare platforms](/compare)[Reviews & mentions](/mentions)[Event glossary](/glossary)[Clubs](/clubs)[Studio](/studio)[Conference](/conference)

Share on X[Download as Markdown](/blog/md/webmcp-event-platform.md)
