Skip to main content
Glama
docentovich

chrometools-mcp

by docentovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to chrometools-mcp

No user-submitted related servers found.

    Related Servers

    • Browser MCP

      IlGabbia998
      A
      license
      B
      quality
      B
      maintenance
      Automates browser actions through AI with 39 tools including navigation, tab management, JavaScript execution, and cookie access, using a Chrome extension for local automation.
      39
      7,578 npm
      1
      Apache 2.0

    • agent-browser-mcp-server

      hughedward
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides complete browser automation capabilities for AI agents via 44 tools, including navigation, element interaction, state management, and session recording.
      583 npm
      1
      Apache 2.0

    • Browser MCP

      pomoq-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Automate your real Chrome browser locally with AI, supporting vision, human-like input, code execution, macros, and watchdogs.
      18 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.
      -

    • agent-browser-mcp

      335234131
      A
      license
      B
      quality
      F
      maintenance
      Enables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.
      20
      243
      MIT
    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

    B3.4/5.0

    Scored across 59 tools

    Disambiguation3/5

    Several tools have overlapping purposes, such as executeModelAction vs click/type/selectOption, and analyzePage vs smartFindElement vs getElementDetails. However, detailed descriptions help distinguish many of them, though the volume creates ambiguity.

    Naming Consistency4/5

    All tools use camelCase with a mostly verb-first pattern (get, list, search, click, type, etc.). A few names like smartFindElement and executeModelAction break the pattern slightly, but overall naming is consistent.

    Tool Count2/5

    With 59 tools, the server is excessively large. While it covers multiple domains (browser automation, Figma, scenarios, API models), many tools could be consolidated, making the surface overwhelming.

    Completeness4/5

    The server covers browser automation, iframe handling, network, console, Figma design, scenario recording, and API model generation comprehensively. Minor gaps exist (e.g., cookie management, file upload), but the core workflows are well covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources