browserstack/mcp-server

• querystringобязательный

  Any accessibility, a11y, WCAG, or web accessibility question

• indexnumberобязательный

  Index of the test file to update

• project_identifierstringобязательный

  Identifier of the project (Starts with 'PR-')

• test_case_idstringобязательный

  Identifier of the test case, e.g., 'TC-13'.

• test_resultobjectобязательный
• test_run_idstringобязательный

  Identifier of the test run (e.g., TR-678)

• namestringобязательный

  Name for the auth configuration

• passwordstring

  Site password; omit to have it requested from the user.

• passwordSelectorstring

  CSS selector for password field (required for form auth)

• submitSelectorstring

  CSS selector for submit button (required for form auth)

• typeenumобязательный

  Authentication type: 'form' for form-based auth, 'basic' for HTTP basic auth

• urlstringобязательный

  URL of the authentication page

• usernamestring

  Site username; omit to have it requested from the user.

• usernameSelectorstring

  CSS selector for username field (required for form auth)

• base_urlstringобязательный

  Base URL for the test (e.g., 'google.com')

• credentialsobject

  Login credentials; omit to have them requested from the user.

• local_enabledboolean

  Whether local testing is enabled

• project_identifierstringобязательный

  ID of the project (Starts with 'PR-')

• requires_authenticationboolean

  Set true if the test case requires login.

• test_case_detailsobjectобязательный

  Test case details including steps

• test_case_identifierstringобязательный

  Identifier of the test case (e.g., 'TC-12345')

• test_namestringобязательный

  Name of the test

• wait_for_completionboolean

  Whether to wait for LCA build completion (default: true)

• folder_descriptionstring

  Description for the new folder.

• folder_namestring

  Name of the folder to create.

• parent_idnumber

  Parent folder ID; if omitted, folder is created at root.

• project_descriptionstring

  Description for the new project.

• project_identifierstring

  Existing project identifier to use for folder creation.

• project_namestring

  Name of the project to create.

• automation_statusstring

  Automation status of the test case. Common values include 'not_automated', 'automated', 'automation_not_required'.

• case_typestring

  Test case type display or internal name (per-project). Omit for project default.

• custom_fieldsobject

  Map of custom field NAME to value; use an array for multi-select fields.

• descriptionstring

  Brief description of the test case.

• folder_idstringобязательный

  The ID of the folder within the project where the test case should be created. If not provided, ask the user if they would like to create a new folder using the createProjectOrFolder tool.

• issuesstring[]

  List of the linked Jira, Asana or Azure issues ID's. This should be strictly in array format not the string of json.

• issue_trackerobject
• namestringобязательный

  Name of the test case.

• ownerstring

  Email of the test case owner.

• preconditionsstring

  Any preconditions (HTML allowed).

• prioritystring

  Priority of the test case. Accepts either display name (e.g. 'Critical', 'High', 'Medium', 'Low') or internal name (e.g. 'medium'). If omitted, the project default (usually 'Medium') is applied. Valid values are per-project and discoverable via the form-fields endpoint.

• project_identifierstringобязательный

  The ID of the BrowserStack project where the test case should be created. If no project identifier is provided, ask the user if they would like to create a new project using the createProjectOrFolder tool.

• tagsstring[]

  Tags to attach to the test case. This should be strictly in array format not the string of json

• templatestring

  System template slug only: 'test_case_steps' or 'test_case_bdd'. For a custom template, use template_id instead.

• template_idnumber

  Numeric ID of a custom template (from listTestCaseTemplates); applies that template. Overrides 'template'.

• test_case_stepsobject[]обязательный

  List of steps and expected results.

• documentIdstringобязательный

  Internal document identifier

• folderIdstringобязательный

  BrowserStack folder ID

• projectReferenceIdstringобязательный

  The BrowserStack project reference ID is a unique identifier found in the project URL within the BrowserStack Test Management Platform. This ID is also returned by the Upload Document tool.

• project_identifierstringобязательный

  Identifier of the project in which to create the test run.

• test_runobjectобязательный

• detectedBrowserAutomationFrameworkenumобязательный
• detectedLanguageenumобязательный
• detectedTestingFrameworkenumобязательный
• filePathsstring[]

  An array of absolute file paths to specific UI test files. Use this when you want to target specific test files rather than entire folders. If not provided, will use folderPaths instead.

• folderPathsstring[]

  An array of absolute folder paths containing UI test files. If not provided, analyze codebase for UI test folders by scanning for test patterns which contain UI test cases as per framework. Return empty array if none found.

• integrationTypeenumобязательный

  Specify the Percy integration type: web (Percy Web) or automate (Percy Automate). If not provided, always prompt the user with: 'Please specify the Percy integration type.' Do not proceed without an explicit selection. Never use a default.

• projectNamestringобязательный

  A unique name for your Percy project.

• cursornumber

  Character offset for pagination (default: 0)

• scanIdstringобязательный

  The scan ID from a completed accessibility scan

• scanRunIdstringобязательный

  The scan run ID from a completed accessibility scan

• sessionIdstringобязательный

  The BrowserStack session ID to fetch screenshots from

• sessionTypeenumобязательный

  Type of BrowserStack session

• buildIdstringобязательный

  The build UUID of the BrowserStack build

• project_namestringобязательный

  The name of the BrowserStack project. If not found, ask user directly.

• testIdinteger[]обязательный

  Array of integer test IDs to fetch RCA data for (maximum 3 IDs). These must be numeric test IDs, not session IDs or strings. If not provided, use the listTestIds tool to get all failed testcases. If more than 3 IDs are provided, only the first 3 will be processed.

• buildUuidstring

  Build UUID. Fetches the build's self-healing report.

• sessionIdstring

  Session ID. Mutually exclusive with buildUuid.

• sessionTypeenum

  Used with sessionId. Defaults to automate.

• configIdnumberобязательный

  ID of the auth configuration to retrieve

• browserStackBuildNamestringобязательный

  The BrowserStack build name used during test run creation. Action: First, check browserstack.yml or any equivalent project configuration files. If the build name is found, extract and return it. If it is not found or if there is any uncertainty, immediately prompt the user to provide the value. Do not infer, guess, or assume a default.

• browserStackProjectNamestringобязательный

  The BrowserStack project name used during test run creation. Action: First, check browserstack.yml or any equivalent project configuration files. If the project name is found, extract and return it. If it is not found or if there is any uncertainty, immediately prompt the user to provide the value. Do not infer, guess, or assume a default.

• buildIdstring

  Required only when sessionType is 'app-automate'. If sessionType is 'app-automate', always ask the user to provide the build ID before proceeding.

• logTypesenum[]обязательный

  The types of logs to fetch.

• sessionIdstringобязательный

  The BrowserStack session ID. Must be explicitly provided by the user.

• sessionTypeenumобязательный

  Type of BrowserStack session. Must be explicitly provided by the user.

• parent_test_plan_identifierstringобязательный

  Parent test plan identifier (TP-*).

• project_identifierstringобязательный

  Project identifier (PR-*).

• sub_test_plan_identifierstringобязательный

  Sub-test-plan identifier (STP-*).

• project_identifierstringобязательный

  Identifier of the project (starts with PR- followed by a number).

• test_plan_identifierstringобязательный

  Identifier of the test plan (starts with TP- followed by a number).

• browserStackBuildNamestringобязательный

  The BrowserStack build name used during test run creation. Action: First, check browserstack.yml or any equivalent project configuration files. If the build name is found, extract and return it. If it is not found or if there is any uncertainty, immediately prompt the user to provide the value. Do not infer, guess, or assume a default.

• browserStackProjectNamestringобязательный

  The BrowserStack project name used during test run creation. Action: First, check browserstack.yml or any equivalent project configuration files. If the project name is found, extract and return it. If it is not found or if there is any uncertainty, immediately prompt the user to provide the value. Do not infer, guess, or assume a default.

• pnumber

  Page number.

• parent_idnumber

  If provided, list sub-folders under this parent folder id. If omitted, lists top-level folders.

• project_identifierstringобязательный

  Identifier of the project to fetch folders from (starts with PR- followed by a number).

• pnumber

  Page number.

• parent_test_plan_identifierstringобязательный

  Parent test plan identifier (TP-*).

• project_identifierstringобязательный

  Project identifier (PR-*).

• case_typestring

  Comma-separated list of case types (e.g. functional,regression).

• folder_idstring

  Optional. If provided, only return test cases in this folder. If omitted, returns all test cases in the project. Folder ids can be discovered via listFolders.

• pnumber

  Page number.

• prioritystring

  Comma-separated list of priorities (e.g. critical,medium,low).

• project_identifierstringобязательный

  Identifier of the project to fetch test cases from. This id starts with a PR- and is followed by a number.

• namestring

  Case-insensitive substring filter on template name.

Без параметров.

• buildIdstringобязательный

  The Browserstack Build ID of the test run. If not known, use the getBuildId tool to fetch it using project and build name

• includeFailureDetailboolean

  Add per-test failure signature for clustering. Default false.

• statusenumобязательный

  Filter tests by status. If not provided, all tests are returned. Example for RCA usecase always use failed status

• pnumber

  Page number.

• project_identifierstringобязательный

  Identifier of the project to fetch test plans from (starts with PR- followed by a number).

• project_identifierstringобязательный

  Identifier of the project to fetch test runs from (usually starts with PR-).

• run_statestring

  Return all test runs with this state (comma-separated)

• actionenumобязательный

  The action to perform on the Percy build.

• buildIdstringобязательный

  The ID of the Percy build to approve or reject.

• detectedBrowserAutomationFrameworkenumобязательный
• detectedLanguageenumобязательный
• detectedTestingFrameworkenumобязательный
• filePathsstring[]

  An array of absolute file paths to specific UI test files. Use this when you want to target specific test files rather than entire folders. If not provided, will use folderPaths instead.

• folderPathsstring[]

  An array of absolute folder paths containing UI test files. If not provided, analyze codebase for UI test folders by scanning for test patterns which contain UI test cases as per framework. Return empty array if none found.

• integrationTypeenumобязательный

  Specify the Percy integration type: web (Percy Web) or automate (Percy Automate). If not provided, always prompt the user with: 'Please specify the Percy integration type.' Do not proceed without an explicit selection. Never use a default.

• projectNamestringобязательный

  A unique name for your Percy project.

• sessionsobject[]обязательный

  Sessions to plan edits for. See tool description for accepted shapes.

• appPathstringобязательный

  The path to the .ipa or .apk file to install on the device. Always ask the user for the app path, do not assume it.

• desiredPhonestringобязательный

  The full name of the device to run the app on. Example: 'iPhone 12 Pro' or 'Samsung Galaxy S20' or 'Google Pixel 6'. Always ask the user for the device they want to use, do not assume it.

• desiredPlatformenumобязательный

  Which platform to run on, examples: 'android', 'ios'. Set this based on the app path provided.

• desiredPlatformVersionstringобязательный

  Specifies the platform version to run the app on. For example, use '12.0' for Android or '16.0' for iOS. If the user says 'latest', 'newest', or similar, normalize it to 'latest'. Likewise, convert terms like 'earliest' or 'oldest' to 'oldest'.

• appPathstringобязательный

  Path to your application file: If in development IDE directory: • For Android: 'gradle assembleDebug' • For iOS: xcodebuild clean -scheme YOUR_SCHEME && xcodebuild archive -scheme YOUR_SCHEME -configuration Release -archivePath build/app.xcarchive && xcodebuild -exportArchive -archivePath build/app.xcarchive -exportPath build/ipa -exportOptionsPlist exportOptions.plist If in other directory, provide existing app path

• detectedAutomationFrameworkenumобязательный

  The automation framework used in the project, such as 'espresso' (Android) or 'xcuitest' (iOS).

• devicesobject[]

  Tuples describing target mobile devices. Add device only when user asks explicitly for it. Defaults to [] . Example: [['android', 'Samsung Galaxy S24', '14'], ['ios', 'iPhone 15', '17']]

• projectstring

  Project name for organizing test runs on BrowserStack.

• testSuitePathstringобязательный

  Path to your test suite file: If in development IDE directory: • For Android: 'gradle assembleAndroidTest' • For iOS: xcodebuild test-without-building -scheme YOUR_SCHEME -destination 'generic/platform=iOS' && cd ~/Library/Developer/Xcode/DerivedData/*/Build/Products/Debug-iphonesimulator/ && zip -r Tests.zip *.xctestrun *-Runner.app If in other directory, provide existing test file path

• desiredBrowserenumобязательный

  Browser for desktop (Chrome, IE, Firefox, Safari, Edge)

• desiredBrowserVersionstring

  Browser version for desktop (e.g. '133.2', 'latest'). If the user says 'latest', 'newest', or similar, normalize it to 'latest'. Likewise, convert terms like 'earliest' or 'oldest' to 'oldest'.

• desiredDevicestring

  Device name for mobile

• desiredOSenumобязательный

  Desktop OS ('Windows' or 'OS X') or mobile OS ('android','ios','winphone')

• desiredOSVersionstringобязательный

  The OS version must be specified as a version number (e.g., '10', '14.0') or as a keyword such as 'latest' or 'oldest'. Normalize variations like 'newest' or 'most recent' to 'latest', and terms like 'earliest' or 'first' to 'oldest'. For macOS, version names (e.g., 'Sequoia') must be used instead of numeric versions.

• desiredURLstringобязательный

  The URL to test

• platformTypeenumобязательный

  Must be 'desktop' or 'mobile'

• integrationTypeenumобязательный

  Specifies whether to integrate with Percy Web or Percy Automate. If not explicitly provided, prompt the user to select the desired integration type.

• percyRunCommandstring

  The test command to run with Percy. Optional — the LLM should try to infer it first from project context.

• projectNamestringобязательный

  The name of the project to run Percy on.

• appPathstringобязательный

  Path to the mobile app file (.apk for Android, .ipa for iOS). Can be a local file path or a BrowserStack app URL (bs://)

• detectedFrameworkenumобязательный

  The mobile automation framework configured in the project. Example: 'appium'

• detectedLanguageenumобязательный

  The programming language used in the project. Supports Java and C#. Example: 'java', 'csharp'

• detectedTestingFrameworkenumобязательный

  The testing framework used in the project. Be precise with framework selection Example: 'testng', 'behave', 'pytest', 'robot'

• devicesobject[]

  Tuples describing target mobile devices. Add device only when user asks explicitly for it. Defaults to [] . Example: [['android', 'Samsung Galaxy S24', '14'], ['ios', 'iPhone 15', '17']]

• projectstring

  Project name for organizing test runs on BrowserStack.

• detectedBrowserAutomationFrameworkenumобязательный
• detectedLanguageenumобязательный
• detectedTestingFrameworkenumобязательный
• devicesobject[]

  Device objects array. Use the object format directly - no transformation needed. Add only when user explicitly requests devices. Examples: [{ platform: 'windows', osVersion: '11', browser: 'chrome', browserVersion: 'latest' }] or [{ platform: 'android', deviceName: 'Samsung Galaxy S24', osVersion: '14', browser: 'chrome' }].

• projectNamestringобязательный

  A single name for your project to organize all your tests.

• advancedRulesboolean

  Enable advanced accessibility rules in the scan settings

• authConfigIdnumber

  Optional auth config ID for authenticated scans

• namestringобязательный

  Name of the accessibility scan

• pageURLstringобязательный

  The URL to scan for accessibility issues

• appPathstringобязательный

  The path to the .apk or .ipa file. Required for app installation.

• desiredPhonestringобязательный

  The full name of the device to run the app on. Example: 'iPhone 12 Pro' or 'Samsung Galaxy S20'. Always ask the user for the device they want to use.

• desiredPlatformenumобязательный

  Platform to run the app on. Either 'android' or 'ios'.

• desiredPlatformVersionstringобязательный

  The platform version to run the app on. Use 'latest' or 'oldest' for dynamic resolution.

• automation_statusstring

  Updated automation status. Use internal name such as 'not_automated', 'automated', 'automation_not_required', 'cannot_be_automated', or 'obsolete'.

• case_typestring

  Updated test case type. Accepts either display name (e.g. 'Functional', 'Regression', 'Smoke & Sanity') or internal name (e.g. 'functional', 'smoke_sanity'). Valid values are per-project.

• custom_fieldsobject

  Map of custom field NAME to value; use an array for multi-select fields.

• descriptionstring

  Updated brief description of the test case.

• issuesstring[]

  Replacement list of linked Jira/Asana/Azure issue IDs for the test case.

• namestring

  Updated name of the test case.

• ownerstring

  Email of the test case owner.

• preconditionsstring

  Updated preconditions for the test case.

• prioritystring

  Updated priority. Accepts either display name (e.g. 'Medium', 'Critical', 'High', 'Low') or internal name (e.g. 'medium'). Valid values are per-project and discoverable via the form-fields endpoint.

• project_identifierstringобязательный

  The ID of the BrowserStack project containing the test case to update.

• statusstring

  Updated review status of the test case (e.g. 'active', 'draft', 'in_review', 'outdated', 'rejected').

• tagsstring[]

  Replacement list of tags for the test case.

• test_case_identifierstringобязательный

  The ID of the test case to update. This can be found using the listTestCases tool.

• test_case_stepsobject[]

  Updated list of test case steps with expected results.

• project_identifierstringобязательный

  Identifier of the project (Starts with 'PR-')

• test_runobjectобязательный
• test_run_idstringобязательный

  Test run identifier (e.g., TR-678)

• file_pathstringобязательный

  Full path to the file that should be uploaded

• project_identifierstringобязательный

  ID of the project where the file should be uploaded. Do not assume it, always ask user for it.