Skip to main content
Glama
Mokecy

mcp-browser-parallel

by Mokecy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-browser-parallel

No user-submitted related servers found.

    Related Servers

    • browser-store

      bysking
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
      5 npm
      MIT

    • chrome-mcp

      wzxklm
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.
      124 npm
      3
      MIT
    • @kuramalab/mysupportdetails-mcp by kuramalab

      @kuramalab/mysupportdetailsofficial

      kuramalab
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for QA and test automation that provides runtime switching between multiple browser profiles (Chromium, Firefox, WebKit) without restart, enabling cross-browser regression testing, multi-account testing, localization QA, and more.
      8 npm
      MIT

    • BrowserMesh

      scrollDynasty
      A
      license
      A
      quality
      A
      maintenance
      A local, open-source MCP server that enables AI clients to control multiple isolated Chromium browser sessions concurrently, with explicit session and page addressing and independent state.
      35
      83 npm
      3
      Apache 2.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3.4/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Even similar actions like click vs mouse_click_xy are differentiated by targeting element vs coordinates. Fill, fill_form, and type are distinct in scope and behavior.

    Naming Consistency5/5

    All tools follow a consistent category_verb pattern in snake_case. Prefixes like browser_, instance_, page_ clearly indicate the scope. Multi-word verbs are used consistently.

    Tool Count3/5

    With 36 tools, the set is larger than typical recommendations (25+). However, the browser automation domain inherently requires many distinct actions. The count is borderline but justified by the comprehensive coverage.

    Completeness5/5

    The tool set covers the full lifecycle of browser interactions: connection, instance management, navigation, all major user actions, state inspection (snapshot, console, network), debugging (tracing), and output (screenshot, PDF). No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources