You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/accessibility-mcp-server.md
-62Lines changed: 0 additions & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,68 +68,6 @@ Here are the key benefits of using Accessibility MCP Server:
68
68
- Generates a comprehensive accessibility report that can be shared with team members.
69
69
- Provides suggested remediations for addressing accessibility (a11y) issues in locally hosted applications.
70
70
71
-
72
-
## Connecting to Accessibility MCP Server
73
-
74
-
The interface can be used with various AI assistants that support the Model Context Protocol (MCP). Here's how to connect using popular assistants:
75
-
76
-
### Connecting with Cline
77
-
Cline (The Collaborative AI Coder) is an advanced, AI-powered coding assistant that integrates seamlessly into your development workflow. It provides intelligent code suggestions and documentation help—and now, with MCP support, it can interface with tools like LambdaTest Accessibility MCP to enhance your testing capabilities.
78
-
79
-
#### Installing Cline in VS Code:
80
-
81
-
**Step 1:** Open VS Code.<br />
82
-
**Step 2:** Click on the Extensions icon in the Activity Bar on the side of the window (or press `Ctrl+Shift+X`).<br />
83
-
**Step 3:** Search for **Cline** in the Extensions Marketplace.
**Step 3:** Add Server Name as **MCP-Accessibility**.<br />
101
-
**Step 4:** Enter the following URL in the server URL field: `http://mcp-api.lambdatest.com/automation?<_USERNAME=[your-lt-username]<_ACCESS_KEY=[your-lt-access-key]` <br />
102
-
**Step 5:** Replace [your-lt-username] and [your-lt-access-key] with your LambdaTest credentials. <br />
Copy file name to clipboardExpand all lines: docs/automation-mcp-server.md
-66Lines changed: 0 additions & 66 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,72 +67,6 @@ Here are the key benefits of using the Automation MCP Server:
67
67
4. Generate new test cases using execution data from LambdaTest.
68
68
5. Leverage network logs, Selenium logs, and console logs to pinpoint bottlenecks and failures.
69
69
70
-
## Connecting to Automation MCP Server
71
-
72
-
### Connecting with Cline
73
-
74
-
Cline (The Collaborative AI Coder) is an advanced, AI-powered coding assistant that integrates seamlessly into your development workflow. It provides intelligent code suggestions and documentation help—and now, with MCP support, it can interface with tools like LambdaTest Automation MCP to enhance your testing capabilities.
75
-
76
-
Cline allows natural language interaction with your codebase—just describe what you want, instead of manually configuring it.
77
-
78
-
#### Installing Cline in VS Code:
79
-
80
-
**Step 1:** Open VS Code.<br />
81
-
**Step 2:** Click on the Extensions icon in the Activity Bar on the side of the window (or press `Ctrl+Shift+X`).<br />
82
-
**Step 3:** Search for **Cline** in the Extensions Marketplace.
**Step 3:** Add Server Name as **LambdaTest-MCP**.<br />
100
-
**Step 4:** Enter the following URL in the server URL field: `https://mcp-api.lambdatest.com/automation?<_USERNAME=[your-lt-username]<_ACCESS_KEY=[your-lt-access-key]` <br />
101
-
**Step 5:** Replace [your-lt-username] and [your-lt-access-key] with your LambdaTest credentials. <br />
102
-
**Step 6:** Click on **Add Server**.
103
-
104
-
### Interacting with Automation MCP Server
105
-
106
-
Once connected, you can begin using Cline to interact with the Automation MCP Server. A typical workflow:
107
-
108
-
109
-
**Step 1:** Open your project in VS Code.<br />
110
-
**Step 2:** Open the Cline panel.<br />
111
-
**Step 3:** Type the following prompt:
112
-
113
-
114
-
```
115
-
Analyze the LambdaTest TestID. Review the command logs, network logs, and console logs to identify the cause of the test failure. Suggest a code fix based on your findings.
116
-
```
117
-
118
-
**Step 4:** Cline will:
119
-
120
-
- Pull command, network, and console logs from the LambdaTest cloud.
121
-
- Identify your testing framework and test code.
122
-
- Investigate the cause of failure and share the RCA.
123
-
- Create change requests/suggestions in the code to fix the failure or enhance error handling.
124
-
- Save the code changes to your project directory.
125
-
126
-
**Step 5:** Review the suggested changes and make any final adjustments before re-running your tests on the LambdaTest platform.
127
-
128
-
You can also ask Cline more specific questions like:
129
-
130
-
-*"What are the possible causes of failure, and what else can be done to mitigate them?"*
131
-
-*"What does the suggested code change do?"*
132
-
133
-
Cline’s natural language interface allows you to work on triaging and debugging Selenium tests directly alongside your code—highlighting the specific sections responsible for the failure.
Copy file name to clipboardExpand all lines: docs/hyperexecute-mcp-server.md
-102Lines changed: 0 additions & 102 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,108 +71,6 @@ Here are the key benefits of using HyperExecute MCP Server:
71
71
-**Efficient Debugging:** Inspect test results with comprehensive recordings
72
72
-**Instant Documentation:** Access relevant documentation through integrated AI agents
73
73
74
-
## Connecting to HyperExecute MCP Server
75
-
76
-
### Connecting with Cline
77
-
Cline (The Collaborative AI Coder) is an advanced AI-powered coding assistant that integrates directly into your development workflow. It provides intelligent code suggestions and documentation assistance, and now, with MCP support, you can interface with external tools like HyperExecute to enhance your testing capabilities. Cline offers natural language interactions with your codebase, allowing you to simply describe what you need rather than manually configuring everything.
78
-
79
-
#### Installing Cline in VS Code:
80
-
81
-
**Step 1:** Open VS Code.<br />
82
-
**Step 2:** Click on the Extensions icon in the Activity Bar on the side of the window (or press `Ctrl+Shift+X`).<br />
83
-
**Step 3:** Search for **Cline** in the Extensions Marketplace.
**Step 3:** Add Server Name as **MCP-HyperExecute**.<br />
101
-
**Step 4:** Enter the following URL in the server URL field: `http://mcp.lambdatest.com/hyperexecute?&username=[your-lt-username]&accessKey=[your-lt-access-key]` <br />
102
-
**Step 5:** Replace [your-lt-username] and [your-lt-access-key] with your LambdaTest credentials. <br />
Once connected, you can start using Cline to interact with the HyperExecute MCP Server. A common workflow would be:
110
-
111
-
**Step 1:** Open your project in VS Code.<br />
112
-
**Step 2:** Open the Cline panel.<br />
113
-
**Step 3:** Type the following prompt: `Analyze the project and create a HyperExecute YAML file using MCP HyperExecute server.`<br />
114
-
**Step 4:** Cline will:
115
-
- analyze your project structure.
116
-
- Identify your testing framework and test files.
117
-
- Generate appropriate test runner commands.
118
-
- Create a complete HyperExecute YAML configuration file tailored to your project.
119
-
- Save the YAML file to your project directory.<br />
120
-
121
-
**Step 5:** You can then review the generated YAML file and make any necessary adjustments (if any, e.g., adding environment variables, etc.) before running your tests on the LambdaTest HyperExecute Platform.
122
-
123
-
You can also ask Cline for more specific operations, such as:
124
-
125
-
- "What are the key features of HyperExecute?"
126
-
- "What does failFast in HyperExecute mean?"
127
-
128
-
The natural language interface allows you to work with HyperExecute without having to remember specific command syntax or configuration details.
129
-
130
-
## Connecting With Other MCP-Compatible Tools
131
-
132
-
For any other MCP-compatible tool, use the following URL format:
133
-
134
-
```
135
-
https://mcp.lambdatest.com/mcp
136
-
```
137
-
138
-
Make sure to include your LambdaTest username and access key in the request headers:
139
-
140
-
*`username`: Your LambdaTest username.
141
-
*`accesskey`: Your LambdaTest access key.
142
-
143
-
Configure the above parameters in your MCP tool configuration file:
144
-
145
-
```
146
-
{
147
-
"mcpServers": {
148
-
"mcp-lambdatest": {
149
-
"disabled": false,
150
-
"timeout": 60,
151
-
"type": "stdio",
152
-
"command": "npx",
153
-
"args": [
154
-
"mcp-remote@latest",
155
-
"https://mcp.lambdatest.com/mcp",
156
-
"--header",
157
-
"username:<user_name>",
158
-
"--header",
159
-
"accessKey:<access_key>"
160
-
]
161
-
}
162
-
}
163
-
}
164
-
```
165
-
166
-
167
-
## Authentication
168
-
169
-
The server supports authentication for the HTTP interface and for LambdaTest API calls:
170
-
171
-
***HTTP Interface**: Requires a valid LambdaTest username and access key in the request headers.
172
-
***LambdaTest API Calls**: Can use credentials provided in the request or from environment variables (`LT_USERNAME` and `LT_ACCESS_KEY`).
0 commit comments