Skip to main content
Glama

Related Servers

Alternatives to ie-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      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
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to launch or attach to a Microsoft Edge session and drive it through a four-tiered tool set spanning navigation, clicking, typing, and token-efficient accessibility-tree inspection. Also exposes raw Chrome DevTools Protocol calls for network interception, cookie manipulation, console and performance telemetry, and device emulation.
      20
      2
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control legacy web applications running in Microsoft Edge's IE Mode via MCP, using Selenium WebDriver and IEDriverServer for browser automation.
      10
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to automate Microsoft Edge in IE mode through Selenium and IEDriver, letting them inspect legacy pages, fill forms, click controls, handle frames, alerts, windows, and file uploads.
      32
      MIT

    TDQS

    B3.4/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource or action, and the long descriptions carefully separate the near-neighbours (driver windows via ie_switch_window/ie_windows vs. the user's tabs via ie_tabs/ie_attach, ie_close vs. ie_close_window vs. ie_detach vs. ie_kill_orphans). The wait family (ie_wait_ready/ie_wait_text/ie_wait_element/ie_sleep) and the two clear tools overlap slightly, but each has an explicit 'when to use me instead' note, so an agent can still choose correctly.

    Naming Consistency4/5

    Nearly all 39 names are ie_-prefixed snake_case with a verb_noun shape (ie_open, ie_goto, ie_click, ie_wait_text, ie_close_window). The only deviations are the two noun_verb exceptions ie_console_clear and ie_network_clear, plus a few bare-verb names (ie_back, ie_forward, ie_close) where the resource is implicit. Overall predictable and readable.

    Tool Count3/5

    39 tools is heavy for one server, though the domain is genuinely broad (navigation, DOM reading, input, dialogs, network capture, window/tab lifecycle, process cleanup). A few entries feel marginal or bookkeeping-only (ie_sleep, ie_console_clear, ie_network_clear, ie_resize) and could be folded into other tools or arguments. It is over-scoped rather than unjustified.

    Completeness4/5

    The surface covers the full automation lifecycle: session open/close, navigation and history, page/frame reads, grid extraction, clicking/filling/selecting/keys/hover/scroll/upload, script dialogs, screenshots, console and network evidence, plus attach/detach and orphan cleanup. Remaining gaps are minor and workaroundable via ie_js: no multi-element query tool (returning all matches for a selector), no cookie/session or download handling, and no dialog handling for prompts inside modal dialogs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues