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

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.

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, deprecated, experimental, discouraged, and usage_percent_excluded with its usage_source. Usage is absent, never zero, when no caniuse id exists.
• 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.
• Each verdict is clears, fails, inconclusive, miss, or ambiguous. failing_targets names targets with partial, prefixed, flagged, removed, unsupported, or preview_only support.
• unchecked_targets carries no_bcd_browser, unknown_version, or no_bcd_data; all_clear requires it to be empty. The response also includes caniuse-derived target_coverage_percent and unchecked_coverage_percent.

Data sources

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 ~96.7% 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 verdict is never claimed for a browser that was not evaluated: unknown support moves the target into unchecked_targets and the feature to 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

Getting started

Public Hosted Instance