What can @browserstack/mcp-server do?

browserstack device session orchestration via mcp protocol, real device session lifecycle management through mcp tools, device capability querying and filtering via mcp, test execution and result collection through mcp, network condition simulation and performance testing via mcp, screenshot and video capture with automated analysis, test report generation and result aggregation, mcp protocol transport and authentication management

@browserstack/mcp-server

MCP ServerFree

BrowserStack's Official MCP Server

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

browserstack device session orchestration via mcp protocol

Medium confidence

Exposes BrowserStack's device cloud infrastructure through the Model Context Protocol, enabling LLM agents and Claude instances to programmatically request, configure, and manage real device sessions (iOS, Android, web browsers) without direct API calls. Implements MCP server transport layer that translates Claude tool calls into BrowserStack REST API operations, handling authentication, session lifecycle, and device allocation.

Solves for

I want Claude to automatically provision a real iOS device for testing my mobile app without me manually logging into BrowserStackI need an AI agent to run cross-browser compatibility tests across 20+ device/OS combinations and report resultsI want to integrate BrowserStack device access into my Claude-powered QA automation workflow

Best for

QA engineers building AI-assisted test automation workflows

DevOps teams integrating BrowserStack into Claude-based CI/CD pipelines

Mobile app developers using Claude as a testing copilot

Requires

BrowserStack account with valid API key and secret

Node.js 16+ runtime

MCP-compatible client (Claude Desktop, or custom MCP client implementation)

Limitations

Requires active BrowserStack subscription with API credentials — free tier may have limited concurrent sessions

MCP protocol overhead adds ~100-200ms per request compared to direct REST API calls

Session management is stateless at MCP layer — requires external persistence for multi-step test workflows

What makes it unique

First official MCP server implementation for BrowserStack, providing native Claude integration without custom API wrapper code. Uses MCP's tool-calling schema to abstract BrowserStack's REST API, enabling LLMs to reason about device capabilities and test scenarios directly.

vs alternatives

Eliminates need for custom Python/Node.js wrapper code around BrowserStack API — Claude can invoke device sessions directly through MCP tools, reducing integration latency and cognitive overhead for AI-driven QA workflows.

real device session lifecycle management through mcp tools

Medium confidence

Provides MCP tool definitions for creating, monitoring, and terminating BrowserStack device sessions with full lifecycle control. Implements session state tracking (active, idle, terminated), timeout handling, and graceful cleanup. Maps MCP tool calls to BrowserStack session endpoints, managing authentication headers and request/response serialization for each operation.

Solves for

I want Claude to start a test session on a specific device and automatically clean up when doneI need to check the status of running test sessions and terminate hung sessions programmaticallyI want Claude to manage session timeouts and prevent resource exhaustion

Best for

Automated test orchestration systems using Claude as the control plane

CI/CD pipelines that need dynamic device allocation without manual intervention

Teams running long-running test suites with automatic resource cleanup

Requires

BrowserStack API credentials with session management permissions

MCP client with tool-calling support

Active network connection to BrowserStack API

Limitations

Session timeout is controlled by BrowserStack server-side limits — MCP layer cannot extend beyond account tier limits

No transaction semantics — if session creation succeeds but cleanup fails, orphaned sessions may accumulate

Concurrent session limits depend on BrowserStack subscription tier, not MCP server capacity

What makes it unique

Implements full session lifecycle as atomic MCP tools rather than requiring multi-step API orchestration. Handles BrowserStack's session state machine (provisioning → active → idle → terminated) transparently, allowing Claude to reason about session health without understanding underlying API state transitions.

vs alternatives

Cleaner abstraction than raw BrowserStack API — Claude sees 'create session' and 'terminate session' as single operations, not multi-step provisioning workflows, reducing context overhead and error handling complexity.

device capability querying and filtering via mcp

Medium confidence

Exposes BrowserStack's device inventory as queryable MCP tools, allowing Claude to discover available devices, filter by OS/browser/version/capability, and retrieve detailed device metadata. Implements caching of device catalog to reduce API calls, with invalidation strategy for handling new device releases. Returns structured device objects with capabilities (touch, geolocation, network throttling, etc.) that Claude can reason about for test planning.

Solves for

I want Claude to automatically select the right devices for testing based on my app's OS requirementsI need to query which devices support a specific capability like 5G network simulationI want Claude to recommend device combinations for comprehensive cross-browser coverage

Best for

QA teams building intelligent test selection logic in Claude workflows

Mobile app developers who need AI-assisted device matrix planning

CI/CD systems that dynamically select test devices based on code changes

Requires

BrowserStack API key with read access to device catalog

MCP client with support for structured tool responses

Network access to BrowserStack API

Limitations

Device catalog is cached — new devices may not appear immediately after BrowserStack release

Capability filtering is limited to BrowserStack's predefined capability taxonomy — custom capabilities not supported

Large device inventory (1000+ devices) may cause slow response times if not paginated

What makes it unique

Transforms BrowserStack's static device catalog into a queryable knowledge base accessible to Claude through MCP tools. Implements client-side caching with TTL-based invalidation, reducing API load while keeping device metadata fresh for intelligent device selection.

vs alternatives

Enables Claude to reason about device capabilities at query time rather than requiring hardcoded device lists — Claude can dynamically select devices based on test requirements, OS support, and capability needs without manual device matrix maintenance.

test execution and result collection through mcp

Medium confidence

Provides MCP tools for executing test commands on provisioned BrowserStack devices and collecting results (screenshots, logs, performance metrics, test status). Implements streaming of test output back to Claude, with structured parsing of test results into actionable insights. Handles different test frameworks (Appium, Selenium, XCUITest) through abstraction layer that normalizes output formats.

Solves for

I want Claude to run a test suite on a real device and analyze the results to determine next stepsI need to capture screenshots and logs from test execution for debuggingI want Claude to interpret test failures and suggest fixes based on device-specific behavior

Best for

AI-driven test automation systems where Claude interprets test results

Debugging workflows where Claude analyzes device-specific failures

Continuous testing pipelines that need intelligent test result analysis

Requires

Active BrowserStack device session

Test code compatible with BrowserStack's supported frameworks (Appium, Selenium, XCUITest)

MCP client with support for streaming responses

Limitations

Test execution timeout is limited by BrowserStack session timeout — long-running tests may be interrupted

Result collection is asynchronous — requires polling or webhook integration for real-time updates

Screenshot and log sizes can be large — may cause MCP message size limits if not streamed

What makes it unique

Abstracts multiple test framework APIs (Appium, Selenium, XCUITest) into unified MCP tools, allowing Claude to execute tests without framework-specific knowledge. Implements result normalization layer that parses framework-specific output into structured data Claude can reason about.

vs alternatives

Simpler than managing multiple test framework SDKs separately — Claude sees a single 'execute test' tool that works across iOS, Android, and web, reducing cognitive load and enabling cross-platform test orchestration.

network condition simulation and performance testing via mcp

Medium confidence

Exposes BrowserStack's network throttling and condition simulation capabilities through MCP tools, allowing Claude to test app behavior under various network conditions (4G, 5G, WiFi, offline, latency injection). Implements configuration of network profiles and real-time condition changes during test execution. Collects performance metrics (load time, resource timing, network waterfall) for analysis.

Solves for

I want Claude to automatically test my app on slow networks and report performance degradationI need to simulate offline scenarios and verify graceful degradationI want Claude to identify performance bottlenecks by testing across different network conditions

Best for

Performance-focused QA teams testing app behavior under real-world network conditions

Mobile app developers optimizing for emerging markets with poor connectivity

CI/CD pipelines that include network resilience testing

Requires

BrowserStack device session with network simulation support

Test code that can measure performance metrics (e.g., Navigation Timing API for web)

MCP client with support for numeric/metric data types

Limitations

Network simulation is device-dependent — not all devices support all network profiles

Latency injection has ~50ms accuracy — not suitable for sub-millisecond timing tests

Network conditions cannot be changed mid-session on some devices — requires session restart

What makes it unique

Integrates BrowserStack's network simulation as first-class MCP tools rather than requiring manual device configuration. Allows Claude to reason about network conditions as test variables, automatically selecting appropriate profiles and interpreting performance metrics.

vs alternatives

Enables automated performance testing across network conditions without manual device setup — Claude can systematically test app behavior under 4G, 5G, WiFi, and offline scenarios, collecting metrics for regression detection.

screenshot and video capture with automated analysis

Medium confidence

Provides MCP tools for capturing screenshots and video recordings from BrowserStack device sessions, with optional automated visual analysis. Implements screenshot comparison for regression detection, OCR for text extraction from UI, and structured metadata about captured content. Supports both on-demand capture and continuous recording during test execution.

Solves for

I want Claude to capture screenshots during test execution and detect visual regressionsI need to extract text from app screenshots for assertion validationI want Claude to record video of test execution for debugging and documentation

Best for

Visual regression testing workflows where Claude compares screenshots

Accessibility testing where Claude extracts and validates UI text

Test documentation and debugging where video evidence is needed

Requires

Active BrowserStack device session

Storage backend for screenshots/videos (BrowserStack cloud or external S3)

Optional: OCR engine (Tesseract or cloud vision API) for text extraction

Limitations

Screenshot comparison requires baseline images — first run must be manually validated

OCR accuracy varies by text size and font — small UI text may be misrecognized

Video recording increases session resource usage — may impact test performance

What makes it unique

Combines screenshot capture with automated visual analysis (regression detection, OCR) as integrated MCP tools, allowing Claude to interpret visual test results without external image processing services. Implements baseline comparison logic that Claude can use for regression detection.

vs alternatives

Eliminates need for separate visual testing tools — Claude can capture, analyze, and compare screenshots in a single workflow, detecting visual regressions and extracting UI text without manual image processing.

test report generation and result aggregation

Medium confidence

Provides MCP tools for aggregating test results from multiple device sessions into structured reports, with support for different report formats (JSON, HTML, JUnit XML). Implements result filtering, sorting, and summarization (pass rate, failure categories, performance trends). Generates actionable insights from aggregated data, such as device-specific failure patterns or performance regressions.

Solves for

I want Claude to generate a comprehensive test report across all tested devicesI need to identify which devices have the most failures and whyI want Claude to detect performance regressions by comparing results across test runs

Best for

QA teams that need automated test reporting and analysis

CI/CD pipelines that require structured test result artifacts

Teams tracking test quality metrics over time

Requires

Completed test sessions with result data

MCP client with support for file/document output types

Optional: external storage for report archival

Limitations

Report generation requires all test sessions to be completed — cannot generate partial reports

Aggregation logic is limited to BrowserStack's result schema — custom metrics require external processing

HTML report generation may be slow for large result sets (1000+ test cases)

What makes it unique

Transforms raw BrowserStack test results into actionable reports with automated analysis (failure categorization, performance trends, device-specific patterns). Implements multi-format export (JSON, HTML, JUnit) allowing integration with CI/CD systems and test dashboards.

vs alternatives

Provides structured test analytics without requiring external reporting tools — Claude can generate comprehensive reports, identify failure patterns, and detect regressions directly from BrowserStack results.

mcp protocol transport and authentication management

Medium confidence

Implements the MCP server transport layer that handles Claude client connections, tool schema definition, and request/response serialization. Manages BrowserStack API authentication (API key/secret) securely, with support for credential rotation and environment variable injection. Implements error handling and response formatting that conforms to MCP specification, ensuring compatibility with Claude Desktop and other MCP clients.

Solves for

I want to securely connect Claude to BrowserStack without exposing API credentialsI need the MCP server to handle authentication and credential management automaticallyI want reliable request/response handling that works with Claude's MCP client

Best for

Teams deploying BrowserStack MCP server in production environments

Security-conscious organizations requiring credential isolation

Claude Desktop users integrating BrowserStack automation

Requires

Node.js 16+ with MCP server library

BrowserStack API credentials (key and secret)

Environment variable support or config file

Limitations

Credentials must be provided via environment variables or config file — no interactive credential entry

No built-in credential rotation — requires external secret management system

MCP protocol version is fixed — cannot negotiate protocol version with client

What makes it unique

Implements full MCP server stack with BrowserStack-specific authentication, handling credential injection, request routing, and response serialization. Provides secure credential management without requiring manual API key handling in Claude prompts.

vs alternatives

Eliminates need for custom MCP server implementation — BrowserStack credentials are managed securely by the server, not exposed to Claude, reducing security risk compared to passing API keys in prompts.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @browserstack/mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server32

@browserstack/mcp-server

BrowserStack's Official MCP Server

remote browser session orchestration via mcp protocoldevice capability enumeration and filteringsession state management and cleanupmulti-session parallel test execution coordination

4 shared capabilities

MCP Server46

Browserbase MCP Server

Run cloud browser sessions and web automation via Browserbase MCP.

cloud-hosted browser session creation and lifecycle managementtool registry and resource management through mcpmcp protocol transport abstraction with stdio and http support

3 shared capabilities

MCP Server24

onestep-puppeteer-mcp-server

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

browser-lifecycle-managementmcp-protocol-transport-and-tool-discovery

2 shared capabilities

MCP Server47

Puppeteer MCP Server

Automate browser interactions and take screenshots via Puppeteer MCP.

browser-session-management-via-mcp-context

1 shared capability

MCP Server21

Puppeteer

** - Browser automation and web scraping.

browser-context-and-session-management

1 shared capability

MCP Server43

mobile-mcp

Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)

multi-device-orchestration-and-discovery

1 shared capability

Best For

✓QA engineers building AI-assisted test automation workflows
✓DevOps teams integrating BrowserStack into Claude-based CI/CD pipelines
✓Mobile app developers using Claude as a testing copilot
✓Automated test orchestration systems using Claude as the control plane
✓CI/CD pipelines that need dynamic device allocation without manual intervention
✓Teams running long-running test suites with automatic resource cleanup
✓QA teams building intelligent test selection logic in Claude workflows
✓Mobile app developers who need AI-assisted device matrix planning

Known Limitations

⚠Requires active BrowserStack subscription with API credentials — free tier may have limited concurrent sessions
⚠MCP protocol overhead adds ~100-200ms per request compared to direct REST API calls
⚠Session management is stateless at MCP layer — requires external persistence for multi-step test workflows
⚠No built-in retry logic or circuit breaker for BrowserStack API failures — relies on client-side error handling
⚠Session timeout is controlled by BrowserStack server-side limits — MCP layer cannot extend beyond account tier limits
⚠No transaction semantics — if session creation succeeds but cleanup fails, orphaned sessions may accumulate

Requirements

BrowserStack account with valid API key and secretNode.js 16+ runtimeMCP-compatible client (Claude Desktop, or custom MCP client implementation)Network access to BrowserStack API endpoints (api.browserstack.com)BrowserStack API credentials with session management permissionsMCP client with tool-calling supportActive network connection to BrowserStack APIBrowserStack API key with read access to device catalog

Input / Output

Accepts: JSON configuration objects (device specs, OS version, browser type), Test commands and assertions, Session parameters (timeout, orientation, network conditions), Device configuration JSON (OS, browser, version, capabilities), Session parameters (timeout in seconds, project name, build ID), Session identifiers for status queries and termination, Filter criteria (OS, OS version, browser, browser version, device type), Capability queries (e.g., 'supports_5g', 'has_touch', 'supports_geolocation'), Pagination parameters (limit, offset), Test commands (Appium/Selenium/XCUITest code), Test parameters (timeout, assertions, expected behavior), Device session identifier, Network profile name (e.g., '4g', '5g', 'wifi', 'offline'), Custom latency/bandwidth parameters (milliseconds, Mbps), Capture type (screenshot, video, continuous recording), Optional: baseline image for regression comparison, Test result identifiers or session IDs, Report format (JSON, HTML, JUnit XML), Filter criteria (device, test status, date range), Optional: baseline results for regression comparison, MCP client requests (tool calls with parameters), BrowserStack API credentials (via environment or config)

Produces: Session identifiers and connection URLs, Device metadata (capabilities, screen resolution, OS version), Test execution logs and screenshots, Session status and performance metrics, Session creation response with session ID and connection details, Session status objects (state, duration, device info), Termination confirmation with cleanup status, Device objects with metadata (name, OS, browser, screen resolution, capabilities), Filtered device lists matching query criteria, Device capability matrices for cross-browser planning, Test execution status (passed, failed, error), Screenshots and video recordings, Device logs and performance metrics, Structured test results with failure reasons, Network condition configuration confirmation, Performance metrics (page load time, resource timing, network waterfall), Network condition status during test execution, Screenshot image data (PNG/JPEG), Video file (MP4), Regression comparison results (match percentage, diff regions), Extracted text from OCR analysis, Structured report (JSON, HTML, XML), Summary statistics (pass rate, failure count, average duration), Device-specific failure analysis, Performance metrics and trends, MCP protocol responses (tool results, errors), Structured error messages with diagnostic information

UnfragileRank

Adoption34%(30% weight)

Quality17%(25% weight)

Ecosystem52%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit @browserstack/mcp-server→

Repository Details

Package Details

npm

Registry

1.2.14

Version

2,546

Weekly Downloads

About

BrowserStack's Official MCP Server

Alternatives to @browserstack/mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @browserstack/mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

npm

Looking for something else?

Search →

Capabilities8 decomposed

browserstack device session orchestration via mcp protocol

Medium confidence

Solves for

Best for

QA engineers building AI-assisted test automation workflows

DevOps teams integrating BrowserStack into Claude-based CI/CD pipelines

Mobile app developers using Claude as a testing copilot

Requires

BrowserStack account with valid API key and secret

Node.js 16+ runtime

MCP-compatible client (Claude Desktop, or custom MCP client implementation)

Limitations

Requires active BrowserStack subscription with API credentials — free tier may have limited concurrent sessions

MCP protocol overhead adds ~100-200ms per request compared to direct REST API calls

Session management is stateless at MCP layer — requires external persistence for multi-step test workflows

What makes it unique

vs alternatives

real device session lifecycle management through mcp tools

Medium confidence

Solves for

Best for

Automated test orchestration systems using Claude as the control plane

CI/CD pipelines that need dynamic device allocation without manual intervention

Teams running long-running test suites with automatic resource cleanup

Requires

BrowserStack API credentials with session management permissions

MCP client with tool-calling support

Active network connection to BrowserStack API

Limitations

Session timeout is controlled by BrowserStack server-side limits — MCP layer cannot extend beyond account tier limits

No transaction semantics — if session creation succeeds but cleanup fails, orphaned sessions may accumulate

Concurrent session limits depend on BrowserStack subscription tier, not MCP server capacity

What makes it unique

vs alternatives

device capability querying and filtering via mcp

Medium confidence

Solves for

Best for

QA teams building intelligent test selection logic in Claude workflows

Mobile app developers who need AI-assisted device matrix planning

CI/CD systems that dynamically select test devices based on code changes

Requires

BrowserStack API key with read access to device catalog

MCP client with support for structured tool responses

Network access to BrowserStack API

Limitations

Device catalog is cached — new devices may not appear immediately after BrowserStack release

Capability filtering is limited to BrowserStack's predefined capability taxonomy — custom capabilities not supported

Large device inventory (1000+ devices) may cause slow response times if not paginated

What makes it unique

vs alternatives

test execution and result collection through mcp

Medium confidence

Solves for

Best for

AI-driven test automation systems where Claude interprets test results

Debugging workflows where Claude analyzes device-specific failures

Continuous testing pipelines that need intelligent test result analysis

Requires

Active BrowserStack device session

Test code compatible with BrowserStack's supported frameworks (Appium, Selenium, XCUITest)

MCP client with support for streaming responses

Limitations

Test execution timeout is limited by BrowserStack session timeout — long-running tests may be interrupted

Result collection is asynchronous — requires polling or webhook integration for real-time updates

Screenshot and log sizes can be large — may cause MCP message size limits if not streamed

What makes it unique

vs alternatives

network condition simulation and performance testing via mcp

Medium confidence

Solves for

Best for

Performance-focused QA teams testing app behavior under real-world network conditions

Mobile app developers optimizing for emerging markets with poor connectivity

CI/CD pipelines that include network resilience testing

Requires

BrowserStack device session with network simulation support

Test code that can measure performance metrics (e.g., Navigation Timing API for web)

MCP client with support for numeric/metric data types

Limitations

Network simulation is device-dependent — not all devices support all network profiles

Latency injection has ~50ms accuracy — not suitable for sub-millisecond timing tests

Network conditions cannot be changed mid-session on some devices — requires session restart

What makes it unique

vs alternatives

screenshot and video capture with automated analysis

Medium confidence

Solves for

Best for

Visual regression testing workflows where Claude compares screenshots

Accessibility testing where Claude extracts and validates UI text

Test documentation and debugging where video evidence is needed

Requires

Active BrowserStack device session

Storage backend for screenshots/videos (BrowserStack cloud or external S3)

Optional: OCR engine (Tesseract or cloud vision API) for text extraction

Limitations

Screenshot comparison requires baseline images — first run must be manually validated

OCR accuracy varies by text size and font — small UI text may be misrecognized

Video recording increases session resource usage — may impact test performance

What makes it unique

vs alternatives

test report generation and result aggregation

Medium confidence

Solves for

Best for

QA teams that need automated test reporting and analysis

CI/CD pipelines that require structured test result artifacts

Teams tracking test quality metrics over time

Requires

Completed test sessions with result data

MCP client with support for file/document output types

Optional: external storage for report archival

Limitations

Report generation requires all test sessions to be completed — cannot generate partial reports

Aggregation logic is limited to BrowserStack's result schema — custom metrics require external processing

HTML report generation may be slow for large result sets (1000+ test cases)

What makes it unique

vs alternatives

mcp protocol transport and authentication management

Medium confidence

Solves for

Best for

Teams deploying BrowserStack MCP server in production environments

Security-conscious organizations requiring credential isolation

Claude Desktop users integrating BrowserStack automation

Requires

Node.js 16+ with MCP server library

BrowserStack API credentials (key and secret)

Environment variable support or config file

Limitations

Credentials must be provided via environment variables or config file — no interactive credential entry

No built-in credential rotation — requires external secret management system

MCP protocol version is fixed — cannot negotiate protocol version with client

What makes it unique

vs alternatives

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @browserstack/mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@browserstack/mcp-server

Capabilities8 decomposed

browserstack device session orchestration via mcp protocol

real device session lifecycle management through mcp tools

device capability querying and filtering via mcp

test execution and result collection through mcp

network condition simulation and performance testing via mcp

screenshot and video capture with automated analysis

test report generation and result aggregation

mcp protocol transport and authentication management

Related Artifactssharing capabilities

@browserstack/mcp-server

Browserbase MCP Server

onestep-puppeteer-mcp-server

Puppeteer MCP Server

Puppeteer

mobile-mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @browserstack/mcp-server

Are you the builder of @browserstack/mcp-server?

Get the weekly brief

Data Sources

@browserstack/mcp-server

Capabilities8 decomposed

browserstack device session orchestration via mcp protocol

real device session lifecycle management through mcp tools

device capability querying and filtering via mcp

test execution and result collection through mcp

network condition simulation and performance testing via mcp

screenshot and video capture with automated analysis

test report generation and result aggregation

mcp protocol transport and authentication management

Related Artifactssharing capabilities

@browserstack/mcp-server

Browserbase MCP Server

onestep-puppeteer-mcp-server

Puppeteer MCP Server

Puppeteer

mobile-mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @browserstack/mcp-server

Are you the builder of @browserstack/mcp-server?

Get the weekly brief

Data Sources