DocsWebMCP

WebMCP Browser Tools

BugsPulse registers tools in the browser via the WebMCP API so AI agents running inside your browser can interact with the site directly.

What is WebMCP?

WebMCP is a browser API (navigator.modelContext) that lets websites register tools an AI agent can call while the user is on the page. Think of it as the browser-native equivalent of a server MCP — no separate HTTP connection needed. Agents running in supported browsers (currently Chrome with the WebMCP origin trial enabled) can discover and call these tools automatically.

BugsPulse registers four tools on every page load. They become available to any AI agent with browser access the moment the page opens.

Browser support: WebMCP is currently available in Chrome via an Early Preview Programme (origin trial). The tools are registered safely — on browsers without WebMCP support the code does nothing. No errors, no impact on page performance.

Registered Tools

get_pricing

Fetches live BugsPulse pricing plans from the API — features, session limits, and prices for every tier.

Arguments: None

list_blog_posts

Returns a list of published BugsPulse blog posts. Useful for agents that need to surface relevant articles.

Arguments: limit (number, optional) — max posts to return, default 20

navigate_to

Navigates the browser to a BugsPulse page.

Arguments: page (string, required) — one of: home, pricing, blog, docs, docs/sdk/react-native, docs/sdk/flutter, contact, react-native, flutter, expo, changelog

get_docs_urls

Returns all documentation and integration URLs including the SDK guides, REST API reference, and MCP server endpoint.

Arguments: None

How It Works

The tools are registered via a React client component that runs on every page of bugspulse.com. Here is a simplified version of what happens:

// Runs on page load in the user's browser
const controller = new AbortController();

navigator.modelContext.registerTool({
  name: "get_pricing",
  description: "Get BugsPulse pricing plans",
  inputSchema: { type: "object", properties: {}, required: [] },
  execute: async () => {
    const res = await fetch("https://api.bugspulse.com/billing/plans");
    return res.json();
  },
}, { signal: controller.signal });

// Tools are automatically unregistered when the user leaves the page

WebMCP vs. MCP Server

WebMCPMCP Server

AccessBrowser onlyAny MCP client

AuthNone — public data onlySession cookie required

Use caseMarketing site toolsFull crash & session data

Endpointnavigator.modelContexthttps://api.bugspulse.com/mcp

For full programmatic access to crash reports and analytics, use the MCP Server. WebMCP is designed for lightweight, public-facing interactions on the marketing site.