Server facts
w3c-mcp
Project
- Author
- shuji-bonji
- Repository
- github.com/shuji-bonji/w3c-mcp
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 4
- Last commit
- Data as of
Tags
- Documentation
- css
- html
- pwa
- specifications
- w3c
- web standards
- webidl
Overview
Web standards research in w3c-mcp starts with finding a specification by topic, organization, or category, then retrieving its metadata by shortname. Search covers titles, shortnames, and descriptions, while individual records include links, status, repository details, and test information. For developers using AI assistants to examine browser APIs or markup, separate tools retrieve WebIDL interfaces, CSS property definitions, and HTML element definitions. Discovery tools also identify which specifications have each kind of definition available, helping users choose a source before requesting its contents.
PWA research has a dedicated lookup covering related standards, with an option to narrow results to Service Worker, Manifest, Push, and Notifications. Users can follow that selection with individual specification lookups or inspect definitions for a particular API, property, or element. The underlying sources are W3C-maintained packages containing specification metadata and machine-readable material extracted from official standards. One limitation matters for dependency research: the deprecated dependency tool returns basic metadata but empty dependency and dependent lists because its upstream source does not expose that data; the documented replacement is the individual specification lookup.
w3c-mcp setup notes
- w3c-mcp records stdio only; confirm a network transport upstream before planning remote access.
- w3c-mcp has no recorded license; confirm reuse terms in its repository.