omni-web-mcp
Related Servers
Alternatives to omni-web-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceAn open-source MCP server that provides browser automation capabilities to external AI systems, enabling navigation, DOM interaction, and web content extraction.19Apache 2.0- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents mouse-and-keyboard control over a live Chrome session, enabling navigation, clicking, typing, screenshots, and DOM inspection.20 npm-
- FlicenseBqualityDmaintenanceAn MCP server that enables AI coding tools to control a browser for automated actions, UI extraction, network interception, and screenshots.231-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents human-like control over Windows via visual perception and simulated mouse and keyboard input, enabling automation of any application without APIs.38 npm4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP Server that enables AI assistants to interact with your local browsers.4,189 npm55MIT
- AlicenseAqualityDmaintenanceA MCP server that gives AI assistants full browser control, enabling navigation, clicking, form filling, and screenshots via any MCP client.8MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: listing available pages, extracting DOM structure, clicking, entering text, and scrolling. Their descriptions explicitly explain how they compose, such as using clientId from list_pages and numeric ids from get_dom_tree.
All tool names follow a consistent snake_case verb_noun pattern: list_pages, get_dom_tree, click_element, input_text, scroll_page. The convention is predictable and readable.
Five tools is well-scoped for a focused browser-interaction server. Each tool earns its place in the inspect-and-act workflow without obvious redundancy.
The core loop of listing pages, inspecting the DOM, clicking, typing, and scrolling is covered. However, there is no tool to open or navigate directly to a URL, close a page, take a screenshot, or wait for async state, which are notable gaps for general web automation.