Skip to main content
Glama
jiawei686

jev-ultrafast-mcp

by jiawei686

Related Servers

Alternatives to jev-ultrafast-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control a real, persistent Chrome browser over MCP, perceiving pages as accessibility trees and interacting with elements by their accessible names without automation fingerprints or site-specific glue.
      1,410,742 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.
      25
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate an isolated local Chromium browser through MCP, with semantic snapshots, ref-based actions, search, research, crawling, and CDP access.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control Chrome browser actions like navigation, clicking, form filling, screenshots, and console/network logging via an MCP server and Chrome extension.
      532 npm
      MIT

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct responsibilities, but browser_sessions and browser_tabs overlap in listing managed tabs, and browser_tabs also handles opening/closing which overlaps with browser_open and browser_close. The descriptions help disambiguate, so this is only a minor concern.

    Naming Consistency3/5

    All tools share the browser_ prefix and snake_case style, but the second word mixes verbs (open, observe, act, assert, close) with nouns (sessions, macro, goal, tabs, doctor). The naming is readable and predictable enough, though not a consistent verb_noun pattern.

    Tool Count4/5

    Ten tools is a reasonable, well-scoped count for a browser automation server. There is slight redundancy between session/tab management tools, but the overall count is neither bloated nor too thin.

    Completeness5/5

    The tool set covers the full browser automation lifecycle: opening pages, observing, acting, asserting, tab management, macros, autonomous goal completion, cleanup, and diagnostics. No obvious dead ends or missing core operations are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues