Rename HyperExecute MCP Server to LambdaTest MCP Server and reorder entry

[tanveer-farooq]

Description

LambdaTest MCP Servers ranging from Accessibility, SmartUI, Automation, and HyperExecute allows you to connect AI assistants with your testing workflow, streamlining setup, analyzing failures, and generating fixes to speed up testing and improve efficiency.

Server Details

• Server:

Option 1: Remote MCP Server (StreamableHTTP)

{
  "mcpServers": {
    "mcp-lambdatest-remote": {
      "disabled": false,
      "timeout": 60,
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "https://mcp.lambdatest.com/mcp",
        "--header",
        "username:<LT_USERNAME>",
        "--header",
        "accessKey:<LT_ACCESSKEY>"
      ],
      "transportType": "streamableHTTP"
    }
  }
}

Option 2: Local STDIO Server (NPM Package)

{
  "mcpServers": {
    "mcp-lambdatest-stdio": {
      "disabled": false,
      "timeout": 100,
      "command": "npx",
      "args": ["-y", "mcp-lambdatest", "--transport=stdio"],
      "env": {
        "LT_USERNAME": "<LT_USERNAME>",
        "LT_ACCESS_KEY": "<LT_ACCESSKEY>"
      },
      "transportType": "stdio"
    }
  }
}

• Changes to:

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

Need to update link