Autopilot Browser MCP Server
OfficialRelated Servers
Alternatives to Autopilot Browser MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks like navigation, typing, clicking, and taking screenshots.-
- AlicenseAqualityDmaintenanceEnables AI assistants to perform browser automation using Playwright, including navigation, content extraction, screenshot analysis, and custom script execution.54 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search the web, read and extract content from webpages, fetch JSON from REST APIs, and collect links while bypassing anti-bot protections.18 npmISC
- AlicenseAqualityFmaintenanceEnables AI agents to crawl, scrape, search, and automate browsers with anti-bot bypass, providing fast web access via 22 tools.2246 npm3MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks such as navigation, typing, clicking, and taking screenshots.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_workflows is for discovery and information retrieval, while run_workflow is for execution. There is no overlap in functionality, and the descriptions explicitly differentiate them with one being preparatory and the other operational.
Both tools follow a consistent verb_noun naming pattern (search_workflows, run_workflow) with snake_case throughout. The naming is predictable and aligns well with their functions, making them easily distinguishable and readable.
With only 2 tools, the server feels thin for a browser automation domain that typically involves more operations like navigation, clicking, or data extraction. While the tools cover basic workflow execution, the limited count suggests significant gaps in functionality for comprehensive browser control.
The tool set is severely incomplete for a browser automation server. It lacks core operations such as page navigation, element interaction, data scraping, or session management. The existing tools only handle workflow search and execution, leaving most browser automation tasks unsupported and likely causing agent failures.