LambdaTest MCP server

What the model can do

LambdaTest (TestMu AI) cloud testing: automation builds and test sessions with status, browser, platform, duration and remarks, running and queued concurrency, open tunnels, and Test Manager projects, folders, test cases and test runs with pass and fail counts; when you ask, can mark a session passed or failed, rename a session or build, stop a running session, build or tunnel, delete a session or build, and in Test Manager create projects, test cases and test runs, set a test's result, and archive or delete runs and test cases.

Reads

• lambdatest_buildsAutomation builds, as LambdaTest lists them: name, status (running, queued, completed, timeout, error), project, tags…
• lambdatest_sessionsTest sessions (single test runs): name, status (passed, failed, error, timeout, running …), remark, build, browser and version, platform, device…
• lambdatest_concurrencyHow many tests are running and queued across the organisation right now (the plan's parallel sessions in use).
• lambdatest_tunnelsTunnels running in the account (connections that let cloud browsers reach a private network): id, name, status, whether shared, and when it started.
• lambdatest_test_managerTest Manager projects with their test case counts and tags; with project_id, that project's folders (folder ids are needed to create test cases).
• lambdatest_test_casesTest cases in a Test Manager project: key (TC-12), title, priority, status, type, whether automated, folder and estimate.
• lambdatest_test_runsTest runs in a Test Manager project with status, totals passed, failed, skipped and not started, and percent complete.

Acts, when you ask

These change something in LambdaTest. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• lambdatest_update_sessionMarks a LambdaTest session passed, failed, skipped, ignored, unknown or error (with a reason), renames it or replaces its tags…
• lambdatest_stop_sessionStops a running LambdaTest session now; the test is cut off where it is.
• lambdatest_delete_sessionPermanently deletes a LambdaTest session with its video, screenshots and logs.
• lambdatest_rename_buildRenames a LambdaTest build.
• lambdatest_stop_buildStops every running and queued test in a LambdaTest build now; a stopped build cannot be resumed.
• lambdatest_delete_buildPermanently deletes a LambdaTest build from the dashboard with its sessions.
• lambdatest_stop_tunnelStops a running LambdaTest tunnel; tests that need it to reach a private site fail until it is started again from wherever it runs.
• lambdatest_create_projectCreates a Test Manager project, visible to the organisation's Test Manager users.
• lambdatest_create_test_casesCreates one or more test cases in a Test Manager folder (lambdatest_test_manager with project_id lists folders).
• lambdatest_create_test_runCreates an empty test run in a Test Manager project (test cases are added in Test Manager).
• lambdatest_update_test_run_instanceRecords a result (Passed, Failed, Not Started) for one test case in a Test Manager run, and/or assigns it to a Test Manager user by id…
• lambdatest_archive_test_runArchives a Test Manager test run, taking it out of the active list (it is kept).
• lambdatest_delete_test_runPermanently deletes a Test Manager test run and its recorded results.
• lambdatest_delete_test_casePermanently deletes a Test Manager test case and its steps.

Connect it

First connect LambdaTest on Dashboard → Connections, then add Memtro to your client once. The LambdaTest tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared LambdaTest connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which sessions failed in the nightly build?
• › How many tests are running and queued right now?
• › Which tunnels are open?
• › How far has the release regression test run got?
• › Mark session 8812 as failed with the reason checkout timeout.

Questions

Is this an official LambdaTest MCP server?

No. It is Memtro's MCP server with Memtro's LambdaTest connector behind it: the connector reads LambdaTest through its API with the credentials you connect on Dashboard → Connections, and LambdaTest publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in LambdaTest?

Only when you ask, and only what it has been granted: mark a test session passed or failed, rename or retag it; stop a running test session; delete a test session; rename a build; stop every running test in a build; delete a build; stop a running tunnel; create a Test Manager project; create test cases in a Test Manager folder; create a test run; set a test run instance's result or assignee; archive a test run; delete a test run; delete a test case. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server