302_browser_use_mcp

302 Browser Use MCP Server

302AI BrowserUse connects natural-language requests to remote browser automation built on Browser Use and Sandbox. It serves MCP client users who want to submit web tasks, retain a task ID, and retrieve results through a separate tool.

Server facts

302_browser_use_mcp MCP Server

Project

Author
302ai
License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
9
Last commit
Data as of

Tags

  • Browser Automation
  • automation tool
  • remote browser

Overview

Remote browser tasks are the focus of 302AI BrowserUse, which combines Browser Use and Sandbox with an MCP interface for natural-language browser control and web research. Its createBrowserAgentTask tool accepts a task description and returns an identifier. The tool description supports submitting complex, continuous work directly rather than first dividing it into smaller requests. This gives the workflow a submission stage followed by a separate result lookup, with the task ID linking those interactions.

The getBrowserAgentTaskResult tool retrieves the outcome associated with a browser task. When results are not yet available, the documented workflow keeps the identifier available for a later request. The project also describes refreshing its tool list from a remote server and running locally over stdio or as a hosted HTTP service. Configuration examples cover Claude Desktop, Cherry Studio, and ChatWise, passing a 302AI_API_KEY environment variable. Development documentation includes build, watch, and MCP Inspector debugging workflows.

302_browser_use_mcp setup notes

  • 302_browser_use_mcp records stdio only; confirm a network transport upstream before planning remote access.
  • 302_browser_use_mcp has no recorded license; confirm reuse terms in its repository.

Related MCP servers