Command Palette

Search for a command to run...

UnylyUnyly
Browse all

Web Compat

FreeNot checked

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

GitHubEmbed

About

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

README

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.)

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

from github.com/shuji-bonji/web-compat-mcp

Installing Web Compat

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/shuji-bonji/web-compat-mcp

FAQ

Is Web Compat MCP free?

Yes, Web Compat MCP is free — one-click install via Unyly at no cost.

Does Web Compat need an API key?

No, Web Compat runs without API keys or environment variables.

Is Web Compat hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Web Compat in Claude Desktop, Claude Code or Cursor?

Open Web Compat on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare Web Compat with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All browse MCPs