Skip to main content
Glama
Mehmoodqureshi

MCP Browser Extension

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Browser Extension

No user-submitted related servers found.

    Related Servers

    • Chrome MCP Bridge

      randyrt
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.
      -

    • cc-chrome

      joshoq
      A
      license
      B
      quality
      C
      maintenance
      Enables browser control through your existing signed-in Chrome profile, letting MCP clients like Claude Code manage tabs, navigate, inspect pages, and perform real user interactions via tool calls. Works with any model backend without needing Playwright or a fresh browser profile.
      21
      MIT

    • Controlium

      am-will
      A
      license
      Not graded
      quality
      D
      maintenance
      Chrome extension + MCP bridge that gives Claude control over your real browser via CDP, enabling navigation, clicking, typing, scrolling, screenshots, and JS execution with a visible cursor and tab-bring-to-front.
      1
      MIT

    • chrome-control-mcp

      masterdeepak15
      A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients such as Claude to drive the user's real Chrome in the background via the DevTools Protocol through a companion extension, exposing 32 tools for navigation, form input, screenshots, snapshots, script evaluation, network and console inspection, performance tracing and raw CDP commands, with control off by default and limited by allowed sites and blocked domains.
      32
      79 npm
      1
      MIT

    • browser-mcp

      747486675
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to control a real, visible Chrome via MCP for navigating, clicking, typing, downloading files, and reading page content. Supports isolated CDP and everyday-Chrome extension modes with user confirmations for risky actions.
      19 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.2/5.0

    Scored across 21 tools

    Disambiguation4/5

    Each tool has a distinct purpose, but there are clusters that could confuse: proxy_status/chrome_status/task_status all report status, and get_text/get_html/read_as_markdown/snapshot all extract page content. Descriptions do a good job of clarifying the boundaries, so misselection is unlikely but possible.

    Naming Consistency3/5

    The set mixes several conventions: verb_noun (extract_links, read_as_markdown, get_text), noun_status (chrome_status, task_status), noun_verb (profile_use, task_new, tabs_list), and bare single words (batch, snapshot, storage). Readable but not predictable.

    Tool Count4/5

    21 tools is on the heavier side but each appears to earn its place across status, profile/task management, extraction, and capture concerns. Reasonable for a full-featured browser automation surface, though slightly bloated.

    Completeness3/5

    Profile/task lifecycle, content extraction, and capture are well covered, but core interaction tools are absent: there is no navigate, click, type/fill, or scroll, even though snapshot/auth_check explicitly reference targeting by `ref` and acting 'after a navigate'. This is a notable gap for a browser automation server.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources