Skip to main content
Glama
sailaoda

Concurrent Browser MCP

by sailaoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Concurrent Browser MCP

No user-submitted related servers found.

    Related Servers

    • parallel-browser-mcp

      etairl
      A
      license
      C
      quality
      B
      maintenance
      parallel-browser-mcp is an MCP server for parallel browser automation. It exposes a numeric session model over MCP so one client can create and control multiple browser sessions at the same time across multiple browser providers.
      26
      170 npm
      42
      Apache 2.0

    • mcp-browser-parallel

      Mokecy
      A
      license
      B
      quality
      D
      maintenance
      Multi-instance parallel browser MCP server that manages multiple isolated browser instances in a single Chrome process with automatic login state cloning, allowing parallel independent operations across instances.
      36
      MIT

    • Better Browser MCP

      nbiish
      A
      license
      A
      quality
      B
      maintenance
      Multi-agent local browser automation MCP server with per-agent WebSocket paths, configurable ports, and fixes for upstream issues like port collisions and recursion bugs.
      23
      1
      Apache 2.0

    • playwright-mcp-server

      doucej
      A
      license
      A
      quality
      F
      maintenance
      Stateful MCP server wrapping Playwright for browser automation. Provides tools to navigate, interact, and extract data from web pages via a persistent browser session.
      19
      928 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific browser interaction (e.g., navigation, element interaction, instance management, content retrieval), and the descriptions clearly differentiate their functions. There is no overlap that would cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent 'browser_' prefix with snake_case and descriptive verb_noun patterns (e.g., browser_click, browser_navigate, browser_get_markdown). This predictability makes it easy for agents to understand and use the tools without confusion.

    Tool Count4/5

    With 20 tools, the count is slightly high but reasonable for a comprehensive browser automation server. It covers a wide range of operations from basic navigation to advanced interactions, though it might feel heavy compared to simpler servers. Each tool appears to earn its place in the domain.

    Completeness5/5

    The tool set provides complete coverage for browser automation, including instance management, navigation, element interaction, content retrieval, and waiting mechanisms. There are no obvious gaps; agents can perform full workflows from setup to teardown without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources