mcp

This MCP server lets Claude Desktop and other AI agents run Autopilot Browser workflows. It exposes an MCP-based interface that enables searching for available Autopilot workflows by keyword, listing all workflows, and executing a selected workflow with the required inputs. The server is published as the npm package @autopilotbrowser/mcp-server and is intended to be run via npx in your Claude Desktop configuration. Once installed, you can prompt Claude to find workflows, view them, and trigger automated browser tasks through the Autopilot API key you provide.

Typically, you will configure Claude to reach this MCP server, then issue natural language commands like: “Show me all available Autopilot workflows”, “Search for web scraping workflows”, or “Run the data extraction workflow with URL https://example.com”. The MCP server handles the translation from these commands to workflow invocations, returning real-time results as the workflow progresses.

Prerequisites:

• Node.js installed on the host where Claude Desktop is configured (npx is used via Node).
• Claude Desktop installed and accessible to load MCP server configurations.

Step-by-step:

1. Install or prepare Claude Desktop to reference an MCP server configuration. The following example shows a typical JSON configuration file location for Claude Desktop:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

2. Add the MCP server entry to your Claude Desktop configuration. Create or edit the file to include:

{
  "mcpServers": {
    "autopilot": {
      "command": "npx",
      "args": ["-y", "@autopilotbrowser/mcp-server"],
      "env": {
        "AUTOPILOT_API_KEY": "your_api_key_here"
      }
    }
  }
}

3. Replace the placeholder API key with your actual API key from Autopilot Browser.

4. Save the configuration and restart Claude Desktop if necessary. The MCP server should now be available under the name autopilot in Claude’s MCP integration.

Optional: If you prefer to run the MCP server directly from the command line for testing, you can run:

npx -y @autopilotbrowser/mcp-server

This will start the server (assuming your environment has access to the npm registry).

Tips and common considerations:

• Ensure AUTOPILOT_API_KEY is valid and has the necessary permissions to access your Autopilot Browser workflows.
• The MCP server uses the npm package @autopilotbrowser/mcp-server; keep this package up to date to benefit from new workflows and features.
• If Claude desktop cannot reach the MCP server, verify network connectivity and that the npx command is available in your environment.
• You may customize the server name in the Claude configuration (here it’s autopilot); ensure consistency across tools that reference the MCP server.
• When troubleshooting, check for API key errors, workflow availability, and the specific inputs required by each workflow.
• For best results, provide explicit inputs when executing workflows, since some automation steps depend on URL, selectors, or form data.