Skip to main content
Glama
sumikof

ie-mode-mcp

by sumikof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ie-mode-mcp

No user-submitted related servers found.

    Related Servers

    • ie-mcp

      thomfilg
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to drive Edge in IE mode for automating legacy IE-only web applications, supporting tasks like clicking, filling forms, and data extraction via Selenium.
      28
      MIT

    • Selenium MCP Server

      AbyvargheseMandapathel
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to automate web browsers via Selenium WebDriver, supporting Chrome, Firefox, and Edge in headless or visible mode with tools for navigation, interaction, content extraction, screenshots, and scripting.
      21
      39 npm
      MIT

    • browser-bridge

      jeffkit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote agents to control a local Chrome/Edge browser via MCP, supporting navigation, snapshots, clicks, typing, screenshots, and script execution.
      152 npm
      ISC

    • Selenium MCP Server

      nayakprashant
      A
      license
      A
      quality
      C
      maintenance
      Exposes Selenium WebDriver as an MCP server, enabling AI agents and LLMs to control real browsers for automation tasks like navigation, element interaction, and screenshot capture.
      22
      3
      MIT

    • selagent

      akshay-rajan
      A
      license
      Not graded
      quality
      D
      maintenance
      A Selenium-based MCP server that exposes browser automation tools for navigation, interaction, form filling, and assertions, enabling AI agents to control web browsers through natural language.
      GPL 3.0
    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

    A3.8/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: session management (start/close), navigation, inspection, interaction (click, type, select), window switching, waiting, and screenshot. No two tools overlap in functionality.

    Naming Consistency3/5

    The naming pattern is inconsistent: some tools use a 'browser_' prefix (browser_start, browser_close), while others are bare verbs (navigate, click, type) or compound snake_case (inspect_page, switch_window, wait_for). This mix of styles could cause confusion.

    Tool Count5/5

    With 10 tools, the set is well-scoped for browser automation. It covers session lifetime, navigation, element interaction, inspection, window handling, and waiting without being bloated or too thin.

    Completeness3/5

    The tools cover fundamental browser actions but miss common features like back/forward navigation, JavaScript execution, alert handling, or cookie management. The set is functional for basic scenarios but has notable gaps for comprehensive automation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources