Skip to main content
Glama

Related Servers

Alternatives to Chrome Course MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      A local MCP server that enables Codex to inspect and interact with Chrome tabs through the Chrome DevTools Protocol, primarily for collecting authorized Brightspace course materials into local folders.
      16
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
      64
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading browser DevTools data (tabs, console errors, network requests, screenshots, DOM, CSS, JS execution) via Chrome DevTools Protocol.
      5,334 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Lets an AI assistant inspect a running Google Chrome or Microsoft Edge browser over the Chrome DevTools Protocol, reading console output, network traffic, DOM snapshots, errors, performance metrics, storage, and screenshots. It also supports live event subscriptions, screen-frame streaming, and one-shot export of everything into an offline-readable archive such as HAR, CSV, and a self-contained HTML report.
      36
      184 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.
      1
      355
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to scrape web pages, fill forms, take screenshots, and extract structured data via Chrome DevTools Protocol with zero external dependencies.
      MIT

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose within its domain (Chrome automation or Coinbase trading). There is no overlap; descriptions clearly differentiate similar actions like 'chrome_click' and 'chrome_select' or 'coinbase_recon' and 'coinbase_attach'.

    Naming Consistency5/5

    All tools follow a consistent prefix_naming convention: 'chrome_verb' for Chrome tools and 'coinbase_verb_noun' for Coinbase tools. The use of snake_case is uniform, and the pattern is predictable across the entire set.

    Tool Count4/5

    22 tools is on the higher side but still reasonable given the combination of two distinct domains (Chrome automation and Coinbase trading). Each tool serves a specific purpose, though some users might find the Coinbase tools excessive for a 'Chrome Course' server.

    Completeness4/5

    The Chrome automation tools cover essential actions (navigation, clicking, typing, JS evaluation, screenshots, tabs), though a few common operations like scrolling are missing. The Coinbase tools provide extensive coverage for trading research (market streaming, portfolio reading, dry-run orders, diagnostics), making the overall surface fairly complete for its intended use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues