Skip to main content
Glama
CrispyW0nton

Chrome Course MCP

by CrispyW0nton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Chrome Course MCP

No user-submitted related servers found.

    Related Servers

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      3
      2
      MIT

    • edge_browser

      rakaar
      F
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for Codex that provides on-demand, read-only access to Edge tabs and bookmarks, plus controlled interaction with agent-owned tabs. Requires manual activation via the browser extension and enforces a fail-closed security model.
      -

    • Chrome Tools MCP Server

      nicholmikey
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
      68
      53
      MIT

    • MCP Browser Logger

      tao-Lionel
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct actions (open, navigate, click, type, screenshot, etc.), and the two Brightspace tools are clearly separate. Slight overlap exists between chrome_open_tab and chrome_launch, and between chrome_snapshot and chrome_extract_media, but descriptions resolve ambiguity.

    Naming Consistency5/5

    All tools follow a consistent pattern: domain_verb_noun (chrome_*, brightspace_*). Every name uses lowercase with underscores and a clear action verb, making the naming predictable and easy to learn.

    Tool Count4/5

    With 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for Chrome automation plus Brightspace-specific archiving. Each tool has a specific role, and the count feels justified rather than bloated.

    Completeness4/5

    The Chrome automation covers a full interaction lifecycle: tab management, navigation, reading, clicking, typing, selecting, pressing, evaluating, saving, downloading, and media extraction. Brightspace coverage is limited to collecting/archiving pages, which fits the apparent purpose but lacks other potential course-management operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources