Skip to main content
Glama
misterboe

Webtools MCP Server

by misterboe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Webtools MCP Server

No user-submitted related servers found.

    Related Servers

    • Chrome DevTools MCP

      az9713
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and inspect a live Chrome browser for automated web debugging, performance analysis, and Lighthouse audits. It allows agents to capture screenshots, monitor network requests, and measure Core Web Vitals using plain-English prompts.
      1,026,016 npm
      Apache 2.0

    • Lighthouse MCP

      mizchi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to perform Google Lighthouse website performance analysis, including Core Web Vitals, accessibility, SEO audits, and actionable optimization recommendations. Provides comprehensive web performance insights through natural language interactions.
      1,300 npm
      4
      MIT

    • rasterly-mcp

      rasterly-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read, screenshot, or convert web pages to PDF using a real headless browser, turning any URL into clean Markdown, a visual image, or a print-ready document.
      82 npm
      MIT

    • Percepta MCP Server

      0x-hewm
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation, AI-powered analysis, visual processing, web scraping, automated test generation, and DevTools analysis capabilities. Supports multiple AI providers (OpenAI, Anthropic, Google, Ollama) for intelligent web interaction and data extraction.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources