Redocly Lets Browser AI Agents Search and Read Docs Through WebMCP
Redocly's Oct. 12 Realm 0.138.0 adds WebMCP for browser AI agents, a prompt tag and a consent option. Segment page tracking is now off by default.

Redocly’s Realm 0.138.0 adds WebMCP support for AI agents running in a reader’s browser. They can search, read and navigate a docs site, according to the Realm changelog entry dated Oct. 12. The same release adds a prompt Markdoc tag, a cookie consent option and a Connect to Claude shortcut.
WebMCP lets browser agents use the docs directly
The changelog describes WebMCP as support for AI agents “in the reader’s browser” to search, read and move through documentation. Mintlify’s Sept. 25 changelog listed a WebMCP feature too. It exposes site tools to in-browser agents.
A prompt tag puts a copyable AI prompt on the page
The new prompt Markdoc tag displays an AI prompt on a page. Readers can copy it or open it in Cursor, Claude or ChatGPT. Redocly also added a Connect to Claude option to page actions and to the MCP server setup page.
Analytics defaults and consent change
Realm now turns off page view tracking by default for three options: analytics.segment.trackPage, analytics.segment.includeTitleInPageCall and analytics.rudderstack.trackPage. Sites that relied on the old defaults stop sending page views to Segment and RudderStack after the upgrade. Set the options back to restore them. A new consent option shows a cookie banner or a privacy choices link. Gated analytics scripts load only after a visitor approves.
MCP server and sidebar additions
The changelog lists more MCP work. Teams can define project-specific MCP tools in an @mcp folder. The connect-mcp tag supports ordering options. The execute tool gained an output schema. A submit-feedback tool lets agents report documentation issues through the MCP server. Sidebars gained tab entries in sidebars.yaml for grouping a project into sections. The preview command now takes the next free port and warns when the requested one is busy. Redocly listed about 70 fixes as well, covering the AI assistant, the Try it console, GraphQL, AsyncAPI, accessibility and dependency security updates.
Key takeaways
- Realm 0.138.0, dated Oct. 12, adds WebMCP for AI agents running in the reader’s browser.
- Segment and RudderStack page view tracking is now off by default.
- The
consentoption holds analytics scripts until a visitor approves. - A
prompttag and a Connect to Claude option put AI hand-offs on the page.
The take
We think the analytics default matters more to most teams than WebMCP. A default that flips to off fails quietly. Dashboards flatten and nobody gets an error. Check the Segment and RudderStack settings in redocly.yaml before upgrading, then compare page view counts a day later.
Try WebMCP on a preview site. It lets an agent act on a page the reader already has open. Mintlify listed it Sept. 25 and Redocly followed Oct. 12. We read that as browser agents becoming a normal docs audience. Test your own pages against one now.


