Browser Jet Pilot
Related Servers
Alternatives to Browser Jet Pilot
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI assistants drive real Chromium browsers — navigate, click, type, read pages, run OCR, and record network traffic. 43 tools, credentials stay local, zero telemetry.-
- 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
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
- AlicenseAqualityBmaintenanceMCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic from any AI client that supports the Model Context Protocol.211MIT

kitewrightofficial
AlicenseNot gradedqualityBmaintenanceA lightweight MCP server for browser automation that gives AI agents navigate, screenshot, and extract tools via a single small binary, without needing Node.js or Playwright. It provides CDP-based browser control with efficient startup and resource usage.23MIT- AlicenseNot gradedqualityAmaintenancesingle-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.12MIT
TDQS
Scored across 19 tools
Each tool targets a distinct action or purpose: clicking, filling, typing, evaluating scripts, managing tabs, etc. The only potential overlap is between 'browser_fill' and 'browser_type', but their descriptions clearly differentiate them (bulk fill vs. character-by-character typing with events). No confusion between tools.
All tools follow a consistent 'browser_verb' or 'browser_verb_noun' pattern in snake_case (e.g., browser_click, browser_list_tabs, browser_disable_shaders). No mixing of conventions or verb styles.
With 19 tools, the server covers a wide range of browser automation tasks without being bloated. Each tool serves a clear purpose, from basic navigation and interaction to advanced features like shader control. The count feels appropriate for a comprehensive browser automation MCP server.
The tool set covers core browser operations: navigation, clicks, typing, filling, scrolling, select, tab management, screenshots, JavaScript execution, and waiting. Minor gaps exist such as file upload, cookie management, or form submission utilities, but these can often be worked around via JavaScript or clicking. Overall, it's robust for typical use cases.