Introducing the MDN MCP server

The MDN Team June 15, 2026 4 minutes read

We're excited to announce the release of the MDN MCP server. MCP (Model Context Protocol) is an open standard that enables AI tools to connect to external data sources. The MDN MCP server uses this protocol to bring MDN's documentation and browser compatibility data directly into your AI agent or IDE.

Why we built the MDN MCP

More and more AI tools are being integrated into web development workflows, but they can surface outdated web platform information based on their training data and knowledge cutoff.

For example, an LLM or coding agent may not know that a feature like @view-transition CSS at-rule exists, or whether it has reached "Widely Available" baseline and is safe to use across browsers.

The MDN MCP gives your coding agent access to accurate, up-to-date web platform information. It also makes it easier for you to access the latest documentation without leaving your preferred tools.

The server is currently experimental. See our privacy notice for details about data handling during this phase.

How to use the MDN MCP

The MDN MCP server works with any MCP-compatible client, including:

• Editors: VS Code, Zed, and Cursor.

• Agent CLIs: Claude Code, Codex CLI, and Antigravity CLI (previously Gemini CLI).

• Chat apps: Claude Desktop.

See the links in this list for how to set up MCP with each tool. For installation instructions and other details, check our MDN MCP server page .

As a quick example, to use it with Claude Code, you would run the following:

bash

claude mcp add --transport http mdn https://mcp.mdn.mozilla.net/

We're looking forward to seeing how you integrate it into your web development workflow, and the scenarios where you find it most useful.

What difference does the MCP make?

Given the non-deterministic nature of LLMs and the variety of available models, it's often challenging to compare their behavior with or without certain skills, prompts, tools, and MCPs enabled.

We tested Claude Code Opus 4.7 with and without the MDN MCP on a few features recently shipped in Firefox 151, asking how to use the features and what the browser support is. Specifically:

1. How to use the light-dark() CSS function for images and which browsers support it?

2. How to use the :buffering CSS pseudo-class and which browsers support it?

3. How to use the shadowrootslotassignment attribute on <template> and which browsers support it?

4. How to use the Web Serial API and which browsers support it?

We noticed certain patterns in the results. In most cases, the usage notes from Claude Code with and without the MDN MCP enabled were comparable. Some answers which used the MCP were better structured and more complete. For example, the notes for the light-dark() CSS function also included examples with linear gradients that weren't directly mentioned in the question but are also supported.

When it came to browser support information, the winner was clear: the MDN MCP produced much better and more reliable results. Claude Code without the MCP got the browser support right only in one case: for the :buffering pseudo-class. For example, Claude Code without the MCP insisted that the declarative shadowrootslotassignment attribute is supported in Chrome 120 and Safari 18.3, possibly conflating it with the Element.attachShadow()'s slotAssignment option. But in fact, Firefox 151 is the first browser to ship support for this attribute.

Without the MCP, Claude Code also didn't provide any concrete browser support information about using images in the light-dark() function: "support is less uniform than the color variant", while with the MCP, it provided the full table listing Firefox 150 and Chrome (behind a flag) as supported browsers.

The worst performance of Claude Code without the MCP came from the Web Serial API question. Firefox 151 shipped support for the Web Serial API in May 2026. However, Claude Code without the MCP correctly mentioned Chromium-based browsers as supporting this feature, but also insisted that in Firefox it's:

Not implemented (and not on the roadmap — see Mozilla's standards position: "harmful")

With the MCP enabled, Claude Code correctly identified that Firefox 151 ships support for the Web Serial API, in line with the release notes.

Additionally, we noticed that in our tests, responses which used the MDN MCP were roughly twice as fast. Without the MCP, Claude Code had to fetch and parse quite a few HTML pages to find current information, which took some time, but even then didn't provide accurate results.

Get involved

Your feedback helps us improve. If you encounter issues, have comments or suggestions, or want to share how you're using the MDN MCP, we'd love to hear from you. Please feel free to come chat with us in the platform channel in our Discord. If you spot any issues, please raise them in the mdn/mcp GitHub repository.

What's next

As AI tools become a bigger part of web development workflows, we're committed to making MDN's documentation available wherever you need it. This release is one step toward that goal, and we're excited to continue improving the experience with your input.