Webtools MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | No | Proxy server URL. | |
| USE_PROXY | No | Enable proxy support (true/false). | false |
| ENABLED_TOOLS | No | Enable only specific tools or presets. Defaults to ALL. Options: ALL, BASIC, WEB, DEBUG, PERFORMANCE, FULL_ANALYSIS, or comma-separated tool names. | ALL |
| PROXY_TIMEOUT | No | Proxy timeout in milliseconds. | 10000 |
| IGNORE_SSL_ERRORS | No | Ignore SSL certificate errors (true/false). | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| webtool_gethtmlB | Get the HTML content of a webpage. Automatically handles retries and proxy if needed. |
| webtool_readpageA | Get the webpage content in Markdown format, including links and images. Handles blocked access automatically. |
| webtool_screenshotB | Take a screenshot of a webpage or specific element on the page with custom device emulation |
| webtool_debugB | Debug a webpage by capturing console output, network requests, errors, and layout thrashing with custom device emulation. Includes advanced response size management with pagination, output limits, and compact formatting to stay within MCP token limits. |
| webtool_lighthouseA | Run a Lighthouse audit on a webpage to generate a comprehensive performance report with detailed resource analysis. The report includes specific file paths, resource sizes, and performance metrics similar to Chrome DevTools. Identifies exact files causing performance issues without offering improvement suggestions. |
| webtool_performance_traceA | Perform a detailed performance analysis with specialized modules for layout thrashing, CSS variables impact, JavaScript execution timeline, long tasks breakdown, memory and DOM growth analysis, and resource loading optimization. Provides actionable recommendations for performance improvements. |
| webtool_coverage_analysisB | Analyze JavaScript and CSS coverage to identify unused code and optimization opportunities. Uses Chrome DevTools Protocol Coverage API to provide detailed insights into code usage. |
| webtool_web_vitalsB | Analyze Core Web Vitals metrics (LCP, CLS, FID/INP, TTFB) and identify problematic elements affecting these metrics. Uses Performance Observer API to provide detailed insights into real user experience metrics. |
| webtool_network_monitorC | Analyze network activity and resource loading performance. Provides detailed insights into network requests, timing, and optimization opportunities. |
| webtool_performance_testB | Run performance tests across different devices and network conditions. Compare results and identify device-specific or network-specific issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-website | Umfassende Analyse einer Website mit Fokus auf Performance, SEO, Accessibility und User Experience für Desktop oder Mobile |
| get-website-content | Extrahiert den Hauptinhalt einer Website und konvertiert ihn in ein gut lesbares Markdown-Format. |
| screenshot-website | Erstellt einen Screenshot einer Website für visuelle Analyse und Dokumentation. |
| technical-performance-analysis | Detaillierte technische Analyse von Performance-Schwachstellen mit Code-Beispielen und Optimierungsvorschlägen |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose, covering different aspects of web analysis: coverage, debugging, HTML retrieval, Lighthouse audit, network, performance testing, performance tracing, reading as markdown, screenshots, and web vitals. Minimal overlap with sufficient differentiation.
All tools use the 'webtool_' prefix followed by a descriptive name (e.g., coverage_analysis, debug, lighthouse). The naming pattern is predictable and consistent, making it easy for agents to infer tool functions.
With 10 tools, the server is well-scoped for its domain of web development analysis. Each tool serves a specific need without redundancy, and the count is neither too small nor excessive.
The tool set covers a comprehensive range of web debugging and performance analysis tasks, including HTML extraction, screenshots, network monitoring, multiple performance metrics, and tracing. It provides a full lifecycle for analyzing web pages.