@shuji-bonji/web-compat-mcp
Related Servers
Alternatives to @shuji-bonji/web-compat-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that provides browser compatibility data and web API support information using caniuse.com, MDN BCD, and Web Features, enabling developers to check feature support across browsers and against browserslist configurations.38 npm5MIT
- AlicenseAqualityBmaintenanceMCP 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.11363 npm4MIT
- FlicenseBqualityDmaintenanceAn 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.21-
- AlicenseNot gradedqualityBmaintenanceMCP server that checks the Baseline status using Web Platform APIs.37MIT
- AlicenseAqualityDmaintenanceMCP server that provides access to web accessibility documentation, enabling search and retrieval of W3C WAI-ARIA patterns and accessibility best practices.34 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.8 npmISC
TDQS
Scored across 7 tools
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.
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.
Seven tools is well-scoped for a web compatibility server. It covers all essential query operations without being bloated or too sparse.
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.