What can you do with the BrowserStack integration?

LiveContext exposes 28 operations on BrowserStack, covering session, build, project and media. Common uses include automate session management, automate build management and automate project management.

LiveContext

All integrations

BrowserStack integration

Cloud-based browser and mobile app testing platform that enables testing on real devices and browsers

28 toolsBasic authAPI docs

Connect BrowserStack How integrations work

Common BrowserStack use cases

automate session management
automate build management
automate project management
delete build programmatically
delete session programmatically
automate media management
session debugging
mobile test debugging
get plan programmatically
list build programmatically

What you can do with BrowserStack

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Session, 5 operations

DELETEdelete_session
Permanently delete a specific test session including its logs, video recordings, and screenshots. Sessions once deleted cannot be recovered.
DELETEdelete_sessions
Delete multiple sessions at once. Pass multiple sessionId query parameters for bulk deletion. Sessions once deleted cannot be recovered.
GETget_session
Get detailed information about a specific test session including browser configuration, duration, status, and URLs for video recordings, logs, and screenshots.
GETlist_sessions
Get a paginated list of test sessions within a specific build. Each session represents an individual test execution with its own browser configuration, logs, and video recording.
PUTupdate_session
Update session details including marking test status as passed or failed, updating the session name, and providing a failure reason for reporting.

Build, 4 operations

DELETEdelete_build
Permanently delete a specific build and all its associated test sessions, logs, videos, and screenshots. Builds once deleted cannot be recovered.
DELETEdelete_builds
Delete multiple builds at once. Maximum 5 builds can be deleted per request. All sessions within deleted builds are also removed. Builds once deleted cannot be recovered. Pass multiple buildId query parameters (e.g., ?buildId=id1&buildId=id2&build...
GETlist_builds
Get a paginated list of test builds with optional filtering by status and project. Each build groups related test sessions executed together. Returns the 10 most recent builds by default.
PUTupdate_build
Update build details such as name and tags. Build name accepts A-Z, a-z, 0-9, and special characters like . : - [] / @ & ' _ with a 255-character limit.

Project, 4 operations

DELETEdelete_project
Permanently delete a project from your BrowserStack account. The project must be empty (contain no builds) before it can be deleted. Projects once deleted cannot be recovered.
GETget_project
Get detailed information about a specific project including its associated builds, creation date, and metadata.
GETlist_projects
Get a list of all projects in your BrowserStack account. Projects group related builds and sessions for organizational purposes.
PUTupdate_project
Update project details such as the project name. Name accepts A-Z, a-z, 0-9, and special characters like . : - [] / @ & ' _ with a 255-character limit.

Media, 2 operations

DELETEdelete_media
Delete an uploaded media file by its unique identifier. Files are also automatically deleted after 30 days from upload.
POSTupload_media
Upload a media file (image, video, etc.) for use in automated tests. Maximum 10 files can be stored at a time. Files are automatically deleted after 30 days.

Browser, 1 operation

GETlist_browsers
Get the complete list of all available browsers, operating systems, and real mobile devices for testing on BrowserStack Automate. Includes desktop browsers (Chrome, Firefox, Safari, Edge) and real mobile devices (iOS, Android).

Media file, 1 operation

GETlist_media_files
Get a list of recently uploaded media files for use in automated tests. Files are automatically deleted after 30 days from upload. Maximum 10 files can be stored at a time.

Plan, 1 operation

GETget_plan
Get details about your BrowserStack Automate plan including running sessions, maximum allowed parallel sessions, queued sessions, and capacity limits.

Project badge, 1 operation

GETget_project_badge
Get the badge key for a project to embed status badges in README files and documentation. The badge shows the status of the latest build in that project.

Recycle key, 1 operation

PUTrecycle_key
Reset your BrowserStack access key. Generates a new access key and invalidates the old one. The response contains both the old and new access keys.

Session appium log, 1 operation

GETget_session_appium_logs
Get Appium framework logs for a mobile test session. Only available for real-device Appium sessions. Contains internal Appium commands and execution details.

Session console log, 1 operation

GETget_session_console_logs
Get JavaScript console logs (console.log, console.error, console.warn) captured from the browser during the test session. Useful for debugging frontend issues.

Session log, 1 operation

GETget_session_logs
Get the raw Selenium/WebDriver session logs containing all HTTP requests and responses between the test client and the browser. Available in text format.

Session network log, 1 operation

GETget_session_network_logs
Get network logs in HAR (HTTP Archive) format capturing all HTTP traffic, request/response headers, and latency during the test session.

Session selenium log, 1 operation

GETget_session_selenium_logs
Get Selenium/WebDriver framework logs for the test session containing internal Selenium commands and their execution details.

Session telemetry log, 1 operation

GETget_session_telemetry_logs
Get Selenium telemetry logs for the test session. Telemetry logs are available for tests run using Selenium 4 and must be enabled via the telemetryLogs capability. Downloaded as a compressed telemetrylogs.gz file.

Terminal logs build, 1 operation

POSTupload_terminal_logs_build
Upload terminal or CI/CD logs for a build for debugging and post-mortem analysis. Maximum file size is 2MB.

Terminal logs session, 1 operation

POSTupload_terminal_logs_session
Upload terminal or CI/CD logs for a specific test session for debugging and post-mortem analysis. Maximum file size is 2MB.

Use BrowserStack from Claude Code, Cursor or Codex

Connect BrowserStack in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its BrowserStack operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect BrowserStack

Create your workspace
Sign up free. Nothing to install.
Connect BrowserStack once
Add your BrowserStack connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

BrowserStack integration FAQ

What can you do with the BrowserStack integration?: LiveContext exposes 28 operations on BrowserStack, covering session, build, project and media. Common uses include automate session management, automate build management and automate project management.