Can I see the exact console errors from a failed browser test through my agent?

Yes. Use the `get_session_details` tool with a specific Session ID. Your agent will retrieve full metadata including console logs, network configurations, and execution artifacts, helping you identify the root cause of the failure instantly.

How do I retrieve the video recording of a specific test execution?

Ask your agent to `get_session_video` for a targeted Session ID. Your agent will return the absolute MP4 URL to stream or download the complete browser session recording, which is essential for debugging flakey UI bugs.

Can my agent check if our secure localhost tunnel is active?

Absolutely. Use the `list_active_tunnels` tool to identify dedicated private connection endpoints. Your agent will report which TestMu AI tunnels are currently running, ensuring you can test local environments from the cloud.

TestMu AI (formerly LambdaTest) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: TestMu AI (formerly LambdaTest)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to TestMu AI (formerly LambdaTest) through Vinkius, pass the Edge URL in the `mcps` parameter and every TestMu AI (formerly LambdaTest) 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="TestMu AI (formerly LambdaTest) Specialist",
    goal="Help users interact with TestMu AI (formerly LambdaTest) effectively",
    backstory=(
        "You are an expert at leveraging TestMu AI (formerly LambdaTest) 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 TestMu AI (formerly LambdaTest) "
        "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 TestMu AI (formerly LambdaTest) MCP Server

Connect your TestMu AI (formerly LambdaTest) account to any AI agent and take full control of your cross-browser testing and automation orchestration through natural conversation.

When paired with CrewAI, TestMu AI (formerly LambdaTest) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TestMu AI (formerly LambdaTest) 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

Build Orchestration — List all test automation builds and retrieve high-level aggregated telemetry for Selenium, Playwright, or Cypress suites directly from your agent
Session Inspection — Deep-dive into individual browser test sessions to extract console errors, network configurations, and exact metadata required for rapid debugging
Visual Artifacts — Fetch absolute URLs for bug screenshots and full video recordings of browser executions to reproduce flakey UI issues instantly
Precision Logging — Extract command-level logs including W3C WebDriver protocols or Playwright RPC calls with precise execution timestamps
Tunnel & Platform Audit — Monitor active secure tunnels for localhost testing and query the grid for supported macOS, Windows, iOS, and Android capabilities
Environment Mapping — Filter and retrieve all child test sessions nested under specific CI/CD builds to isolate and analyze deployment regressions

The TestMu AI (formerly LambdaTest) 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 TestMu AI (formerly LambdaTest) to CrewAI via MCP

Follow these steps to integrate the TestMu AI (formerly LambdaTest) 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 TestMu AI (formerly LambdaTest)

Why Use CrewAI with the TestMu AI (formerly LambdaTest) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with TestMu AI (formerly LambdaTest) 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

TestMu AI (formerly LambdaTest) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the TestMu AI (formerly LambdaTest) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries TestMu AI (formerly LambdaTest) 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 TestMu AI (formerly LambdaTest), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain TestMu AI (formerly LambdaTest) 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 TestMu AI (formerly LambdaTest) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

TestMu AI (formerly LambdaTest) MCP Tools for CrewAI (10)

These 10 tools become available when you connect TestMu AI (formerly LambdaTest) to CrewAI via MCP:

get_build

Get exact telemetry for a specific LambdaTest build

get_build_sessions

Extract all explicit test sessions associated with a Build

get_screenshots

saveScreenshot()` or failure-hook logic within the LambdaTest grid. Fetch visual bug screenshots captured during a test session

get_session

Identifies explicit console errors, network configuration, and URL artifacts necessary to debug why a specific UI interaction failed. Get deep context for a specific automated test session

get_session_logs

Extract precise Selenium/Appium command logs for a test

get_video

Retrieve the full video recording URL for a test execution

list_builds

Groups thousands of executed Selenium, Cypress, Playwright, or Appium browser tests into their respective parent CI/CD builds. List all test automation builds on LambdaTest Cloud

list_platforms

Returns exactly which combinations of macOS, Windows, iOS, and Android versions are actively available in the testing grid. List all supported OS/browser capabilities available

list_sessions

Provides OS, Browser version, execution duration, and final completion status of the Selenium/Playwright scripts. List recent automated test sessions executed on LambdaTest

list_tunnels

List all active secure Tunnels (UnderTest tunnels)

Example Prompts for TestMu AI (formerly LambdaTest) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with TestMu AI (formerly LambdaTest) immediately.

"List the last 5 automation builds in my TestMu AI account"

"Show me the logs and screenshots for session ID 'abc-123-xyz'"

"Which OS and browser versions are currently supported in the grid?"

Troubleshooting TestMu AI (formerly LambdaTest) MCP Server with CrewAI

Common issues when connecting TestMu AI (formerly LambdaTest) 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.

TestMu AI (formerly LambdaTest) + CrewAI FAQ

Common questions about integrating TestMu AI (formerly LambdaTest) 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.