Skip to main content
Glama
@shuji-bonji/web-compat-mcp

@shuji-bonji/web-compat-mcp

by shuji-bonji

Web Compat MCP server

CI npm version License: MIT

MCP server providing browser compatibility data for the entire Web Platform.

Answers the question: "Does this actually work in browsers?"

Uses MDN Browser Compat Data (BCD) (15,000+ features) and W3C WebDX web-features (1,000+ features with Baseline status) to provide real-world browser implementation status.

Fully offline β€” all data is bundled via npm packages. No API calls, zero latency.

πŸ‡―πŸ‡΅ ζ—₯本θͺžη‰ˆ README はこけら

Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚           web-compat-mcp server             β”‚
β”‚                                             β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚ @mdn/browser- β”‚  β”‚   web-features    β”‚   β”‚
β”‚  β”‚  compat-data  β”‚  β”‚  (W3C WebDX CG)   β”‚   β”‚
β”‚  β”‚  15K+ featuresβ”‚  β”‚  1K+ features     β”‚   β”‚
β”‚  β”‚  BCD JSON     β”‚  β”‚  Baseline status  β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β”‚          β”‚   cross-reference β”‚              β”‚
β”‚          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜              β”‚
β”‚                   β”‚                         β”‚
β”‚          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”                β”‚
β”‚          β”‚   7 MCP Tools   β”‚                β”‚
β”‚          β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜                β”‚
β”‚                   β”‚ stdio                   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                    β”‚
            MCP Client (Claude, etc.)

Related MCP server: w3c-mcp

Tools

Tool

Description

compat_check

Check browser compatibility for a single feature (BCD dot notation)

compat_search

Search 15,000+ BCD features by keyword

compat_get_baseline

Get Baseline status for a web feature (web-features kebab-case)

compat_list_baseline

List features filtered by Baseline status

compat_compare

Compare browser compatibility across 2–5 features side by side

compat_list_browsers

List all tracked browsers with versions

compat_check_support

Find features added in a specific browser version

Identifier conventions

The two data sources use different identifier schemes, and each tool expects a specific one:

Tool

Scheme

Example

compat_check, compat_compare, compat_search

BCD dot notation β€” fine-grained, often camelCase

api.PushManager, css.properties.grid

compat_get_baseline, compat_list_baseline

web-features kebab-case β€” coarse, feature-group

push, container-queries

compat_check_support

Browser id + version string

safari + 17

BCD is fine-grained (api.PushManager, api.PushEvent, api.PushSubscription are separate entries) while web-features groups related specs into a single feature (push covers all three). When unsure of the exact identifier, run compat_search first. Input normalization handles kebab-case queries (view-transition β†’ viewtransition) and trailing .0 versions (17.0 β†’ 17) automatically.

Quick Start

Requires Node.js 22 or later.

npx (no install)

npx -y @shuji-bonji/web-compat-mcp@latest

npm (global)

npm install -g @shuji-bonji/web-compat-mcp
web-compat-mcp

MCP Client Configuration

Claude Desktop

Add to claude_desktop_config.json:

{
	"mcpServers": {
		"web-compat": {
			"command": "npx",
			"args": ["-y", "@shuji-bonji/web-compat-mcp@latest"]
		}
	}
}

Claude Code

claude mcp add web-compat -- npx -y @shuji-bonji/web-compat-mcp@latest

VS Code (Copilot / Continue)

Add to .vscode/mcp.json:

{
	"servers": {
		"web-compat": {
			"command": "npx",
			"args": ["-y", "@shuji-bonji/web-compat-mcp@latest"]
		}
	}
}

Usage Examples

Check browser compatibility

"Is Push API supported in Safari?"

β†’ compat_check feature: "api.PushManager"

Returns version support across browsers, Baseline status, and links to MDN/spec documentation.

Search features

"Find CSS grid features"

β†’ compat_search query: "grid" category: "css"

Returns matching feature IDs with standard/experimental/deprecated flags.

Compare features

"Compare fetch vs XMLHttpRequest"

β†’ compat_compare features: ["api.fetch", "api.XMLHttpRequest"]

Returns side-by-side comparison table with version support and Baseline status.

Check Baseline status

"Is container queries Baseline?"

β†’ compat_get_baseline feature: "container-queries"

Returns Baseline level (Widely Available / Newly Available / Not Baseline), browser support, and related BCD features.

Find features by browser version

"What CSS features were added in Chrome 120?"

β†’ compat_check_support browser: "chrome" version: "120" category: "css"

Returns features added in the specified browser version.

Workflow: combining multiple tools

"I want to use Push API in my PWA β€” is it realistic today?"

Step 1 β†’ compat_check        feature: "api.PushManager"
         # Per-API browser versions (Chrome 42+, Safari 16+, Firefox 44+)

Step 2 β†’ compat_get_baseline  feature: "push"
         # Feature-group view: Newly Available since 2023-03-27

Step 3 β†’ compat_compare       features: ["api.PushManager", "api.Notification"]
         # Side-by-side when your PWA depends on both

Chained with a spec-oriented server such as W3C MCP or RFCXML MCP, the LLM can answer both "what does the spec require?" and "what actually works in browsers today?" in a single conversation.

Output Formats

All tools support response_format parameter:

  • "markdown" (default) β€” Human-readable tables and formatted text

  • "json" β€” Structured data with structuredContent for programmatic use

Complementary MCP Servers

This server is designed to work alongside other MCP servers:

Server

Role

This Server's Complement

W3C MCP

Spec definitions (MUST/SHOULD/MAY)

Real browser implementation status

RFCXML MCP

RFC requirements

Browser-level protocol support

css-mcp

CSS docs + code analysis

Platform-wide compat + Baseline

Data Sources

Source

Package

Features

Update Frequency

MDN BCD

@mdn/browser-compat-data

15,000+

Weekly

web-features

web-features

1,000+

Monthly

Development

# Install dependencies
npm install

# Build
npm run build

# Run tests
npm test              # Unit tests (94 tests)
npm run test:e2e      # E2E tests via JSON-RPC (10 tests)

# Lint & format (Biome 2.x)
npm run lint          # Check
npm run lint:fix      # Auto-fix
npm run format        # Format

# Type check (TypeScript 7)
npm run typecheck

License

MIT β€” see LICENSE

Available Tools

7 tools
compat_checkCheck Browser CompatibilityA
Read-onlyIdempotent

Check browser compatibility for a specific web platform feature using MDN Browser Compat Data (BCD).

Returns version support across browsers, Baseline status, and links to MDN/spec documentation.

Args:

  • feature (string): BCD identifier in dot notation (e.g., "api.PushManager", "css.properties.grid", "javascript.builtins.Promise")

  • browsers (string[], optional): Filter to specific browsers (e.g., ["chrome", "safari"]). Defaults to desktop browsers.

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Browser support versions, Baseline status, standard/experimental/deprecated flags, and MDN/spec links.

Examples:

  • "Is Push API supported in Safari?" β†’ feature: "api.PushManager"

  • "Can I use CSS grid?" β†’ feature: "css.properties.grid"

  • "Is Array.at() widely available?" β†’ feature: "javascript.builtins.Array.at"

Inputs: feature (required), browsers, response_format.

compat_check_supportCheck Browser Version SupportA
Read-onlyIdempotent

Find web platform features that were added in a specific browser version.

Useful for understanding what new capabilities became available in a particular browser release.

Args:

  • browser (string): Browser identifier (e.g., "safari", "chrome", "firefox")

  • version (string): Browser version (e.g., "17.0", "120", "121")

  • category (string, optional): Filter by BCD category (e.g., "api", "css")

  • limit (number): Max results (default: 20, max: 100)

  • offset (number): Pagination offset (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: List of features added in the specified browser version.

Examples:

  • "What was added in Safari 17.0?" β†’ browser: "safari", version: "17.0"

  • "New CSS features in Chrome 120" β†’ browser: "chrome", version: "120", category: "css"

  • "Firefox 121 API additions" β†’ browser: "firefox", version: "121", category: "api"

Inputs: browser (required), version (required), limit, offset, +2 more.

compat_compareCompare Browser CompatibilityA
Read-onlyIdempotent

Compare browser compatibility across multiple web platform features side by side.

Useful for choosing between alternative APIs or understanding support differences.

Args:

  • features (string[]): 2-5 BCD feature identifiers to compare (e.g., ["api.fetch", "api.XMLHttpRequest"])

  • browsers (string[], optional): Filter to specific browsers. Omit for default desktop browsers.

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Side-by-side comparison table showing version support for each feature across browsers.

Examples:

  • Compare fetch vs XMLHttpRequest β†’ features: ["api.fetch", "api.XMLHttpRequest"]

  • Compare CSS layout methods β†’ features: ["css.properties.grid", "css.properties.flex"]

  • Compare storage APIs β†’ features: ["api.localStorage", "api.sessionStorage", "api.IndexedDB"]

Inputs: features (required), browsers, response_format.

compat_get_baselineGet Baseline StatusA
Read-onlyIdempotent

Get the Baseline status for a web platform feature from W3C WebDX web-features data.

Baseline indicates whether a feature is supported across all major browsers:

  • "high" (Widely Available): Supported for 30+ months across all core browsers

  • "low" (Newly Available): Recently became interoperable across all core browsers

  • false (Not Baseline): Not yet supported across all core browsers

Args:

  • feature (string): web-features identifier in kebab-case (e.g., "container-queries", "push", "view-transitions")

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Baseline status, browser support versions, related BCD features, and spec links.

Examples:

  • "Is container queries Baseline?" β†’ feature: "container-queries"

  • "Is the Push API widely available?" β†’ feature: "push"

  • "Check View Transitions baseline" β†’ feature: "view-transitions"

Inputs: feature (required), response_format.

compat_list_baselineList Features by Baseline StatusA
Read-onlyIdempotent

List web platform features filtered by their Baseline status.

Use this to discover which features are Widely Available, Newly Available, or not yet Baseline.

Args:

  • status (string, optional): Filter by "high" (Widely Available), "low" (Newly Available), or "false" (Not Baseline)

  • group (string, optional): Filter by feature group (e.g., "css", "javascript", "forms")

  • limit (number): Max results (default: 20, max: 100)

  • offset (number): Pagination offset (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Paginated list of features with their Baseline status and availability dates.

Examples:

  • "List all Widely Available features" β†’ status: "high"

  • "What CSS features are Newly Available?" β†’ status: "low", group: "css"

  • "What features aren't Baseline yet?" β†’ status: "false"

Inputs: group, limit, offset, status, +1 more.

compat_list_browsersList Tracked BrowsersA
Read-onlyIdempotent

List all browsers tracked in MDN Browser Compat Data with their current versions and release dates.

Args:

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: List of browsers with id, name, type (desktop/mobile/server), current version, and release date.

Examples:

  • "What browsers are tracked?" β†’ no params needed

  • "List all browser versions" β†’ no params needed

Inputs: response_format.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking a feature's compatibility, finding features by version, comparing features across features, getting Baseline status, listing features by Baseline status, listing browsers, and searching for features. No ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'compat_<verb>' or 'compat_<verb>_<noun>' pattern in snake_case. Names like compat_check, compat_search, compat_compare are predictable and descriptive.

    Tool Count5/5

    Seven tools is well-scoped for a web compatibility server. It covers all essential query operations without being bloated or too sparse.

    Completeness5/5

    The tool set covers the full query lifecycle: discovery (search, list baselines), single feature lookup (check, get baseline), comparison, and version-specific queries. No major gaps for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP Server for accessing W3C/WHATWG/IETF web specifications. Provides AI assistants with access to official web standards data including specifications, WebIDL definitions, CSS properties, and HTML elements.
      11
      29 npm
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that queries the baseline status of web platform features using data from webstatus.dev. It provides tools to get feature baseline status and a summary of baseline categories.
      2
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for exploring the ECMAScript specification and its implementation, enabling semantic search of spec sections, JavaScript execution in engine262, and access to a knowledge graph linking spec sections to implementation functions.
      19 npm
      ISC