agentprose Cloud

Docs · Concepts

How AI agents use your site

What WebMCP is, what an AI browser sees on a page with agentprose, which browsers support it, and why your readers see no change.

Updated · Markdown

When an AI agent visits a page today, it gets the whole page: menus, cookie banners, share buttons and somewhere in the middle the article. It has to guess where the content starts, it spends tokens on markup, and it has no reliable way to search your archive. So it misses posts, mixes them up or quotes you wrong.

WebMCP is a new browser standard that lets a page hand the agent tools instead. The agentprose script registers a set of read-only tools on every page of your site. An AI browser that supports WebMCP sees them next to the page and can call them directly.

What an agent can do

  • Search your whole archive, ranked, with filters for tag, author and date.
  • Read a post as clean Markdown, in full or one section at a time, without menus or ads.
  • Check a quote before citing you, and get a citation with author, date and a link that highlights the exact words.
  • Find related posts, list your tags and authors, and get your subscribe link.

The full list, with every input, is in the WebMCP tools reference.

A typical visit

A reader asks their AI browser: "What has this blog written about pricing?"

  1. The agent calls search_posts with pricing and gets the matching posts with titles, summaries and links.
  2. It calls get_section to read just the part of one post it needs.
  3. Before quoting, it calls get_citation with the sentence. agentprose confirms the text really appears and returns a link that scrolls to it.

Each of those calls is one row in your dashboard.

Safe by design

  • Every tool is read-only (readOnlyHint). The only tool that does anything is navigate_to, which is off unless you turn it on, and it only opens pages on your own site.
  • Post text is marked as untrusted content (untrustedContentHint), so agents know it is data, not instructions.
  • The script only reads your own pages, feeds and sitemaps. It never acts as a proxy for other sites.

Browser support

WebMCP is new. Today it works in Chrome with the WebMCP flag or origin trial, and in any browser with the MCP-B polyfill. Everywhere else the script registers nothing, throws nothing and changes nothing. Your readers see no difference either way.

Where the content comes from

The tools answer from your page and from your site's index: the hosted index we build for you (see How we find your content), or, without Cloud, the feeds and sitemap the script reads in the browser.