BrowserStack MCP

Created By
browserstacka year ago
Overview

What is BrowserStack MCP?

BrowserStack MCP is a server that enables developers and testers to perform manual and automated testing on real devices and browsers through a unified platform.

How to use BrowserStack MCP?

To use BrowserStack MCP, create a BrowserStack account, install the MCP Server, and configure it with your username and access key. You can then run commands to test your applications on various devices and browsers.

Key features of BrowserStack MCP?

  • Manual testing on real devices and browsers.
  • Automated testing support for frameworks like Playwright and Selenium.
  • Real-time debugging and performance profiling.
  • Accessibility testing to ensure compliance with WCAG and ADA standards.

Use cases of BrowserStack MCP?

  1. Testing mobile applications on actual devices.
  2. Running automated test suites in CI/CD pipelines.
  3. Debugging web applications across different browsers.
  4. Ensuring accessibility compliance for web applications.

FAQ from BrowserStack MCP?

  • Is BrowserStack MCP free to use?

No, BrowserStack MCP requires a paid account, but there are free plans available for open-source projects.

  • What types of testing does BrowserStack MCP support?

It supports manual testing, automated testing, and accessibility testing across various devices and browsers.

  • How do I report issues or get support?

You can report issues on the GitHub repository or contact the support team through the BrowserStack website.

Server Config

{
  "mcpServers": {
    "browserstack": {
      "command": "npx",
      "args": [
        "-y",
        "@browserstack/mcp-server@latest"
      ],
      "env": {
        "BROWSERSTACK_USERNAME": "<username>",
        "BROWSERSTACK_ACCESS_KEY": "<access_key>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
browserstack
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago