add browser-use mcp server

[ShawnPana]

Description

This PR adds the Browser Use MCP server to the community registry, enabling users to perform browser automation tasks directly through Chatbox.

Main Changes:

• Added a new MCP registry entry for "browser-use" in src/renderer/components/settings/mcp/registries.ts
• Configured the server to connect via npx mcp-remote to the Browser Use API endpoint

Features provided by Browser Use MCP:

• Browser automation with real-time web access and search capabilities
• Tools for executing browser tasks programmatically
• Persistent authentication profile management for maintaining logged-in sessions
• Task progress monitoring for long-running automation workflows

Configuration:

• Command: npx mcp-remote https://api.browser-use.com/mcp
• Authentication: Requires API key via X-Browser-Use-API-Key header
• Homepage: https://github.com/browser-use/browser-use

Users can now select "Browser Use" from the MCP server settings in Chatbox, add their API key, and enable AI agents to perform browser-based operations such as web scraping, form filling, automated testing, or general web navigation tasks.

Additional Notes

• This is a registry-only addition with no code logic changes
• Users will need to obtain an API key from browser-use.com to use this MCP server
• The server runs remotely via the Browser Use API, so no local installation is required beyond the mcp-remote package

Screenshots

N/A - This is a backend registry addition. The Browser Use option will appear in the MCP server selection dropdown in Settings.

Contributor Agreement

By submitting this Pull Request, I confirm that I have read and agree to the following terms:

• I agree to contribute all code submitted in this PR to the open-source community edition licensed under GPLv3 and the proprietary official edition without compensation.
• I grant the official edition development team the rights to freely use, modify, and distribute this code, including for commercial purposes.
• I confirm that this code is my original work, or I have obtained the appropriate authorization from the copyright holder to submit this code under these terms.
• I understand that the submitted code will be publicly released under the GPLv3 license, and may also be used in the proprietary official edition.

Please check the box below to confirm:

[X] I have read and agree with the above statement.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR adds the Browser Use MCP server to the community registry, enabling browser automation capabilities through the Model Context Protocol. The server connects to Browser Use's remote API endpoint using the mcp-remote package.

Key Changes:

• Added a new "browser-use" entry to the community MCP registry
• Configured remote connection via npx mcp-remote to Browser Use API endpoint
• Included header-based API key authentication in command arguments

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The npx command should include the -y flag for consistency with other registry entries using mcp-remote. The Sentry entry (line 240) shows the pattern: args: ['-y', 'mcp-remote', 'https://mcp.sentry.dev/sse']. This flag auto-confirms package installation and avoids user prompts during setup.

Suggested change

	args: ['mcp-remote', 'https://api.browser-use.com/mcp', '--header', 'X-Browser-Use-API-Key: <YOUR_API_KEY>'],
	args: ['-y', 'mcp-remote', 'https://api.browser-use.com/mcp', '--header', 'X-Browser-Use-API-Key: <YOUR_API_KEY>'],

[Copilot]

API key should be handled via environment variable instead of command-line argument for better security and consistency. The Discord entry (lines 527-533) demonstrates the correct pattern for mcp-remote with authentication: use env field with a variable like BROWSER_USE_API_KEY. Command-line arguments may be logged or exposed in process listings. Suggested configuration: args: ['-y', 'mcp-remote', 'https://api.browser-use.com/mcp'] with env: { BROWSER_USE_API_KEY: '<YOUR_API_KEY>' }.

Suggested change

	args: ['mcp-remote', 'https://api.browser-use.com/mcp', '--header', 'X-Browser-Use-API-Key: <YOUR_API_KEY>'],
	args: ['mcp-remote', 'https://api.browser-use.com/mcp'],
	env: {
	BROWSER_USE_API_KEY: '<YOUR_API_KEY>',
	},