# BOP Data WebMCP

> Progressive browser-agent access for data.bop.ink. WebMCP is separate from the external MCP server.

Capability status: available

WebMCP tools are registered only when the browser exposes `document.modelContext`. Normal browsing never depends on WebMCP support.

## Dataset pages

- `bop.read_dataset` — read-only tool for the canonical dataset currently open in the browser.

## Catalog

- `bop.search_datasets` — read-only tool for searching the public catalog by text/category.

## Data contract

WebMCP handlers read the same public JSON/API representations used by the rest of BOP Data. They do not hold a separate hidden data model.

## Invocation contract

The 28 September 2026 draft defines tool execution callbacks as execute(input) and in-page invocation as document.modelContext.executeTool(registeredTool, inputObject). BOP follows that object-input contract.

## Compatibility

WebMCP remains a W3C Community Group draft. BOP uses feature detection, follows the current object-input contract, and keeps normal browsing independent of browser support. Verified with Chrome for Testing 155.0.8059.12 using the WebMCP testing feature enabled; Chrome may serialize a tool result to JSON text for page-script callers, so parse that text before comparing it with the canonical JSON API.

External MCP server documentation: https://data.bop.ink/mcp.md
Website discovery: https://data.bop.ink/llms.txt