Skip to directory

BrowserStack MCP

BrowserStack

Streamable HTTP (remote); stdio (local)5 documented tools2

About BrowserStack MCP

BrowserStack MCP connects AI clients to BrowserStack testing products for real-device and browser testing, accessibility, automation, test management, reporting, Percy visual testing, and load testing.

What you can use it for

  • Run web and mobile tests on real browsers/devices.
  • Inspect and manage test cases, runs and reports.
  • Run accessibility scans and analyze failures.
  • Perform Percy visual reviews and supported load testing.
Connection and setup
Hosting
Both local and remote hosted
Transport
Streamable HTTP (remote); stdio (local)
Endpoint
https://mcp.browserstack.com/mcp
Authentication
Remote server uses OAuth browser login. Local server uses BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY environment variables.

Requirements

  • BrowserStack account and credentials; account roles/products determine access.
  • Local server requires Node.js v22 or later and package @browserstack/mcp-server.
  • Specific product features require corresponding licenses/enabling; Load Testing rollout may require support enablement and package v2.2.0+.

Setup steps

  1. Choose remote hosted or local installation. For remote, add https://mcp.browserstack.com/mcp as an HTTP server and complete OAuth.
  2. For local, configure `npx -y @browserstack/mcp-server@latest` with username and access key environment variables; keep secrets locally.
  3. Discover available product workflows with `listProducts`; search a requested action using `searchCapability`, inspect it with `describeCapability`, then call `invokeCapability`.
  4. Reads can run under account permissions. The server requires explicit user approval for writes before it executes them.
  5. Start with a harmless read, such as listing products or available projects; consult the docs for product-specific license limits.
Tools 5

BrowserStack documents five core MCP tools: listProducts, describeEntity, searchCapability, describeCapability and invokeCapability. Product-specific workflows are dynamically discovered; writes require approval.

  • listProducts

    List BrowserStack products and summaries.

    01
  • describeEntity

    Describe an entity, its identifiers, relations, and applicable capabilities.

    02
  • searchCapability

    Find capabilities matching a natural-language task.

    03
  • describeCapability

    Return capability parameters and request/response details.

    04
  • invokeCapability

    Run a capability; writes require user approval.

    05
Limitations and notes
  • Available workflows depend on product entitlements and account permissions.
  • Load Testing is being rolled out in phases; requires enablement and local package v2.2.0+ per docs.
  • Write operations require user approval; user/admin role may be required by product.
  • Local and remote setups use different authentication and hosting models.
Original sources
  • official tool reference

    BrowserStack official docs enumerate exactly five core MCP meta-tools matching stored names. Product workflow capabilities are discovered dynamically; OAuth/credentials and account entitlements affect access, and writes require user approval.

  • official documentation or source

    BrowserStack official docs enumerate exactly five core MCP meta-tools matching stored names. Product workflow capabilities are discovered dynamically; OAuth/credentials and account entitlements affect access, and writes require user approval.

Documentation checked 2026-10-28T13:00:03.000Z. Connection has not been runtime tested.

Similar tools