Skip to main content
Glama

browser-compat-mcp-server

Server Details

Browser compatibility and Baseline status for any web feature — offline, from bundled MDN data.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
cyanheads/browser-compat-mcp-server
GitHub Stars
1
Server Listing
browser-compat-mcp-server
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a distinct action: search by keyword, fetch one feature's record, batch-check Baseline status, evaluate against a custom browserslist query, and list reference vocabulary. The only real friction is between check_baseline and compare_support, which both do bulk per-feature support evaluation and return similar verdict/coverage shapes; only the extremely dense compare_support description makes the boundary clear.

Naming Consistency5/5

All five names share the browsercompat_ prefix followed by a clean verb_noun snake_case pattern (check_baseline, compare_support, get_feature, list_reference, search_features). The verbs match the actions precisely, so names are predictable and self-describing.

Tool Count5/5

Five tools is a tight, well-scoped surface for a compatibility-data server: discover, inspect, assess Baseline, assess against a target, and load the reference vocabulary. Nothing appears redundant and no tool feels like filler.

Completeness4/5

The lifecycle from unknown key to full record to ship decision is covered, with batching and pagination handled inside existing tools. Minor gap: there is no way to browse or filter features by group/category or Baseline date without already having a search keyword, so exploratory queries depend on search_features guessing well.

Available Tools

5 tools
browsercompat_check_baselineBrowsercompat Check BaselineA
Read-onlyIdempotent
Inspect

Check whether web features are safe to ship: Baseline state and the date it crossed, the browser and version that limits support, whether the feature is deprecated or discouraged, and the percentage points of global traffic that requiring it would exclude. Evaluates up to 20 BCD keys or web-features ids per call; up to 100 may be sent, and entries past the 20th come back unevaluated in omitted_features for the next call.

Inputs: features (required), resolve. Returns: error, results, totalCount, attribution, +4 more

browsercompat_compare_supportBrowsercompat Compare SupportA
Read-onlyIdempotent
Inspect

Compute whether a set of web features clears an explicit browserslist target query. Compares up to 20 features per call; up to 100 may be sent, and entries past the 20th come back unevaluated in omitted_features for the next call. Every call evaluates the whole query: each feature gets a verdict, the count of failing targets, those targets grouped into runs of consecutive query targets per browser in failing_ranges, and its own evaluated and unevaluated target counts with the percentage points of global traffic each covers. The target rows behind those numbers — which release each target maps to, which targets were not evaluated and why, and the failing and unevaluated targets of each feature, a failing row carrying the prefix, alternative name, or flag behind its verdict — cover target_limit query targets per call, 10 by default and up to 1000; page through them with target_offset, and the verdicts, coverage, and totals stay identical on every page. A target counts as evaluated only where compatibility data was read for it, so a feature clears only when every target in the query was evaluated and supports it, and is inconclusive otherwise — a query that includes a browser with no compatibility data, as "defaults" does, never clears. A BCD key is judged on its own per-browser support. A web-features id spanning several keys, such as grid, is judged on the release web-features lists for the feature as a whole in each Baseline core browser, as support_source says; its other browsers are not evaluated.

Inputs: targets (required), features (required), resolve, target_limit, +1 more. Returns: cap, error, shown, results, +18 more

browsercompat_get_featureBrowsercompat Get FeatureA
Read-onlyIdempotent
Inspect

Get the compatibility record for one web feature: Baseline state and the date it crossed, deprecation and standards status, per-browser version added and removed with flags, vendor prefixes and partial-implementation notes — with every other support statement recorded for that browser, such as an earlier prefixed or flagged release, in other_statements — and the MDN and specification links. Accepts a BCD key such as css.selectors.has or a web-features id such as has; the response echoes which one it matched. A web-features id that spans several BCD keys, such as grid, returns web-features’ own feature-level release per Baseline core browser in feature_support and its compat_keys, 100 per page, in place of per-key fields. An unresolved feature returns found: false with guidance rather than an error.

Inputs: feature (required), resolve, subkeys_offset, include_runtimes, +1 more. Returns: name, error, found, status, +18 more

browsercompat_list_referenceBrowsercompat List ReferenceA
Read-onlyIdempotent
Inspect

Enumerate the reference vocabulary this server uses: BCD namespaces, BCD browser ids, browserslist agent ids and their BCD counterparts, Baseline states, web-features groups, and ECMAScript snapshots. Use it to build valid inputs for the other tools and to see which target browsers can be evaluated.

Inputs: topic (required). Returns: error, topic, entries, attribution, +1 more

browsercompat_search_featuresBrowsercompat Search FeaturesA
Read-onlyIdempotent
Inspect

Find web features by plain name or keyword when the canonical key is unknown, across CSS, JavaScript, HTML, Web APIs, SVG, MathML, WebAssembly, and HTTP headers. Returns ranked matches with the BCD key, the web-features id, the Baseline state, a one-line support summary, and which field matched. Feed a result key into browsercompat_get_feature for the full record.

Inputs: query (required), group, limit, offset, +3 more. Returns: cap, error, shown, results, +7 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables checking web feature compatibility with Baseline standards, analyzing HTML, CSS, and JavaScript code to provide detailed reports on Baseline status, browser support, and recommendations.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides up-to-date CSS documentation and browser compatibility data from MDN through natural language queries. Features intelligent caching and supports all CSS properties, selectors, functions, and concepts with automatic normalization.
      90 npm
      339
      ISC
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.