Webtools

Provides web analysis tools including HTML extraction, Markdown conversion, screenshots, debugging, and Lighthouse audits.
  • javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

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

You run a Model Context Protocol (MCP) server that provides a suite of web analysis tools. This server lets you extract raw HTML, convert pages to Markdown, take screenshots, run debug sessions, and perform deep web audits and performance analyses. It is designed to be used with an MCP client to automate testing, content extraction, and performance measurement across different devices and network conditions.

How to use

You access the MCP server through a client that supports MCP endpoints. Start by running the MCP server locally using the standard runtime command, then configure your client with the server reference. Use tool presets to conserve tokens or enable the full feature set as needed. You can request actions such as extracting main content, rendering screenshots, or running a Lighthouse audit. When you want focused results, enable only the specific tools you need and target pages with precise selectors or device emulations to align with your goals.

How to install

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

Configuration and usage notes

Configure the MCP server by running it with a selected set of tools. Use environment variables to control which tools are loaded. Example presets include BASIC, WEB, DEBUG, PERFORMANCE, and FULL_ANALYSIS. For production deployments, review the security and proxy settings and enable SSL checks unless you have a specific testing need.

Configuration (examples)

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

Security and best practices

Use proxy and SSL settings only when necessary. Avoid disabling SSL checks on production sites. Run Lighthouse audits with only the needed categories to minimize work and improve reliability. Monitor debug output to detect and address JavaScript errors before applying fixes.

Troubleshooting

If you encounter connection issues, verify the URL or proxy settings and confirm that the MCP server is running. For SSL-related problems in local development, consider enabling ignore-SSL-errors temporarily for testing and revert for production.

Examples of common tasks

Extract main content: Use the content extraction tool to retrieve the primary article content and convert it to clean Markdown. Generate a screenshot to accompany the content if needed. Run a performance audit with Lighthouse to assess performance, accessibility, and other quality signals.

Notes

Device emulation and network condition simulations help you understand how pages behave for real users. Start with a baseline configuration and iteratively refine tool usage for your specific scenarios.

Appendix: Frequently used tool prompts

Comprehensive Website Analysis: analyze-website — performance, accessibility, SEO, and UX insights with device-type adjustments.

End-user workflow highlights

  1. Start the MCP server with a chosen tool preset. 2) Configure your MCP client to point to the local server. 3) Execute tasks such as content extraction, screenshots, or audits. 4) Review results and iterate with device and network presets.

Additional guidance

For best results, begin with basic HTML retrieval, then add rendering, screenshots, and audits as needed. Tailor timeouts and selectors to the complexity of the pages you analyze.

Available tools

webtool_gethtml

Raw HTML extraction with JavaScript rendering support and proxy/retry options.

webtool_readpage

Markdown conversion with clean content extraction, link preservation, and selector support.

webtool_screenshot

Screenshot capture for full pages or specific elements with device emulation.

webtool_debug

Debug console with console output capture, network monitoring, and performance metrics.

webtool_lighthouse

Lighthouse-powered audits covering performance, accessibility, SEO, and best practices.

webtool_performance_trace

Advanced performance analysis including layout, rendering, and memory profiling.

webtool_network_monitor

Network activity analysis with timings and optimization recommendations.

webtool_coverage_analysis

Code coverage analysis for JavaScript and CSS with recommendations.

webtool_web_vitals

Core Web Vitals metrics including LCP, CLS, FID/INP, and TTFB.

webtool_performance_test

Cross-device and network testing with baseline comparisons.

analyze-website

Comprehensive website analysis including device-type considerations and actionable recommendations.

get-website-content

Content extraction and clean markdown conversion for webpages.

screenshot-website

Screenshot capture of webpages with full-page or targeted view.

technical-performance-analysis

Detailed performance analysis with code-level optimization guidance.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational