BrowserStack MCP server

Created By
browserstacka year ago
BrowserStack MCP Server allows you to use our cutting-edge Test Platform directly from your favourite AI tools. Enable every developer and tester in your team, whether they are testing manually, starting their automation journey, or scaling test automation.
Overview

What is BrowserStack MCP Server?

BrowserStack MCP Server is a platform that allows developers and testers to utilize BrowserStack's cutting-edge Test Platform directly from their favorite AI tools, facilitating both manual and automated testing.

How to use BrowserStack MCP Server?

To use the BrowserStack MCP Server, create a BrowserStack account, install the MCP Server, and configure it with your username and access key. You can then run tests on real devices and browsers using simple commands.

Key features of BrowserStack MCP Server?

  • Supports manual app and web testing on real devices and browsers.
  • Enables automated testing with popular frameworks like Playwright and Selenium.
  • Provides advanced app profiling and debugging features.
  • Accessibility testing to ensure compliance with WCAG and ADA standards.

Use cases of BrowserStack MCP Server?

  1. Testing mobile applications on real devices for performance and debugging.
  2. Running automated test suites in CI/CD pipelines.
  3. Conducting accessibility audits on websites.

FAQ from BrowserStack MCP Server?

  • Can I test my app on real devices?

Yes! BrowserStack MCP Server allows you to test your app on a wide range of real devices.

  • Is there a free plan available?

Yes! BrowserStack offers a free plan for open-source projects.

  • What frameworks are supported for automated testing?

BrowserStack MCP Server supports frameworks like Playwright, Selenium, and Jest.

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)

20 hours ago
Gpt Scrambler

2 days ago