Browse AI MCP integration for AI agents.
Connect AI agents to Browse AI through 6 structured actions, including get robot, run robot task, and get robot task. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Browse AI integration exposes
The Browse AI Agent App exposes 6 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent retrieve one browse ai robot and its input parameter definitions by robot id, start one browse ai robot task with optional inputparameters overrides, and retrieve one browse ai robot task and its captured data by robot and task ids. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Browse AI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Browse AI capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_robotREADRetrieve one Browse AI robot and its input parameter definitions by robot ID.
INPUTS: robotId
run_robot_taskWRITEStart one Browse AI robot task with optional inputParameters overrides.
INPUTS: robotId / recordVideo / inputParameters
get_robot_taskREADRetrieve one Browse AI robot task and its captured data by robot and task IDs.
INPUTS: robotId / taskId
list_robot_tasksREADList Browse AI robot tasks with pagination and status filters.
INPUTS: robotId / page / pageSize / status / robotBulkRunId
list_robotsREADList the Browse AI robots available to the connected API key.
update_robot_cookiesWRITEUpdate the cookies stored on one Browse AI robot.
INPUTS: robotId / cookies
INPUT CONTRACTS
Know what the action needs before it runs.
get_robot
robotIdREQUIRED- The Browse AI robot ID.
run_robot_task
robotIdREQUIRED- The Browse AI robot ID.
recordVideoOPTIONAL- Whether Browse AI should attempt to record a task video.
inputParametersOPTIONAL- The inputParameters object accepted by a Browse AI robot task.
get_robot_task
robotIdREQUIRED- The Browse AI robot ID.
taskIdREQUIRED- The Browse AI task ID.
list_robot_tasks
robotIdREQUIRED- The Browse AI robot ID.
pageOPTIONAL- The Browse AI task list page number.
pageSizeOPTIONAL- The number of tasks to return per page.
statusOPTIONAL- The Browse AI task status filter.
robotBulkRunIdOPTIONAL- The Browse AI bulk run ID used to filter tasks.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Robot
Retrieve one Browse AI robot and its input parameter definitions by robot ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_robotControl Run Robot Task
Start one Browse AI robot task with optional inputParameters overrides. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
run_robot_taskVerify with Get Robot Task
Retrieve one Browse AI robot task and its captured data by robot and task IDs. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_robot_taskSAFETY BOUNDARY
Operate Browse AI with explicit limits
- Authorize Browse AI with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Browse AI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Browse AI task completed successfully.
CONNECTION MODEL
API key
Browse AI secret API key passed in the Authorization Bearer header. Create it in the API tab of your Browse AI dashboard: https://help.browse.ai/en/articles/12683249-api-guide-getting-started.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Browse AI.