BrowserStack MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is BrowserStack MCP Server?

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

How to use BrowserStack MCP Server?

To use the BrowserStack MCP Server, you need to create a BrowserStack account, install the MCP Server, and configure it with your credentials. You can then run tests using various prompts for manual and automated testing.

Key features of BrowserStack MCP Server?

  • Access to a wide range of real devices and browsers for testing.
  • Support for manual app and web testing.
  • Integration with popular testing frameworks like Playwright and Selenium.
  • Real-time debugging and performance profiling.
  • Accessibility testing tools to ensure compliance with standards.

Use cases of BrowserStack MCP Server?

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

FAQ from BrowserStack MCP Server?

  • Can I test my applications on real devices?

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

  • Is there a free plan available?

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

  • What testing frameworks are supported?

The MCP Server supports various frameworks including Playwright, Selenium, and Jest.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
AGPL-3.0 license

Recommend Servers

View All
Gpt Scrambler

2 days ago
Crevio

a day ago
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