mcp -cloudbrowser

This MCP server exposes a Cloudbase Browser integration, allowing Claude to control a headless browser session via the Cloudbrowser tools. After building the server, configure Claude Desktop to connect to the MCP server using the provided Node command and the path to the compiled dist/index.js. Once connected, you’ll see a suite of browser automation tools (navigate, evaluate, get_current_url, screenshot, click, fill, get_text) available under the MCP toolbar. Use these tools to navigate to URLs, run JavaScript in the page context, retrieve the current URL, take screenshots, interact with page elements, and extract content from the page. The server requires an API key for the Browserbase service, supplied via the API_KEY environment variable.

To use the Cloudbrowser MCP tools, ensure your Claude Desktop configuration points to the server with stdio transport, and restart Claude after saving changes. When you click the hammer icon, the available Cloudbrowser tools will be listed for invocation, enabling scripted browser automation inside your chat workflow.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the Cloudbase API (API_KEY)

Installation steps:

1. Install dependencies and build the server

npm install
npm run build

2. Ensure the built server is accessible at the path specified in the MCP config (dist/index.js).
3. Start the server (using the configuration in your MCP setup). For local testing, you can run

npm run inspector

which starts the inspector tooling to help debug and verify the server. 4) Create or update your Claude Desktop MCP configuration using the example below, replacing the API_KEY placeholder with your Cloudbase API key, and ensuring the path to dist/index.js is correct.

{
  "mcpServers": {
    "cloudbrowser": {
      "command": "node",
      "args": ["path/to/mcp-server-cloudbrowser/cloudbrowser/dist/index.js"],
      "env": {
        "API_KEY": "<YOUR_BROWSERBASE_API_KEY>"
      },
      "transportType": "stdio"
    }
  }
}

5. Restart Claude Desktop to apply the new server configuration and verify that the Cloudbrowser tools appear under the MCP interface.

Notes and tips:

• API_KEY is required for Browserbase access; ensure it is kept secret and not committed to source control.
• The server uses a stdio transport; ensure Claude Desktop supports and is configured for stdio integration.
• If you encounter path errors, verify that dist/index.js exists at the exact path specified in the mcpServers configuration.
• The CLI example shows using npx for npm-package-based invocations; the primary server config uses node with a path to the compiled bundle.
• Tools available: cloudbrowser_navigate, cloudbrowser_evaluate, cloudbrowser_get_current_url, cloudbrowser_screenshot (with name, selector, width, height), cloudbrowser_click, cloudbrowser_fill, cloudbrowser_get_text (with optional selector).
• Resources are exposed via screenshot://<name>, enabling access to PNG captures by name.