w3c-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| W3C_MCP_PERF | No | Enable performance logging only. | |
| W3C_MCP_DEBUG | No | Enable debug logging. Debug output includes tool call arguments, execution timing, and data loading performance. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_w3c_specsA | List W3C/WHATWG/IETF web specifications with optional filtering by organization, keyword, or category |
| get_w3c_specB | Get detailed information about a specific web specification including URLs, status, repository, and test info |
| search_w3c_specsA | Search web specifications by query string, searching in title, shortname, and description |
| get_webidlC | Get WebIDL interface definitions for a specification. WebIDL defines the JavaScript APIs. |
| list_webidl_specsB | List all specifications that have WebIDL definitions available |
| get_css_propertiesB | Get CSS property definitions from a specific spec or all specs |
| list_css_specsB | List all CSS specifications that have property definitions available |
| get_html_elementsC | Get HTML element definitions from a specific spec or all specs |
| list_element_specsB | List all specifications that have HTML element definitions available |
| get_pwa_specsC | Get all Progressive Web App (PWA) related specifications including Service Worker, Web App Manifest, Push API, Background Sync, etc. |
| get_spec_dependenciesA | Get basic information for a specification. Note: Dependency data (dependencies/dependents) is not yet available from the upstream data source and currently returns empty arrays. |
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 11 tools
Every tool has a clearly distinct purpose with no overlap. The tools are organized around specific resources (CSS properties, HTML elements, PWA specs, WebIDL, general specs) and actions (get vs. list vs. search), making it easy for an agent to select the right one. For example, get_css_properties retrieves property definitions, while list_css_specs enumerates available specs, avoiding confusion.
The naming follows a highly consistent verb_noun pattern throughout, using snake_case uniformly. All tools start with either 'get_', 'list_', or 'search_' followed by a clear noun phrase (e.g., get_css_properties, list_w3c_specs). This predictability makes the tool set easy to navigate and understand at a glance.
With 11 tools, the count is well-scoped for the server's purpose of accessing W3C web specifications and related data. Each tool earns its place by covering distinct aspects like CSS, HTML, PWA, WebIDL, and general spec operations, without being overly broad or sparse. This aligns with typical MCP server ranges (3-15 tools) for focused domains.
The tool surface is nearly complete for the domain of retrieving W3C specification data, covering key operations like getting details, listing, and searching across various resource types. A minor gap exists in update or modification tools, but this is reasonable as the server appears focused on read-only access to public specs, and agents can work around this limitation for typical querying tasks.