Analyzes CSS code for Baseline compatibility, providing a detailed compatibility report with detected features, browser support warnings, and recommendations.
Analyzes JavaScript code for Baseline compatibility, providing a detailed compatibility report with detected features, browser support warnings, and recommendations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Baseline Checker Check if display: grid; is Baseline compatible"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server to check web feature compatibility with Baseline standards.
Baseline Tooling Hackathon - Accelerate availability of modern web features
npm install
npm run buildRelated MCP server: CSS MCP Server
{
"servers": {
"baseline-checker": {
"command": "node",
"args": ["/<absolute path to your project>/dist/index.js"]
}
}
}{
"mcpServers": {
"baseline-checker": {
"command": "node",
"args": ["/<absolute path to your project>/dist/index.js"]
}
}
}You can test this MCP server with the inspection tool:
npx @mcpjam/inspector@latestMore info: https://github.com/MCPJam/inspector
check_baselineAnalyzes complete HTML/CSS/JavaScript code for Baseline compatibility.
Input: Complete code to analyze Output: Detailed compatibility report with:
Compatibility percentage
Detected web features grouped by status (Baseline, Non-Baseline, Discouraged)
Browser support warnings
Specific recommendations and alternatives
Usage: "Analyze this code for Baseline compatibility: [paste your code]"
check_baseline_from_selectionAutomatic code retrieval tool.
Input: Source type (selection, active_file, or clipboard)
Output: Instructions for the AI agent to:
Use editor tools to access the selected/active code
Pass the retrieved code to the check_baseline tool
Provides guidance for proper workflow integration
Purpose: Directs AI agents to use proper workflow for code analysis
"Analyze this code for Baseline compatibility: [your code]"
"Check if this HTML/CSS/JS is Baseline compatible"
Use check_baseline tool with your code for immediate analysis
Analyzes web code for Baseline compatibility. Pass the complete code to get compatibility percentage and specific issues.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Complete HTML/CSS/JavaScript code to analyze |
AUTOMATIC CODE RETRIEVAL: Analyzes the currently selected code or active file for Baseline compatibility. No need to copy/paste code - this tool automatically gets the code from the editor. Use this to save tokens and avoid manual code copying.
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | Source of code to analyze: 'selection' for selected text, 'active_file' for current file, or 'clipboard' for clipboard content |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0check_baselinecheck_baseline_from_selectionScored across 2 tools
Both tools perform Baseline compatibility analysis, but their input mechanisms are clearly distinguished: one takes explicit code, the other auto-retrieves the current selection/file. The descriptions make the intended use cases distinct enough to avoid most misselection.
Both tools use a consistent snake_case verb_noun pattern with a shared 'check_baseline' prefix. The suffix clearly denotes the variant.
Two tools is on the low end, but appropriate for a narrow single-purpose checker. One tool handles explicit code and the other handles automatic editor retrieval, so each earns its place without redundancy.
The server covers the core workflow of checking Baseline compatibility, both for pasted code and current editor context. Minor gaps like batch or directory-level checks exist, but the primary use cases are well covered.
Browser compatibility and Baseline status for any web feature — offline, from bundled MDN data.
What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data.
Scan URLs or HTML for WCAG 2.2 violations. 75-rule manifest, weighted score, shareable reports.
Audit public webpages and supplied markup for HTML, CSS, SEO, JSON-LD, and link issues.
