webtools

Webtools MCP Server exposes a suite of browser automation and analysis tools designed for extracting content, converting formats, taking screenshots, debugging, and running Lighthouse-based audits. With the included MCP tools you can fetch raw HTML, convert pages to markdown, generate screenshots (including full-page and device emulation), inspect console and network activity in a debug console, and perform comprehensive web audits and performance analyses. You can selectively enable tool presets to control token usage and runtime load, such as BASIC for content extraction, WEB for content plus visuals, or PERFORMANCE for in-depth performance analysis. Use the server by launching it via npx as shown in the installation guide, then query tools through the MCP interface or Claude integration commands as demonstrated in the presets and examples.

Prerequisites:

• Node.js 14 or higher
• Basic internet access to install npm packages

Installation steps:

1. Install the MCP server globally or run via npx:

npm install -g @bschauer/webtools-mcp-server

2. Run the MCP server (using the quick start configuration shown in the example):

# Using npx with default basic tools
npx -y @bschauer/webtools-mcp-server@latest

3. Optional: Create an explicit mcp configuration file (example shown):

{
  "mcpServers": {
    "webtools": {
      "command": "npx",
      "args": ["-y", "@bschauer/webtools-mcp-server@latest"],
      "env": {
        "ENABLED_TOOLS": "BASIC"
      }
    }
  }
}

4. If you prefer running with a different tool set, adjust ENABLED_TOOLS or use the CLI options described in the README.

Tips and notes:

• Prerequisites mention Node.js 14+ and Puppeteer-provided Chrome; the server bundles Chromium, so no separate Chrome install is needed.
• ENABLED_TOOLS controls which tools are loaded; using BASIC reduces token usage significantly, while PERFORMANCE enables advanced timing and analysis tools.
• When using Claude integration or other MCP clients, you can reference the presets (ALL, BASIC, WEB, DEBUG, PERFORMANCE, FULL_ANALYSIS) to tailor tool availability and token consumption.
• Common issues may include network restrictions affecting Puppeteer/Chromium startup or environment variable parsing; ensure your environment allows network access for page fetches and audits.
• The npm package name is @bschauer/webtools-mcp-server; using the latest tag ensures you have the most recent toolset.