Skip to main content
Glama

Related Servers

Alternatives to Chrome Course MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query course catalogs, assignments, exams, activities, and learning progress through a local Chrome CDP session, refresh and inspect saved snapshots, and open task entries while leaving login, verification, and submission actions manual.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Lets AI assistants browse a Brightspace-based course platform read-only: list courses, search modules for lecture slides, extract text from PDF/PowerPoint/Word files, and check upcoming deadlines, assignments, and announcements. Runs locally on the user's own machine with their own browser sign-in.
      10
      1
      MIT
    • A
      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
      MIT
    • A
      license
      B
      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.
      81
      1
      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,213 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Runs locally and lets AI clients read course deadlines, courses, announcements, activities, and files through a user-authenticated browser session, with assignment submission optional.
      6
      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 recent community issues