World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Agentic AI quality engineering: run, debug and triage tests on real browsers and devices
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
5/5 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (mcp.lambdatest.com) · ✓ Befehle geprüft am 13. Nov. 2026
Zuerst: Welche KI nutzt du?
Wähle deine App, dann erscheinen die Schritte unten.
Klappt mit Claude · etwa 2 Min.
Kein Schlüssel, nichts zu installieren · Einmal auf claude.ai oder in der Desktop-App einrichten, dann im Chat nutzen · kostenlose Konten können 1 hinzufügen · bei Team/Enterprise fügt ein Owner ihn hinzu
CustomizeConnectors
Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue
TestMu AI (formerly LambdaTest)https://mcp.lambdatest.com/mcpKlicke auf der von Claude erkannten Anmelde-Seite auf Continue · wähle bei Authentication, was der Anbieter angibt (Sign in now, Sign in when needed oder No sign in), dann Add
+ConnectorsTestMu AI (formerly LambdaTest)
Nutze TestMu AI (formerly LambdaTest) und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude sagt, dass es TestMu AI (formerly LambdaTest) nutzt, oder ein Werkzeug von TestMu AI (formerly LambdaTest) in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit ChatGPT je nach Tarif
Volles MCP: ChatGPT Business, Enterprise oder Edu im Web · Pro: verbindet mit Lese-/Abrufrechten, Werkzeuge, die Daten ändern, gehen evtl. nicht · Plus: in der Doku nicht bestätigt; siehst du auf der Plugins-Seite eine Option für eigene MCP-Server, kannst du es versuchen · nur Web
Plugins+Add custom MCP server
Namen eingeben, Adresse unter Connection einfügen, Risikohinweis abhaken und Create as a plugin klicken
TestMu AI (formerly LambdaTest)https://mcp.lambdatest.com/mcpNeuen Chat öffnen und vor dem Tippen TestMu AI (formerly LambdaTest) aus deinen Plugins wählen
Nutze TestMu AI (formerly LambdaTest) und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn ChatGPT sagt, dass es TestMu AI (formerly LambdaTest) nutzt, oder ein Werkzeug von TestMu AI (formerly LambdaTest) in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von OpenAI abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit Claude Code · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen
claude mcp add --transport http --scope user lambdatest https://mcp.lambdatest.com/mcpTestMu AI (formerly LambdaTest) sollte in der Liste als verbunden erscheinen
Nutze TestMu AI (formerly LambdaTest) und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Claude Code sagt, dass es TestMu AI (formerly LambdaTest) nutzt, oder ein Werkzeug von TestMu AI (formerly LambdaTest) in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit Cursor · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
Nutze TestMu AI (formerly LambdaTest) und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn Cursor sagt, dass es TestMu AI (formerly LambdaTest) nutzt, oder ein Werkzeug von TestMu AI (formerly LambdaTest) in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von Cursor abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Klappt mit VS Code · etwa 2 Min.
Kein Schlüssel, nichts zu installieren
VS Code fragt nach einer Bestätigung; klicke Install
Nutze TestMu AI (formerly LambdaTest) und sag mir, was du für mich tun kannst; zeig mir dann eine Sache✓ Wenn VS Code sagt, dass es TestMu AI (formerly LambdaTest) nutzt, oder ein Werkzeug von TestMu AI (formerly LambdaTest) in der Antwort zeigt, bist du verbunden
Menünamen am 11. Nov. 2026 mit der Hilfe von VS Code abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen
Andere Apps mit MCP, etwa Windsurf, Zed oder Gemini CLI, fügen Server unterschiedlich hinzu. Sieh in der App-Liste nach
Adresse für Apps, die über das Web verbinden
https://mcp.lambdatest.com/mcpJSON-Einstellungen stehen unten unter „Für Entwickler“
Claude Code
claude mcp add --transport http --scope user lambdatest https://mcp.lambdatest.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lambdatest": {
"url": "https://mcp.lambdatest.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"lambdatest": {
"type": "http",
"url": "https://mcp.lambdatest.com/mcp"
}
}
}Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.
Verbinden sich über das Internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 12. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
upload_appUploads an app to TestMu AI for mobile testing and displays upload status.
generateHyperExecuteYAMLGenerates a HyperExecute YAML configuration for running tests on TestMu AI's HyperExecute platform. REQUIRED fields: project (language, framework) and testing (testDiscovery.command, testRunnerCommand) All other fields are OPTIONAL. Supports multiple languages and frameworks: - J
answerHyperExecuteQueryAnswers questions about HyperExecute features, configuration, usage, troubleshooting, and best practices by searching through documentation.
getHyperExecuteJobInfoFetches and displays information about a HyperExecute job including status, test results, and progress.
getHyperExecuteJobSessionsFetches and displays session information for a HyperExecute job.
getAccessibilityReportRuns an accessibility scan on the given URLs and returns the issues found. Pass urls to start a scan, or testId to re-read a scan that already ran; exactly one of the two. Results arrive in issueDetails: allIssues (most-severe-first, one page at a time), rules (name and reference
analyzeAppViaTunnelAnalyzes a locally running app for accessibility via TestMu AI tunnel.
buildLocalAppForAnalysisReturns step-by-step instructions to build and serve a local web app and open a TestMu AI tunnel to it, so its accessibility can then be scanned with analyzeAppViaTunnel. It does not build, run or scan anything itself, and never includes the access key.
getAutomationTestDetailsFetches detailed information about an automation test by ID
getAutomationTestCommandLogsFetches command logs for a specific automation test
getAutomationTestNetworkLogsFetches network logs for a specific automation test
getAutomationTestBrowserConsoleLogsFetches Browser Console logs for a specific automation test. Note: Not available for mobile app automation tests.
getAutomationTestSeleniumLogsFetches Selenium logs (web), Appium logs (mobile/Appium), or instrumentation logs (mobile/XCUI/Espresso) for a specific automation test. Automatically detects XCUI and Espresso tests and fetches the correct log type.
automationQueryRead-only query of TestMu AI automation resources: list builds, get one build, list the sessions in a build, fetch test details, and retrieve test logs (command, network, console, selenium, instrumentation). Every combination works on platform "web" or "app": build list or get, s
updateBuildRenames a TestMu AI web automation build. Overwrites the current build name.
stopBuildStops every running test in a TestMu AI web automation build. Running sessions end immediately.
deleteBuildPermanently deletes a TestMu AI web automation build and its test results. Cannot be undone.
triggerSuiteRunTriggers a phone call test run for a specific suite. This will initiate phone calls for all scenarios configured in the suite.
getSuiteOverviewGets comprehensive suite overview for a project including run counts, latest status, scores, schedule information, and active calls.
getSupportedPlatformsLists the OS, browser and device combinations TestMu AI supports, to find valid os, browser and version values for a test configuration. With no filters it returns a compact summary: each desktop OS with its browsers (version count, newest and oldest) and resolutions, and each mo
listTunnelsRetrieve all active TestMu AI tunnel connections for the account. Useful for checking which tunnels are running before starting a new one or debugging local testing connectivity.
stopTunnelTerminate a specific active tunnel connection by tunnel ID. Use this to clean up tunnels that are no longer needed.
deleteSessionPermanently delete a specific automation test session from TestMu AI by session ID.
updateSessionUpdate the name or pass/fail status of a test session. Use status_ind to mark tests as passed, failed, error, or skipped from your test framework.
stopSessionStop an active running test session on TestMu AI.
getSessionScreenshotsRetrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessio
getSessionVideoRetrieve the video recording URL for a completed test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
getSessionV2CommandLogsRetrieve v2 command execution logs for a test session. Returns structured JSON with enhanced detail compared to v1 logs. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of
getSessionV2SeleniumLogsRetrieve v2 Selenium/WebDriver grid request and response logs for a test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
postSessionExceptionsUpload exception/error logs from the client machine for a test session, by session ID. Use this to attach assertion failures or unexpected errors to a session. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exception
postTestExceptionsUpload exception logs for a specific test (by test ID) rather than by session ID. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exceptions uploaded this way after the test ended.
getLiveSessionLogsRetrieve the request and response log of a test session, while it runs or after it ends. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
getOrgConcurrencyRetrieve the current concurrency usage and limits for the organization on web automation (Selenium/Cypress).
getAnalyticsDataSummarises web automation test results in a date range: total tests, passed, failed, completed without a pass/fail mark, pass rate (passed over all tests, as the Insights page shows it), pass rate over tests marked passed or failed, average duration and distinct builds, grouped b
getFlakyTestsLists tests that the insights engine marks as flaky (passing and failing intermittently) in a date range, with each test's flake rate, build and environment. Returns only flaky tests, plus how many tests were scanned. Flakiness is only computed for about the last 7 days of tests;
getTestTrendsDaily trend of web automation test results in a date range: for each day, total tests, passed, failed, completed without a pass/fail mark, pass rate (passed over all tests), pass rate over tests marked passed or failed, and average duration.
getAnalyticsErrorsSummarises failed and errored web automation tests in a date range: counts by failure category and by status, and the failing tests themselves with build and environment. Failure categories exist only for about the last 7 days of tests; older failures are counted as uncategorised
deletePrerunFileDelete an uploaded prerun file by stored TestMu AI file path.
deleteUserFileDelete an uploaded user file by stored TestMu AI file path.
listUploadedAppsRetrieve all apps uploaded to TestMu AI for mobile testing. Use type=android/ios for real devices, emulator/simulator for virtual devices.
deleteUploadedAppsDelete one or more uploaded apps from TestMu AI by their app IDs.
uploadAppVirtualDeviceUpload an app (APK for emulator, IPA for simulator) to TestMu AI for virtual device (emulator/simulator) testing.
listDevicesForTestingLists the real devices available on TestMu AI for mobile app testing, 50 per page by default. Filter by region, OS, device name or OS version, and page with limit and offset. The text gives the total that matched.
getMobileCapabilityGeneratorRetrieve capability generation data for mobile automation test configuration.
listMobileBuildsLists mobile app automation builds, newest first, 10 per page by default. Page with limit and offset; the result gives the total the API reports. The API returns only builds from the last 90 days, so total can be higher than the builds you can page through.
listMobileSessionsLists mobile app automation sessions (tests), newest first, 10 per page by default, with their video, screenshot and log links. Page with limit and offset, or filter by buildId or status; the result gives the total the API reports.
getMobileConcurrencyRetrieve the current concurrency usage and limits for mobile automation (real device testing).
checkAppProcessingStatusCheck whether an uploaded app has been processed and is ready for features like image injection, network logs, and screenshot unblock on real devices. The TestMu AI API has no read-only status call: this one starts or refreshes the processing for the requested features, so the ap
tm_list_projectsList all Test Manager projects the authenticated user is allowed to see. Supports keyword search and pagination.
tm_get_test_casesFind test cases in a project by filters (folder, priority, automation status, type, tags) and/or search (matches test case ID like TC-123, or title; minimum 3 characters) — returns summaries. Filters combine (AND). Pass case_id instead to get one case's full detail (steps, BDD sc
tm_list_foldersGet a folder tree. Test Manager keeps three folder types: Test Cases and Test Runs folders (per project — pass project_id) and Modules folders (organization-level, since modules are shared across projects — no project_id needed). Pick with the tree parameter (default: test-cases)
tm_list_modulesList the organization's reusable step Modules (modules are org-level, shared across projects — the same list as the Modules page). Supports name search and pagination. Reference a module by id when creating or editing a test case to include its steps (the Module itself is never c
tm_list_configurationsList saved run Configurations (reusable platform / browser / OS / device setups). To apply one to a run, pass the configuration's TOP-LEVEL id to tm_create_test_run or tm_update_test_run as configuration_id (NOT the nested environments[].environment_id). Pass run_type to see only
tm_get_test_runsPass run_id to get one test run's detail plus its result summary (instance counts by status — passed / failed / skipped / not started / in progress — and pass rate). Otherwise pass project_id to list runs with optional filters. Every returned run carries run_type ("kaneai" or "ma
tm_get_milestonePass milestone_id to get one milestone's detail and live completion progress. Otherwise pass project_id to list the project's milestones.
tm_get_coverage_summaryTest coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to
tm_create_projectCreate a new Test Manager project. Project & Org Instructions (Memory Layer) stay managed in the UI. Deleting projects is not available through this connection.
tm_update_projectUpdate a project's name, description or tags (fields are merged — only what you pass changes). Project & Org Instructions stay managed in the UI.
tm_create_folderCreate a folder — in a project's Test Cases tree (default) or Test Runs tree (pass project_id), or in the organization-level Modules tree (no project_id needed; module folders are shared across projects). Optionally nest it under an existing parent folder to build folder trees. D
tm_update_folderRename a folder, change its description, or move it under a different parent folder. Works on all three folder types: per-project Test Cases (default) and Test Runs trees, and the organization-level Modules tree. Moves of test-cases/test-runs folders require project_id; module fo
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 15. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto LambdaTest bestätigt, dem das Repo gehört
Code zuletzt geändert: vor 3 Tagen
Nutzt MIT
Antwort in 738 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 60 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.
Noch keine Bewertungen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 5 von 5 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt vor 3 Tagen geändert, und die neueste Version (1.0.7) kam vor 25 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL und funktioniert daher auch in Apps mit Remote-MCP, etwa ChatGPT im Web (volles MCP ab Business; Pro nur lesend).
In derselben Kategorie: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Run, debug, and triage tests using natural language, directly from your IDE.
The TestMu AI MCP Server connects any MCP-compatible client to the TestMu AI (Formerly LambdaTest) platform — so you can orchestrate test runs, debug failures, analyze visual regressions, and run accessibility audits without leaving your editor or switching between dashboards.
This repository is the setup guide and reference for the hosted MCP server. The server itself runs as a managed service at
https://mcp.lambdatest.com/mcp— there is nothing to install or self-host.
| Tool | What it does |
|---|---|
| HyperExecute | AI-native test orchestration. Generates HyperExecute YAML and test runner commands, triggers jobs, and reports status — no manual YAML authoring. |
| Automation | Triages test failures by pulling execution details, command logs, network logs, and console errors into one place for root-cause analysis. |
| SmartUI | Explains visual regressions in plain English — pixel, layout, DOM, and perceptual differences, summarized rather than eyeballed. |
| Accessibility | Runs WCAG and a11y audits against hosted URLs or local React apps, returning violations with remediation guidance. |
| Test Manager | Covers the test management lifecycle — AI test case generation through to bulk result recording. |
Authentication is handled over OAuth. On first connection, your client opens a browser window to authorize against testmuai.com; no API keys need to be stored in config files.
The server endpoint is:
https://mcp.lambdatest.com/mcp
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
{
"mcpServers": { "testmu-ai": { "url": "https://mcp.lambdatest.com/mcp" } } }
claude mcp add --transport http testmu-ai https://mcp.lambdatest.com/mcp
Or install from the TestMu AI plugin marketplace (Claude Code v2.1.292 or later):
claude plugin install kane-cli --marketplace LambdaTest/mcp-server-guide
claude plugin install rook --marketplace LambdaTest/mcp-server-guide claude plugin install testmu-ai --marketplace LambdaTest/mcp-server-guide
| Plugin | What you get |
|---|---|
kane-cli | Kane CLI skill for browser automation, mobile app testing and AI test authoring |
rook | Rook inside Claude Code for testing the AI agents you build |
testmu-ai | This MCP server plus the Kane CLI and Rook CLI skills |
On older versions, add the marketplace first with claude plugin marketplace add LambdaTest/mcp-server-guide, then run claude plugin install kane-cli@testmu-ai. Inside a Claude Code session, use /plugin marketplace add LambdaTest/mcp-server-guide and /plugin install kane-cli@testmu-ai.
Add to your MCP configuration:
{
"servers": { "testmu-ai": { "type": "http", "url": "https://mcp.lambdatest.com/mcp" } } }
Open the Cline panel, click the MCP Servers icon, then Configure > Remote Servers:
Or click Configure MCP Servers in Cline to open cline_mcp_settings.json and add:
{
"mcpServers": { "testmu-ai": { "type": "streamableHttp", "url": "https://mcp.lambdatest.com/mcp" } } }
There is nothing to clone or install. Click Authenticate when it appears to complete the OAuth sign-in.
Add to ~/.config/opencode/opencode.json (global) or opencode.json in your project root:
{
"$schema": "https://opencode.ai/config.json", "mcp": { "testmu-ai": { "type": "remote", "url": "https://mcp.lambdatest.com/mcp", "oauth": {} } } }
Then run opencode mcp auth testmu-ai to sign in through your browser. opencode mcp list should show testmu-ai connected.
Add to ~/.config/kilo/kilo.jsonc:
{
"$schema": "https://app.kilo.ai/config.json", "mcp": { "testmu-ai": { "type": "remote", "url": "https://mcp.lambdatest.com/mcp" } } }
Then open Kilo Settings > Agent Behaviour > MCP Servers and click Sign in next to testmu-ai.
Clients that don't yet support remote HTTP transport can connect through mcp-remote:
{
"mcpServers": { "testmu-ai": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.lambdatest.com/mcp"] } } }
Cursor · Claude Code · Claude Desktop · GitHub Copilot · OpenAI Codex · Windsurf · Cline · Continue · Zed AI · JetBrains AI Assistant · Antigravity · OpenCode · Kilo Code
Any client implementing the Model Context Protocol should work. Clients with native remote HTTP support connect directly; the rest use the mcp-remote fallback above.
Once connected, ask your assistant things like:
Generate a HyperExecute YAML for my Playwright TypeScript tests and run it.
My last automation build failed — pull the console and network logs and tell me why.
Summarise the SmartUI visual differences in my latest build.
Run an accessibility audit on https://staging.example.com and list WCAG violations by severity.
Server doesn't appear after editing config Fully quit and reopen the client. Reloading the window is not enough for most clients to re-read MCP configuration.
Config not being picked up Validate the JSON. A trailing comma or mismatched brace will cause the client to silently skip the entry.
`npx` not found (STDIO fallback) Confirm Node.js is on your PATH — which npx on macOS/Linux, where npx on Windows. Some clients don't inherit your shell environment, so an absolute path to npx may be needed.
Authentication loop or expired session Clear the stored authentication for this server in your client's MCP settings and reconnect to re-trigger the OAuth flow.
Built by TestMu AI (formerly LambdaTest)