Skip to main content
Glama
69gg

Chromate MCP

by 69gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Chromate MCP

No user-submitted related servers found.

    Related Servers

    • Chrome MCP Server

      lxe
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to control Chrome browsers through the Chrome DevTools Protocol, allowing for navigation, clicking, typing, and extracting page information.
      82 npm
      49
      MIT

    • Playwright MCP Server

      b3nw
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform web automation tasks by connecting to remote Playwright/browserless instances, supporting navigation, screenshots, HTML extraction, and element interaction.
      10
      4
      -

    • unified-browser-mcp

      msawayda
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that combines Playwright browser automation with DevTools-style monitoring capabilities, enabling AI assistants to automate browser tasks and capture network/console logs.
      13
      3 npm
      MIT

    • Rod MCP Server

      aliwatters
      A
      license
      Not graded
      quality
      B
      maintenance
      Browser automation for AI agents via the Model Context Protocol, enabling web navigation, form filling, screenshots, and more using Chromium.
      MIT

    • Cloudflare Playwright MCP

      potlee
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Control Protocol server that enables AI assistants to control a browser, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -
    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.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct browser automation action: tab management, page info, screenshots, clicking, scrolling, typing, key presses, and waiting. There is no overlap or ambiguity in their intended purposes.

    Naming Consistency4/5

    Most tools follow a verb-first snake_case pattern (list_tabs, select_tab, screenshot, click, scroll, type_text, press_key, wait), but page_info is a noun phrase and slightly breaks the pattern. Overall the naming is predictable and readable.

    Tool Count5/5

    Nine tools is well within the ideal range for a browser automation server. Each tool covers a necessary action without being redundant or overwhelming.

    Completeness4/5

    The set covers tab selection, page inspection, screenshots, input actions, and waiting—core browser interactions. The most obvious gap is navigation (e.g., goto_url) and richer page content access, but agents can work around these limitations by relying on existing tabs.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources