How AI agents find your site
Which agents get your site's sections and forms as tools, what you add to your pages for each, and the MCP address for developers.
Agents reach your published site in different ways, and none of them asks your visitors to install or connect anything. The Agents tab under AI agents shows each path and what it needs from you.
Why it matters
What an agent can do on your site depends on how it opens it. An agent that opens your site in a browser with WebMCP gets your sections and tagged forms as tools it can call. A chat that only reads your pages as text gets no tools — clear labels and section links still help it.
The three paths
| Path | Who | What you add |
|---|---|---|
| Browser agents with WebMCP — automatic | ChatGPT desktop and other agents that open your site in a browser | Web SDK 0.11.0 or later on your pages. Not released yet — see below. |
| Chrome’s own agent — optional | Chrome's built-in agent, offered as a Chrome origin trial | Register your site for the trial and add the token tag to every page. |
| Everyone else — no tools | Chats that read your site as plain text, and browser agents without WebMCP | Nothing. They still benefit from clear labels and section links. |
Web SDK 0.11.0 is not released yet
For Chrome's agent, get a token from Chrome origin trials and add it to the <head> of every page:
<meta http-equiv="origin-trial" content="YOUR_TRIAL_TOKEN">YOUR_TRIAL_TOKEN — the token Chrome gives you when you register your site for the WebMCP origin trial.
When agents get your site
Site tools and links reach agents only while the site is published and its domain verified. The Agents tab says when they do not:
- "Until you publish, agents get no site tools or links." — publish it on Publish. See Publish your site to AI agents.
- "Your domain is not verified, so agents get no site tools or links." — put the tag back on your home page. See Set up your site and verify your domain.
Either way, "Tagged forms stay visible to browser agents with WebMCP." Chrome, and web SDK 0.11.0 once released, register your tagged forms on the page whether or not the site is published.
The MCP address for developers
Expand For developers on the Agents tab to copy your site's MCP address. It serves the same site tools as an MCP server, so you can test what agents get from an MCP client. Your visitors never need it.
The address answers only while the site is published and its domain verified. It needs no token. To try it in Claude Code:
claude mcp add --transport http my-site YOUR_SITE_MCP_URLYOUR_SITE_MCP_URL — the address under For developers.
This address is about your site's tools for agents. To query your own Flamio data from Claude, Cursor or Codex, see Connect an AI tool over MCP.