Hyperbrowser MCP Server

### 1. Basic Configuration This is a minimal setup to run the **Hyperbrowser MCP Server** as a simple automation helper, using the default command and no extra options. ```json { "Hyperbrowser MCP Server": { "command": "hyperbrowser-mcp", "args": [], "env": {}, "disabled": false } } ``` **Explanation (not part of JSON):** - `"Hyperbrowser MCP Server"`: The name as it will appear inside Claude Code under `mcpServers`. - `"command": "hyperbrowser-mcp"`: Assumes the Hyperbrowser MCP Server is installed globally and available on your PATH as `hyperbrowser-mcp`. - `"args": []`: No additional CLI arguments; the server will run with its internal defaults. - `"env": {}`: No special environment variables. - `"disabled": false`: Ensures Claude Code will try to start this MCP server. --- ### 2. Advanced Configuration A more complete configuration with logging, a custom config file, and environment variables for API keys and timeouts. ```json { "Hyperbrowser MCP Server": { "command": "hyperbrowser-mcp", "args": [ "--config", "/Users/youruser/.config/hyperbrowser-mcp/config.json", "--log-level", "debug", "--max-concurrent-tasks", "5" ], "env": { "HYPERBROWSER_API_KEY": "YOUR_HYPERBROWSER_API_KEY_HERE", "HYPERBROWSER_ENV": "development", "HYPERBROWSER_DEFAULT_TIMEOUT_MS": "15000", "HYPERBROWSER_LOG_FILE": "/Users/youruser/.config/hyperbrowser-mcp/hyperbrowser.log" }, "disabled": false } } ``` **Explanation (not part of JSON):** - `"command": "hyperbrowser-mcp"`: Runs the Hyperbrowser MCP Server binary. - `"args"`: - `"--config" "/Users/youruser/.config/hyperbrowser-mcp/config.json"`: Points the server to a specific configuration file managed outside Claude. - `"--log-level" "debug"`: Increases verbosity for troubleshooting and development. - `"--max-concurrent-tasks" "5"`: Limits how many automation tasks Hyperbrowser can run in parallel to avoid overloading your system. - `"env"`: - `"HYPERBROWSER_API_KEY"`: API key or token for the Hyperbrowser backend or associated automation service. - `"HYPERBROWSER_ENV": "development"`: Puts the server in a non-production mode (e.g., more logs, relaxed limits). - `"HYPERBROWSER_DEFAULT_TIMEOUT_MS": "15000"`: Default timeout (in milliseconds) for automation steps (15 seconds). - `"HYPERBROWSER_LOG_FILE"`: Where the server writes detailed logs. - `"disabled": false`: Keeps the server active. --- ### 3. Use Case Specific Configuration – CI/CD & Browser Automation in a Project Workspace This configuration is tailored for a **project-specific, production-like automation setup**, where Hyperbrowser is used to drive browser-based tests and automation tasks for a particular codebase (e.g., end‑to‑end tests, UI checks, or scripted browser workflows). ```json { "Hyperbrowser MCP Server": { "command": "/usr/local/bin/hyperbrowser-mcp", "args": [ "--config", "/var/hyperbrowser/project-config.json", "--log-level", "info", "--headless", "--workspace-root", "/Users/youruser/Projects/my-web-app", "--allow-origins", "https://my-web-app.local,https://staging.my-web-app.com", "--max-concurrent-tasks", "10" ], "env": { "HYPERBROWSER_API_KEY": "PROD_OR_STAGING_API_KEY", "HYPERBROWSER_ENV": "staging", "HYPERBROWSER_DEFAULT_TIMEOUT_MS": "30000", "HYPERBROWSER_SCREENSHOT_DIR": "/var/hyperbrowser/artifacts/screenshots", "HYPERBROWSER_VIDEO_DIR": "/var/hyperbrowser/artifacts/videos", "HYPERBROWSER_STRICT_MODE": "true", "HYPERBROWSER_CI_MODE": "true" }, "disabled": false } } ``` **Explanation (not part of JSON):** - `"command": "/usr/local/bin/hyperbrowser-mcp"`: Uses an absolute path, typical for CI or a production-like environment where the binary is installed system-wide. - `"args"`: - `"--config" "/var/hyperbrowser/project-config.json"`: Project-specific Hyperbrowser config with automation flows, test suites, or integration settings. - `"--log-level" "info"`: Balanced logging level suitable for CI/staging. - `"--headless"`: Runs browser automation without a visible window (necessary in CI servers and often preferred locally). - `"--workspace-root" "/Users/youruser/Projects/my-web-app"`: Ties automation to a specific project directory so Hyperbrowser can read local files, run project scripts, etc. - `"--allow-origins" "https://my-web-app.local,https://staging.my-web-app.com"`: Restricts browser automation to specific domains, reducing risk of accidental operations elsewhere. - `"--max-concurrent-tasks" "10"`: Allows more parallel browser tasks to speed up test suites or automation runs. - `"env"`: - `"HYPERBROWSER_API_KEY"`: Key for a staging or production Hyperbrowser backend. - `"HYPERBROWSER_ENV": "staging"`: Marks this as a staging/CI environment. - `"HYPERBROWSER_DEFAULT_TIMEOUT_MS": "30000"`: Longer default timeout (30s) to accommodate slower staging environments. - `"HYPERBROWSER_SCREENSHOT_DIR"` / `"HYPERBROWSER_VIDEO_DIR"`: Directories where artifacts from browser runs are stored for later inspection (CI logs, debugging). - `"HYPERBROWSER_STRICT_MODE": "true"`: Fails fast on unexpected states or flaky steps. - `"HYPERBROWSER_CI_MODE": "true"`: Enables CI-friendly behavior (non-interactive, stable exit codes, structured logs). - `"disabled": false`: Ensures Claude Code can use this server for project automation and browser-based tasks.