BrowserStack

Run tests on real BrowserStack browsers and devices, debug failures and manage test cases in Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the BrowserStack connector does

The BrowserStack MCP server connects Claude to BrowserStack's testing platform. Anthropic's directory lists 37 tools for starting live sessions on real browsers and devices, setting up and running automated suites, debugging failures, scanning for accessibility issues and managing test cases and runs. It signs in with OAuth, and BrowserStack says data changes need your approval.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

BrowserStack tools (37)

  • accessibilityExpert
  • addTestResult
  • createAccessibilityAuthConfig
  • createLCASteps
  • createProjectOrFolder
  • createTestCase
  • createTestRun
  • fetchAccessibilityIssues
  • fetchAutomationScreenshots
  • fetchBuildInsights
  • fetchRCA
  • fetchSelfHealedSelectors
  • getAccessibilityAuthConfig
  • getBuildId
  • getFailureLogs
  • getSubTestPlan
  • getTestPlan
  • help-asset-upload
  • listBuildId
  • listFolders
  • listSubTestPlans
  • listTestCaseTemplates
  • listTestCases
  • listTestIds
  • listTestPlans
  • listTestRuns
  • managePercyBuildApproval
  • prepareSelfHealingPlan
  • runAppLiveSession
  • runAppTestsOnBrowserStack
  • runBrowserLiveSession
  • setupBrowserStackAppAutomateTests
  • setupBrowserStackAutomateTests
  • startAccessibilityScan
  • takeAppScreenshot
  • updateTestCase
  • updateTestRun

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No Local Testing on the remote server. Use BrowserStack's local MCP server for localhost, VPN or firewalled apps.
  • Product access governs results. Tools for Live, Automate, Accessibility or Test Management need those products on your BrowserStack account.
  • Scopes are coarse. The server advertises read, write and admin; BrowserStack does not document what each grants, or whether you can decline one on the consent screen.
  • Non-deterministic results. BrowserStack's README warns that tool calls rely on an LLM, so behaviour can be unexpected.
  • No rate limits or quotas are documented for the MCP server.
  • We did not read the tools. Our anonymous request returned a 401, so schemas and annotations are not on this page.
  • Data handling, as BrowserStack states it. BrowserStack says data is processed in real time and not stored, is not used to train AI models, and is isolated between tenants.

Frequently asked questions

Do I need a BrowserStack account to use the MCP server?

Yes. BrowserStack's MCP page states that an account is required, and its get-started guide notes a free trial is available. The remote server signs you in with OAuth, so you never paste a username or access key into Claude. Which tools return useful results depends on the BrowserStack products your account includes, such as Live, Automate, Test Management or Accessibility Testing.

Can the remote BrowserStack MCP server test a site on localhost?

No. BrowserStack's README lists no Local Testing support as a limitation of the remote server, so it cannot test apps behind a VPN, a firewall or on localhost. For those, BrowserStack points you to its local MCP server, which runs on your machine with Node.js 20.9 or later and authenticates with your BrowserStack username and access key rather than OAuth.

How is the BrowserStack MCP server different from BrowserStack AI agents?

The MCP server brings BrowserStack's capabilities into your own AI assistant; the AI agents are built into BrowserStack's products. BrowserStack's FAQ describes its AI agents as handling specific tasks independently inside the product. Through MCP, Claude can still call some of them, such as low-code step generation with createLCASteps and self-healed selectors with fetchSelfHealedSelectors.

Does the BrowserStack MCP server change my code automatically?

No. BrowserStack says that when it fetches a root cause analysis, the server returns the suggested fix as a proposal only and never applies code changes. Your assistant must show the suggestion and wait for your approval before editing files. The self-healing plan tool works the same way: BrowserStack describes prepareSelfHealingPlan as building an edit plan that does not modify files itself.

Sources

Use it in an agent

Put BrowserStack to work.

Connect BrowserStack once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.