MDN Web Docs provides AI agents with searchable access to web development documentation, including JavaScript, HTML, CSS, and Web APIs. Retrieve technical references, explore browser compatibility data, find code examples, and look up implementation guidance for frontend and web platform development.
DeepSeek Harness (DSH) is DeepSeek's agent harness. Each MCP server is one plugin entry in your project config.
This guide connects MDN MCP to DeepSeek Harness through MewCP, so DeepSeek Harness can use MDN MCP's 3 tools, like get-compat, get-doc and search.
MDN MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
Manage repositories, pull requests, issues, branches and development workflows on GitHub. Automate software delivery and collaborate across engineering projects.
Connect to external APIs, webhooks and internet services through standard HTTP requests. Build integrations with virtually any platform that exposes a web-based interface.
Give AI coding agents access to a curated library of real-world website designs, screenshots, design systems, and reusable UI components. Search visual references, find similar designs, analyze layouts, extract colors and typography, compare websites, and retrieve copy-ready JSX components for building better interfaces
HotAPI provides a unified API for AI-powered image, video, and audio generation, image editing, and conversational AI. Developers can access multiple models through a single API key, track asynchronous generation tasks, and retrieve results with polling or webhooks.
Other clients
MDN MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact MDN MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
In your DSH project, or the patch file you mount plugins from.
One plugin instance is one MCP server. Add this to your plugin list.
Tools register as mcp__mewcp__<tool_name>. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Retrieve MDN's Browser Compatibility Data.
Retrieve a page of MDN documentation as markdown.
Search MDN for documentation about web technologies.
