BrowserStack MCP Server

Created By
browserstacka year ago
BrowserStack's Official MCP Server
Overview

what is BrowserStack MCP Server?

BrowserStack MCP Server is an official tool that integrates BrowserStack's Test Platform into your development workflow, allowing for efficient testing and debugging of applications across real devices and browsers.

how to use BrowserStack MCP Server?

To use the MCP Server, install it via npm and configure it with your BrowserStack credentials. You can then run tests and debug applications using prompts in various AI clients like Github Copilot and Cursor.

key features of BrowserStack MCP Server?

  • Test mobile apps on real devices in the cloud.
  • Perform manual web testing across different browsers.
  • Run automated tests using frameworks like Playwright and Selenium.
  • Access a wide range of devices and browsers for comprehensive testing.

use cases of BrowserStack MCP Server?

  1. Debugging mobile app crashes in real-time.
  2. Testing websites on various browsers without deployment.
  3. Running automated test suites for continuous integration.

FAQ from BrowserStack MCP Server?

  • Is BrowserStack MCP Server free to use?

No, it requires a BrowserStack account with a subscription plan.

  • What types of tests can I run?

You can run manual, automated, and accessibility tests on both mobile apps and websites.

  • How do I get support?

You can check the documentation, open an issue on GitHub, or contact the support team for assistance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
browserstack
Star
59
Language
TypeScript
License
AGPL-3.0 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)

20 hours ago
Gpt Scrambler

2 days ago