Skip to content

Commit a80f51b

Browse files
authored
Merge pull request #2203 from Ishavyas9/main
Updated documentation HYP MCP
2 parents 319b48d + 000bfe1 commit a80f51b

File tree

1 file changed

+47
-1
lines changed

1 file changed

+47
-1
lines changed

docs/hyperexecute-mcp-server.md

Lines changed: 47 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,53 @@ You can also ask Cline for more specific operations, such as:
152152

153153
The natural language interface allows you to work with HyperExecute without having to remember specific command syntax or configuration details.
154154

155-
**Available Tools:**
155+
## Connecting With Other MCP-Compatible Tools
156+
157+
For any other MCP-compatible tool, use the following URL format:
158+
159+
```
160+
https://mcp.lambdatest.com/mcp
161+
```
162+
163+
Make sure to include your LambdaTest username and access key in the request headers:
164+
165+
* `username`: Your LambdaTest username.
166+
* `accesskey`: Your LambdaTest access key.
167+
168+
Configure the above parameters in your MCP tool configuration file:
169+
170+
```
171+
{
172+
"mcpServers": {
173+
"mcp-lambdatest": {
174+
"disabled": false,
175+
"timeout": 60,
176+
"type": "stdio",
177+
"command": "npx",
178+
"args": [
179+
"mcp-remote@latest",
180+
"https://mcp.lambdatest.com/mcp",
181+
"--header",
182+
"username:<user_name>",
183+
"--header",
184+
"accessKey:<access_key>"
185+
]
186+
}
187+
}
188+
}
189+
```
190+
191+
192+
## Authentication
193+
194+
The server supports authentication for the HTTP interface and for LambdaTest API calls:
195+
196+
* **HTTP Interface**: Requires a valid LambdaTest username and access key in the request headers.
197+
* **LambdaTest API Calls**: Can use credentials provided in the request or from environment variables (`LT_USERNAME` and `LT_ACCESS_KEY`).
198+
199+
200+
201+
## Available HyperExecute MCP Tools
156202

157203
HyperExecute MCP Server provides five main tools:
158204

0 commit comments

Comments
 (0)