BrowserStack MCP integration for AI agents.
Connect AI agents to BrowserStack through 4 structured actions, including get session, list build sessions, and list builds. Review authentication, inputs, w…
- ACTION CONTRACTS
- 4
- 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 BrowserStack integration exposes
The BrowserStack Agent App exposes 4 provider-backed actions for developer tools work. Its current contract lets an authorized agent retrieve details for a browserstack automate session, list browserstack automate sessions for a build, and list recent browserstack automate builds with optional status, project, and pagination filters. 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 BrowserStack account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BrowserStack capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_sessionREADRetrieve details for a BrowserStack Automate session.
INPUTS: session_id
list_build_sessionsREADList BrowserStack Automate sessions for a build.
INPUTS: build_id / limit / offset / status
list_buildsREADList recent BrowserStack Automate builds with optional status, project, and pagination filters.
INPUTS: limit / offset / status / project_id
update_session_statusREADMark a BrowserStack Automate session as passed or failed with a reason.
INPUTS: session_id / status / reason
INPUT CONTRACTS
Know what the action needs before it runs.
get_session
session_idREQUIRED- The BrowserStack session hashed_id.
list_build_sessions
build_idREQUIRED- The BrowserStack build hashed_id.
limitOPTIONAL- The number of results to return. BrowserStack accepts 1 to 100.
offsetOPTIONAL- The zero-based result offset.
statusOPTIONAL- Only return sessions with this BrowserStack status.
list_builds
limitOPTIONAL- The number of results to return. BrowserStack accepts 1 to 100.
offsetOPTIONAL- The zero-based result offset.
statusOPTIONAL- A BrowserStack Automate build status filter.
project_idOPTIONAL- Only return builds for this BrowserStack project ID.
update_session_status
session_idREQUIRED- The BrowserStack session hashed_id.
statusREQUIRED- A BrowserStack Automate session status.
reasonREQUIRED- The reason to store with the BrowserStack session status.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Session
Retrieve details for a BrowserStack Automate session. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_sessionVerify with List Build Sessions
List BrowserStack Automate sessions for a build. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_build_sessionsSAFETY BOUNDARY
Operate BrowserStack with explicit limits
- Authorize BrowserStack with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BrowserStack data may still be sensitive and should be minimized before it enters model context.
- 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 BrowserStack rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BrowserStack task completed successfully.
CONNECTION MODEL
API key
BrowserStack access key used as the HTTP Basic Auth password. Copy it from BrowserStack Account > Settings > Access Keys: https://www.browserstack.com/accounts/settings.
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
- 0
- 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 BrowserStack.