css-sota-mcp

Model Context Protocol server

Know what CSS you
can actually ship.

Your agent guesses at browser support from whatever it read in training. This server gives it the real answer — live Baseline status from webstatus.dev, and MDN browser-compat-data for every property, selector and at-rule.

No key, no account. Read-only, and capped at 120 requests a minute per address — roughly ten times what an agent working through a task actually uses.

audit_css Ready

Six tools, six questions

Each one answers something a developer actually asks mid-task. The agent picks by question, not by guessing at names.

Connect it

Any MCP client that speaks Streamable HTTP. Pick yours.

--scope user registers it once for every project on the machine. Leave it out and the server is added to the current project only. Then ask: “audit src/styles.css for baseline-widely”.

Where the answers come from

Four sources, split by how fast they change. Nothing is inferred, and nothing is remembered from training.

Fetched per request · cached 1 h

webstatus.dev

Baseline status, the browser versions a feature shipped in, Web Platform Tests scores and usage share. Behind search_css_features, whats_new and get_feature, and never more than an hour behind the dashboard.

Compiled into the Worker

browser-compat-data

The CSS slice of MDN's compat dataset, plus the web-features catalog that maps compat keys to Baseline features. Twenty megabytes upstream, reduced at build time to about 1 MB of JSON — 120 KB over the wire — so check_support and audit_css answer with no network call at all.

Loading version info…

Fetched per request · cached 24 h

mdn/content

Reference prose for get_feature, read from the Markdown source. The canonical slug is resolved through MDN first, because compat data records the URL a page had when the entry was written and MDN reorganises.

Compiled into the Worker

UX guidelines

The one source here that is written rather than fetched: 37 principles behind dont_make_me_think, drawn from Nielsen's heuristics, Hick's and Fitts's laws, WCAG 2.2, neurodiversity research and motion practice — each with the rule, why it holds, and what breaking it looks like in markup.

guidelines v1.0.0 · 37 principles · 9 topics