@cyanheads/browser-compat-mcp-server

Browser compatibility and Baseline status for any web feature — offline, from MDN's browser-compat-data, web-features, and caniuse. STDIO or Streamable HTTP.

5 Tools

Public Hosted Server: https://browser-compat.caseyjhand.com/mcp

Overview

Web platform compatibility for frontend work: per-browser support from MDN's @mdn/browser-compat-data, Baseline state and dates from web-features, and browserslist target resolution weighted by caniuse-lite usage figures. Every dataset ships inside the package, so there are no runtime network calls, no API key, no rate limit, and no upstream to be down — the same answers come back air-gapped. Runs as a stdio process, a local Streamable HTTP server, or the public hosted endpoint above.

Tools

Tool	Description
`browsercompat_list_reference`	Enumerate the reference vocabulary the other tools expect — BCD namespaces and browser ids, browserslist agents, Baseline states, groups, and ECMAScript snapshots.
`browsercompat_get_feature`	Full compatibility record for one feature: Baseline state, standards status, per-browser versions with flags and prefixes, MDN and specification links.
`browsercompat_check_baseline`	Ship-or-not across up to 20 features: Baseline state and date, the limiting browser, deprecation flags, and the traffic share requiring it would exclude.
`browsercompat_search_features`	Find features by plain name, keyword, or code notation when the canonical key is unknown, ranked with the field that matched, filterable by group or ECMAScript snapshot, and pageable.
`browsercompat_compare_support`	Check features against an explicit browserslist target query: a whole-query verdict and evaluated coverage per feature, with the failing and unevaluated target rows paged ten query targets at a time.

Capability reference

`browsercompat_list_reference` _tool

Required topic: bcd_namespaces (12), bcd_browsers (17), browserslist_agents (19), baseline_states (4), groups (104), or snapshots (11). Group and snapshot ids feed the search filters.
Entries carry id, label, and detail, plus count, reported, bcd_browser, usage_percent, maps_from, or spec_url where applicable. An agent's bcd_browser: null means support comparisons cannot evaluate it and report it in unchecked_targets.

`browsercompat_get_feature` _tool

One feature, 1–200 characters: a BCD key (css.selectors.has) or web-features id (has). resolve: true accepts a name or notation only when the best exact matches name one feature: one key resolves directly, several keys of one feature return compat_keys, and two features are a miss. Off by default.
outcome is found, no_compat_data, or miss; resolved_as records the match. A miss returns found: false with guidance. A multi-key id omits support, status, limiting_browser, mdn_url, and spec_urls; use compat_keys for a specific call. Whitespace-only input returns invalid_feature_input.
include_runtimes: true adds bun, deno, nodejs, and oculus support to the 13 desktop and mobile browser rows.
Feature-level discouraged is independent of BCD status; status.discouraged remains a compatibility alias when status exists. Unsupported and preview-only rows retain their available notes and tracking links.
limiting_browser appears only when every Baseline core browser has full, unprefixed, unflagged support at a resolvable added release.
A key with direct callable children returns subkeys: { total, keys, truncated, next_offset? }, at most 100 at a time. Continue with subkeys_offset (integer ≥0, default 0). Call one child with this tool or up to 20 with browsercompat_check_baseline; grandchildren and structural nodes are excluded.

`browsercompat_check_baseline` _tool

Up to 20 BCD keys or web-features ids, 1–200 characters each, with one result per entry in input order. A whitespace-only entry returns invalid_feature_input.
Results carry Baseline state and dates, limiting_browser under the full-support condition above, deprecated, experimental, and discouraged. usage_percent_excluded and usage_source describe the caniuse feature: a BCD key receives them only when it is the feature's sole declared compat key. Usage is absent when the scope differs or caniuse data is missing, never a fabricated zero.
all_widely_available requires every entry to resolve at widely; one miss makes it false, and it does not assess deprecation.

`browsercompat_search_features` _tool

query, 1–100 characters, accepts names, keywords, or notation such as Array.prototype.at, display: grid, or <dialog>. Combine namespace (12 BCD namespaces), baseline (widely, newly, limited, not_mapped), group (including nested groups), and snapshot (such as ecmascript-2023).
matched_on explains the six-tier ranking; path_suffix marks trailing key segments matching the supplied notation. support_summary covers the seven Baseline core browsers (— unsupported, ? unknown). Typed failures: invalid_query (zero searchable tokens), unknown_group, unknown_snapshot.
Page with limit (1–50, default 10) and offset (default 0); totalCount counts all matches and nextOffset appears while more remain. Zero hits succeed with a notice naming which filter to drop; an offset past the matches returns an empty page with a notice.

`browsercompat_compare_support` _tool

Up to 20 features against a required targets browserslist query, such as defaults or > 0.5%, last 2 versions; local browserslist config is never used. Typed failures: invalid_target_query, no_targets_resolved, invalid_feature_input.
Every call evaluates the whole query. Each verdict is clears, fails, inconclusive, miss, or ambiguous: fails when any evaluated target lacks support, clears only when every target in the query was evaluated and supports the feature, inconclusive otherwise. A query that includes a browser with no compatibility data, as defaults does, never clears. all_clear is true only when every feature clears.
A target counts as evaluated only where compatibility data was read for it. Each compared result carries failing_total, evaluated_total, evaluated_coverage_percent, unchecked_total, and unchecked_coverage_percent. The top level carries comparable_features, targets_resolved_total, evaluated_targets_total, unchecked_targets_total, and the caniuse-derived target_coverage_percent and unchecked_coverage_percent: the share covered by the targets evaluated for every compared feature, and by the rest of the query.
Target rows are paged with target_offset (integer ≥0, default 0) and target_limit (1–10, default 10). targets_resolved (the mapping inventory, each row flagged evaluated), unchecked_targets, and each result's failing_targets and unchecked_targets cover only the query targets on the page; verdicts, coverage, and totals are identical on every page. totalCount counts the targets in the query and nextOffset appears while more remain; an offset past the end returns the summaries with no rows and a notice.
failing_targets names targets with partial, prefixed, flagged, removed, unsupported, or preview_only support. unchecked_targets carries no_bcd_browser, unknown_version, no_bcd_data, or no_comparable_feature — the last when every entry was a miss or ambiguous, so nothing was compared.

Data sources

Package	Version	License	Supplies
`@mdn/browser-compat-data`	`^8.1.3`	CC0-1.0	Per-browser support, standards status, MDN and specification links
`web-features`	`^3.40.0`	Apache-2.0	Baseline state and dates, discouraged flags, groups, ECMAScript snapshots
`caniuse-lite`	`^1.0.30001812`	CC-BY-4.0	Usage weighting, plus feature titles for the search index
`browserslist`	`^4.29.1`	MIT	Target query resolution and coverage figures

CC BY 4.0 requires attribution wherever the caniuse data travels, so every response carrying a usage figure carries this string: Usage data from caniuse.com, © Can I Use contributors, CC BY 4.0. Figures are a share of the ~97.3% of global traffic caniuse tracks. Full license texts and notices are in THIRD_PARTY_NOTICES.md.

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

Browser-compat-specific:

All four datasets are bundled and loaded in process — no runtime network calls, no API key, no rate limit, and nothing to configure
Baseline is read per browser-compat-data key from status.by_compat_key, never rolled up from the feature level, because keys under one feature legitimately disagree
One shared resolver behind every tool: exact BCD key, then web-features id, then a moved redirect, and only under resolve: true the search index's best exact matches, when they name one feature
Target versions are ordered by browser-compat-data's release index rather than parsed version strings, with the caniuse spellings normalized both directions (safari 16.0 ↔ 16, samsung 20 ↔ 20.0)

Agent-friendly output:

Every response echoes data_version — the version of each bundled dataset behind the answer, since a pinned snapshot goes stale on exactly the newest features
A pass is never claimed for a browser that was not evaluated: a feature clears a target query only when compatibility data was read for every target in it, and a target without data is reported in unchecked_targets and makes the verdict inconclusive
Misses are results, not failures — found: false with guidance naming the next call, and typed error reasons carrying recovery hints for the input a caller has to fix
Usage figures state the population they are a share of, and carry the caniuse attribution on every response that reports one
BCD markup becomes plain text with anchor labels and URLs preserved. Markdown renders literal names such as <dialog> visibly; structured text keeps the original plain-text element names.

Getting started

Public Hosted Instance

A public instance is available at https://browser-compat.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:

{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "type": "streamable-http",
      "url": "https://browser-compat.caseyjhand.com/mcp"
    }
  }
}

Self-Hosted / Local

Add the following to your MCP client configuration file:

{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@cyanheads/browser-compat-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with npx (no Bun required):

{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cyanheads/browser-compat-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with Docker:

{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "MCP_TRANSPORT_TYPE=stdio",
        "ghcr.io/cyanheads/browser-compat-mcp-server:latest"
      ]
    }
  }
}

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp

Prerequisites

Bun v1.4.0 or higher (or Node.js v24+).
No API keys, accounts, or network access required — every dataset ships with the package.

Installation

Clone the repository:

git clone https://github.com/cyanheads/browser-compat-mcp-server.git

Navigate into the directory:

cd browser-compat-mcp-server

Install dependencies:

bun install

Configure environment (optional):

cp .env.example .env
# edit .env if you want to override transport or logging defaults

Configuration

There are no server-specific environment variables: no API keys, no base URLs, and deliberately no browserslist configuration variable — the target query is always a tool input rather than ambient state. Framework transport, logging, and telemetry settings remain configurable.

Variable	Description	Default
`MCP_TRANSPORT_TYPE`	Transport: `stdio` or `http`.	`stdio`
`MCP_HTTP_PORT`	Port for the HTTP server.	`3010`
`MCP_SESSION_MODE`	HTTP session mode, explicitly set by `.env.example` and Docker. When unset, the framework's `auto` fallback resolves to `stateful`.	`stateless`
`OTEL_ENABLED`	Enable OpenTelemetry; local installs need the framework's optional telemetry peers. Docker includes them by default.	`false`
`OTEL_EXPORTER_OTLP_ENDPOINT`	Base URL for traces (`/v1/traces`) and metrics (`/v1/metrics`); signal-specific endpoints override it.	Unset
`OTEL_EXPORTER_OTLP_LOGS_ENDPOINT`	Explicit OTLP log endpoint, used as-is; the base endpoint never enables log export.	Unset
`LOG_TOOL_FAILURE_PAYLOADS`	Log failed-call arguments and results. Redaction matches key names only; free-form values can retain secrets.	`false`
`LOG_TOOL_FAILURE_PAYLOAD_MAX_BYTES`	UTF-8 byte cap per logged payload.	`16384`

See .env.example for the full list of optional framework overrides.

Running the server

Local development

# One-time build
bun run rebuild

# Run the built server
bun run start:stdio
# or
bun run start:http

bun run devcheck   # Lint, format, typecheck, security
bun run test       # Vitest test suite
bun run lint:mcp   # Validate MCP definitions against spec

Docker

docker build -t browser-compat-mcp-server .
docker run --rm -p 3010:3010 browser-compat-mcp-server

The Dockerfile defaults to HTTP transport, stateless session mode, and logs to /var/log/browser-compat-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.

Project structure

Directory	Purpose
`src/index.ts`	`createApp()` entry point — registers the tools and warms the datasets.
`src/data/`	The browserslist agent to browser-compat-data browser map.
`src/mcp-server/tools/`	Tool definitions (`*.tool.ts`) and the output shapes they share.
`src/services/`	bcd, baseline, targets, search, and data-version services over the bundled datasets.
`src/types/`	Ambient module declaration for `caniuse-lite`, which ships no types.
`tests/`	Vitest suites mirroring `src/`.
`docs/`	`design.md` — the surface, the data shapes behind it, and the decisions log.
`changelog/`	Per-version changelog files.

The generated file tree is docs/tree.md.

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

Handlers throw, framework catches — no try/catch in tool logic
Use ctx.log for request-scoped logging, ctx.state for tenant-scoped storage
Register new tools directly in src/index.ts
Data integrity: read the bundled datasets as they are and preserve their uncertainty; never fabricate a support fact the data does not carry

Contributing

Issues are welcome. Run checks and tests before submitting:

bun run devcheck
bun run test

License

Apache-2.0 — see LICENSE for details.

Name		Name	Last commit message	Last commit date
.claude-plugin		.claude-plugin
.codex-plugin		.codex-plugin
.github		.github
.vscode		.vscode
changelog		changelog
docs		docs
framework-skills		framework-skills
scripts		scripts
src		src
tests		tests
.dockerignore		.dockerignore
.env.example		.env.example
.gitattributes		.gitattributes
.gitignore		.gitignore
.mcpbignore		.mcpbignore
AGENTS.md		AGENTS.md
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
Dockerfile		Dockerfile
LICENSE		LICENSE
README.md		README.md
THIRD_PARTY_NOTICES.md		THIRD_PARTY_NOTICES.md
biome.json		biome.json
bun.lock		bun.lock
bunfig.toml		bunfig.toml
devcheck.config.json		devcheck.config.json
manifest.json		manifest.json
package.json		package.json
server.json		server.json
tsconfig.build.json		tsconfig.build.json
tsconfig.json		tsconfig.json
vitest.config.ts		vitest.config.ts

Navigation Menu

Repository files navigation

@cyanheads/browser-compat-mcp-server

Overview

Tools

Capability reference

`browsercompat_list_reference` _tool

`browsercompat_get_feature` _tool

`browsercompat_check_baseline` _tool

`browsercompat_search_features` _tool

`browsercompat_compare_support` _tool

Data sources

Features

Getting started

Public Hosted Instance

Self-Hosted / Local

Prerequisites

Installation

Configuration

Running the server

Local development

Docker

Project structure

Development guide

Contributing

License

About

Releases

Packages

Used by

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

@cyanheads/browser-compat-mcp-server

Overview

Tools

Capability reference

browsercompat_list_reference tool

browsercompat_get_feature tool

browsercompat_check_baseline tool

browsercompat_search_features tool

browsercompat_compare_support tool

Data sources

Features

Getting started

Public Hosted Instance

Self-Hosted / Local

Prerequisites

Installation

Configuration

Running the server

Local development

Docker

Project structure

Development guide

Contributing

License

About

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

`browsercompat_list_reference` _tool

`browsercompat_get_feature` _tool

`browsercompat_check_baseline` _tool

`browsercompat_search_features` _tool

`browsercompat_compare_support` _tool