CanIUse MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable verbose logging with debug pattern (e.g. 'caniuse-mcp*') | |
| CANIUSE_OVERRIDES | No | Set feature overrides as JSON object string | |
| CANIUSE_POLYFILLS | No | Configure polyfills as JSON array string | |
| CANIUSE_DEFAULT_BASELINE | No | Set default baseline browser target |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_projectC | Analyze project files to detect CSS/JS features and check compatibility across browser targets |
| check_compatibilityC | Check specific features or files against multiple browser targets with detailed analysis |
| get_fixesA | Get actionable remediation steps, polyfills, and alternatives for unsupported features |
| generate_configsC | Generate complete build configurations, CI/CD setups, and workflow files for browser compatibility |
| manage_configC | Configure browser baselines, polyfills, and feature overrides for more accurate compatibility checking |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: check_compatibility for specific feature analysis, generate_configs for build setup, get_fixes for remediation, manage_config for configuration, and scan_project for project-wide analysis. The descriptions clearly differentiate their scopes, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., check_compatibility, generate_configs, get_fixes, manage_config, scan_project). The naming is uniform and predictable, using snake_case throughout with clear action-oriented verbs.
With 5 tools, the count is well-scoped for a browser compatibility server. Each tool earns its place by covering distinct aspects of the domain, from checking and scanning to configuration and remediation, without being too sparse or bloated.
The tool set provides complete coverage for browser compatibility workflows: checking features, scanning projects, generating configurations, managing settings, and getting fixes. There are no obvious gaps, as it supports the full lifecycle from detection to resolution.