web-developer

The Web Developer MCP Server exposes a Playwright-powered browser session that AI assistants can drive to inspect and interact with web pages in real time. It provides tools for navigating pages, monitoring network traffic, inspecting DOM elements, extracting HTML, and capturing console output, enabling debugging and UI testing workflows within AI assistants such as Claude Code, Cursor, or other development environments. The server is designed to give your AI agent direct browser access to observe page behavior, interact with elements, and inspect network activity during development.

To use it, connect your MCP client (e.g., Cursor or Claude Code) to the web-developer-mcp endpoint and leverage the available tools. Browser navigation lets you open a URL and begin monitoring; page interactions allow clicking elements, filling inputs, and submitting forms. Console monitoring surfaces logs, warnings, and errors in real time. DOM analysis and HTML extraction enable you to inspect element details and capture raw HTML markup. Network request monitoring provides a view of all requests and the ability to inspect individual requests for headers, payloads, and responses. These capabilities together support debugging, UI testing, and API behavior analysis within your AI workflows.

Prerequisites:

• Bun (for running the MCP server as documented in the repository) or Node.js/npm if the project supports it. The README indicates the server is started with bun start, so Bun is required.
• git to clone the repository.

Installation steps:

1. Clone the repository:

git clone https://github.com/Artmann/web-developer-mcp.git
cd web-developer-mcp

2. Install dependencies using Bun:

bun install

3. Start the MCP server:

bun start

4. Ensure the MCP config includes the server entry you will use (see how_to_use for example configuration).

Prerequisites recap:

• Bun must be installed and available in your PATH.
• The project relies on Bun to install dependencies and launch the server as shown above.

Tips and common issues:

• If bun start fails due to environment configuration, ensure Bun is properly installed and that your environment has network access to fetch dependencies.
• In MCP configuration, use the short server name (e.g., web-developer-mcp) and the appropriate command/args (npx web-developer-mcp) to start the server.
• The Playwright-based browser session is persistent per client connection; reconnecting may reinitialize state.
• If you modify code, rerun bun install to ensure dependencies are up to date, then restart bun start.
• For debugging, verify that the AI agent can reach the MCP endpoint and that the required ports are open in your environment.