Can my AI automatically read the logs of a failed Selenium test?

Yes. When you ask it to investigate a recently failed build, the agent can use `get_build` to find the failed session, and then automatically call `get_session_logs`. It will download the raw textual execution steps directly into the chat and summarize why the UI test failed.

Is there a risk that my AI alters my testing scripts or repository code?

No, this MCP server integrates exclusively with BrowserStack Automate API. It can read statuses, logs, and configurations, and can delete hung sessions or builds, but it has no connection to your actual codebase or git repository.

How can I resolve concurrent session limits preventing my pipeline from advancing?

You can ask your agent to `get_plan` to inspect your parallel boundaries and verify if you are queuing. Then, the agent can look up stalled items via `list_builds` and execute `delete_session` or `delete_build` to manually unblock stuck processes.

BrowserStack MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: BrowserStack
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to BrowserStack through Vinkius, pass the Edge URL in the `mcps` parameter and every BrowserStack tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="BrowserStack Specialist",
    goal="Help users interact with BrowserStack effectively",
    backstory=(
        "You are an expert at leveraging BrowserStack tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in BrowserStack "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About BrowserStack MCP Server

Connect your BrowserStack Automate account to any AI agent and take full control of your automated cross-browser testing pipeline through natural conversation.

When paired with CrewAI, BrowserStack becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call BrowserStack tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Project Management — List all test projects and drill down into specific project details
Build Tracking — Surface your recent automation builds, their statuses (running, failed, passed), and duration
Session Deep Dive — Retrieve the granular executions of a specific test session, including OS and browser stats
Log Extraction — Automatically dump and analyze the raw Selenium/Appium logs of a failed session
Quota & Plan — View your current plan's parallel session usage and testing queue length
Environment Specs — List all supported OS/browser combinations required to configure your capabilities

The BrowserStack MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect BrowserStack to CrewAI via MCP

Follow these steps to integrate the BrowserStack MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from BrowserStack

Why Use CrewAI with the BrowserStack MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with BrowserStack through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

BrowserStack + CrewAI Use Cases

Practical scenarios where CrewAI combined with the BrowserStack MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries BrowserStack for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries BrowserStack, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain BrowserStack tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries BrowserStack against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

BrowserStack MCP Tools for CrewAI (10)

These 10 tools become available when you connect BrowserStack to CrewAI via MCP:

delete_build

json`. Delete a BrowserStack build by ID

delete_session

json`. Delete a BrowserStack session by ID

get_build

json`. Returns session details, OS/browser combos, results, and logs. Get all sessions within a BrowserStack automation build

get_plan

json`, including parallel sessions allowed, team parallel sessions used, queued sessions, and plan name. Essential for managing execution concurrency. Get current BrowserStack plan details and parallel session usage

get_project

json`. This includes name, group ID, and recent builds associated with the project. Get full details of a BrowserStack project including linked builds

get_session

json`. Includes name, OS, browser, status, reason, duration, video URL, and log URLs. Get full details of a specific BrowserStack session

get_session_logs

Useful for debugging failed test steps. Get text execution logs of a BrowserStack session

list_browsers

json`. Returns OS names/versions, browser names/versions required for configuring automation desired capabilities. List all supported OS/browser combinations on BrowserStack

list_builds

json`. Returns build names, IDs, statuses (running/done/timeout/failed), durations, and session counts. Useful for tracking test suite execution. List recent builds on BrowserStack Automate

list_projects

json`. Returns project names, IDs, and build counts. Used to organize automation runs. List all projects on BrowserStack Automate

Example Prompts for BrowserStack in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with BrowserStack immediately.

"List my recent automation builds and summarize their outcomes."

"Fetch the logs for the failed session in build e4da3b."

"Check how many parallel sessions our current plan allows."

Troubleshooting BrowserStack MCP Server with CrewAI

Common issues when connecting BrowserStack to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

BrowserStack + CrewAI FAQ

Common questions about integrating BrowserStack MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.