302AI BrowserUse MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 302AI_API_KEY | Yes | Your 302AI API key that can be found at https://dash.302.ai/apis/list |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createBrowserAgentTaskA | Create a browser agent task, and return the task id. This agent can handle continuous complex tasks, and you do not need to break down the tasks. Just input them directly. Clearly return the task_id to the user for use in the next request. |
| getBrowserAgentTaskResultA | Get the result of the browser agent task. If no results are obtained, clearly return the task_id to the user for use in the next request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one creates a task, the other retrieves its result. There is no overlap or ambiguity.
Both tools use camelCase and follow a verb_noun pattern, but one ends with 'Task' and the other with 'TaskResult', introducing minor inconsistency. Still understandable.
With only 2 tools, the server feels minimal. While it may suffice for the specific purpose of managing browser agent tasks, it is on the low end of reasonable scope.
The tool set covers creation and result retrieval, but lacks any management operations (e.g., list, cancel, retry). This limits the agent's ability to handle errors or task lifecycles.