Runs manual and automated tests on BrowserStack's real devices and browsers, plus accessibility, test management and load tests.

How it works

Foe: Bug Slime, a defect in your code.

Foes

  • Bug Slime

Party · Context

  • SentinelYour agent100/100
  1. Bug Slime

    The Bug Slime blocks the way.

    What really happensIt stands for a defect in your code.

    Sentinel: Context 100/100.

  2. Regress

    The Bug Slime uses Regress.

    What really happensA fix in one place breaks something that used to work.

    Sentinel takes 8. Sentinel: Context 92/100.

  3. BrowserStack MCP Server

    A portal opens to BrowserStack's device hall.

    What really happensAdd the local server with your BrowserStack username and access key. It can reach apps on localhost or behind your firewall.

    Bug Slime takes 29.

  4. BrowserStack MCP Server

    The hero asks the hall's keeper for the right tool.

    What really happensFive core tools list products, search capabilities in plain language, and describe one before running it.

    Bug Slime takes 13.

  5. Regress

    The Bug Slime uses Regress.

    Sentinel takes 8. Sentinel: Context 84/100.

  6. BrowserStack MCP Server

    The app is tested on a real device far away.

    What really happensinvokeCapability runs the chosen workflow, such as a live session, Playwright or Selenium tests, or an accessibility scan.

    Bug Slime takes 32.

  7. BrowserStack MCP Server

    The slime is found on a phone you never held.

    What really happensResults come back to the agent. Any change to BrowserStack data, such as test cases, needs your approval first.

    Bug Slime takes 26. Bug Slime falls.

  8. Victory

    The Bug Slime falls.

Learn this spell

Claude Code

claude mcp add --scope user browserstack -e BROWSERSTACK_USERNAME=YOUR_USERNAME -e BROWSERSTACK_ACCESS_KEY=YOUR_ACCESS_KEY -- npx -y @browserstack/mcp-server@latest

Codex

codex mcp add browserstack --env BROWSERSTACK_USERNAME=YOUR_USERNAME --env BROWSERSTACK_ACCESS_KEY=YOUR_ACCESS_KEY -- npx -y @browserstack/mcp-server@latest

Notes

Needs a BrowserStack account and plan; open-source projects can get a free plan. The local server needs Node 20.9+ and can test localhost and staging. A hosted remote server at https://mcp.browserstack.com/mcp signs in with OAuth but cannot reach localhost. Five core tools search a catalog and run the capability you need; changes to data need your approval. File and app uploads need MCP_UPLOAD_BASE_DIR.

This spell has no recorded sessions in the curator's logs. Tried it? Send a spell report.