jev-ultrafast-mcp
Related Servers
Alternatives to jev-ultrafast-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to drive a Chromium browser through MCP, with persistent sessions, compact page snapshots, guarded actions, batched operations, and explicit result verification.16MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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,619,036 npm1MIT
- AlicenseAqualityAmaintenanceMCP 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.251Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.14 npm1MIT
- FlicenseNot gradedqualityBmaintenanceMCP 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.-
- AlicenseNot gradedqualityAmaintenanceEnables 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
TDQS
Scored across 10 tools
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.
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.
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.
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.