browser-mcp
Related Servers
Alternatives to browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Chrome browser actions like navigation, clicking, form filling, screenshots, and console/network logging via an MCP server and Chrome extension.MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets AI clients drive the user's own Chrome browser through an extension, enabling navigation, clicking, typing, file uploads, tab management, scrolling, and JavaScript evaluation while staying logged in with a real browser profile.251Apache 2.0
- 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 gradedqualityAmaintenanceA local MCP server that lets AI coding assistants drive the Chrome browser you already have open, using your existing logged-in sessions. It enables navigating and reading pages, clicking, typing, filling forms, taking screenshots, uploading files, and inspecting console, network, storage, and cookies — without headless browsers or opening a remote-debugging port.1 npmISC
- AlicenseBqualityDmaintenanceAn MCP server that provides AI models with full browser automation capabilities through Chrome. It enables navigation, interaction, screenshots, and complete DevTools access by bridging AI clients with a companion Chrome extension.993 npm3Apache 2.0
- 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 13 tools
Each tool maps to a distinct action on the page: navigate/back/forward for history, snapshot vs screenshot for structure vs image, and click/type/select_option/press_key/hover for separate input modalities. The only superficially close pair, browser_snapshot and browser_screenshot, is clearly differentiated by their descriptions.
All 13 tools share a uniform browser_ prefix and snake_case style, making the set highly predictable. Minor deviation: several names are bare nouns or adverbs (browser_snapshot, browser_back, browser_close) rather than verb_noun, but this stays readable and consistent within the domain.
13 tools is right in the sweet spot for a browser automation surface, and every tool covers a genuinely needed operation (navigation, interaction, inspection, lifecycle). No redundant or filler tools are present.
Core browser workflows are fully covered: navigate, inspect, interact, capture, read console, and close. Minor gaps remain around explicit scrolling, tab/window management, file upload, and iframe or JS evaluation, though most can be worked around with press_key and repeated snapshots.