mdn-lookup

mdnlookup is an MCP tool server that fetches and summarizes MDN Web Docs content. It exposes a simple MCP-compatible tool named mdnlookup over stdio, allowing editors and other MCP clients to search MDN and receive concise summaries along with a link to the full documentation. You can query the tool by sending a request with the tool name and a query parameter, for example a web API name or JavaScript method, and the server returns a short summary suitable for quick references inside your development workflow. The server is designed to work well with editor integrations (like VS Code) and MCP clients that rely on stdio-based communication.

To use it, configure an MCP client (or VS Code extension) to invoke the mdnlookup tool by its name and pass a query string under the params. The response includes a content array with a brief textual summary and a link to the full MDN page, enabling rapid context switching without leaving your code editor. You can also run the Node-based server directly via node index.js and connect from an MCP client configured to communicate over stdio.

Prerequisites:\n- Node.js (LTS) installed on your machine.\n- Access to the repository you want to run (clone or download the source).\n\n1) Clone the repository and install dependencies:\nbash\ngit clone https://github.com/yourusername/mdn-lookup.git\ncd mdn-lookup\nnpm install\n\n\n2) Run the server locally (Node.js):\nbash\nnode index.js\n\nThis starts the MCP server over stdio and it will listen for MCP requests from compatible clients.\n\n3) Optional: configure MCP client examples (as shown in the README) to point to the local Node server or to a Docker container if you prefer containerized execution.\n\nNotes:\n- Ensure network access to MDN is available from the host running the server.\n- If you modify the code, reinstall dependencies with npm install.\n

Tips and notes: \n- The server fetches documentation from MDN in English. If you need a different language, verify if the upstream MDN API supports it and adjust client requests accordingly.\n- When using Docker, you can run the container with -i to keep stdio interactive and feed MCP requests from your editor.\n- If you encounter timeouts, check your network connectivity to MDN or consider increasing any client-side timeouts in your MCP client.\n- The npm package name (if publishing) appears to be mdnlookup based on the repository configuration and sample usage in the docs. If you deploy, set the npm_package field accordingly.\n