Browser Use

ConnectionMCP

Run managed browser automation tasks through Browser Use's MCP server.

Install

Connections live under agent/connections/. Install the framework:

Quick start

Create agent/connections/browser-use.ts. The connection name is derived from the filename:

// agent/connections/browser-use.tsimport { defineMcpClientConnection } from "eve/connections";
export default defineMcpClientConnection({  url: "https://api.browser-use.com/v3/mcp",  description: "Browser Use: run browser automation tasks, inspect sessions, and manage browser profiles.",  headers: () => ({    "x-browser-use-api-key": process.env.BROWSER_USE_API_KEY!,  }),});

// agent/connections/browser-use.tsimport { defineMcpClientConnection } from "eve/connections";
export default defineMcpClientConnection({  url: "https://api.browser-use.com/v3/mcp",  description: "Browser Use: run browser automation tasks, inspect sessions, and manage browser profiles.",  headers: () => ({    "x-browser-use-api-key": process.env.BROWSER_USE_API_KEY!,  }),});

Keep the API key in a server-side environment variable. eve sends it directly to the MCP server and does not expose it to the model.

Configure

Set BROWSER_USE_API_KEY as a server-side environment variable:

Browser Use runs tasks in managed cloud browsers. Add approval gates or tool filters before allowing unattended browser actions.

See the Connections docs for principal types, headers, approval, and protocol-specific filters.