Autopilot Browser MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTOPILOT_API_KEY | Yes | Your Autopilot Browser API key. Visit https://autopilotbrowser.com to sign up and generate your API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_workflowsB | Search for available Autopilot Browser workflows by keyword. Returns a list of workflows that match the search term. If no search term is provided, returns all workflows. |
| run_workflowA | Execute a specific Autopilot Browser workflow with the provided inputs. Use search_workflows first to find available workflows and their required inputs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Workflows | List of all available Autopilot Browser workflows that can be executed |
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.