LoadRunner Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectsB | Retrieve all projects in a tenant. |
| get_active_test_runsB | Get active test runs from LoadRunner Cloud. |
| test_runs_getTestRunTransactionsC | List all transaction information in a test run. |
| test_runs_getTestRunResultsC | Get test run results from LoadRunner Cloud. |
| test_runs_getHttpResponsesC | Get HTTP responses for a test run from LoadRunner Cloud. |
| test_runs_getRecentTestRunsB | Get recent test runs details for the last month from LoadRunner Cloud. Optionally filter by projectIds. |
| projects_getLoadTestsC | Retrieve load tests for a project from LoadRunner Cloud. |
| projects_getLoadTestScriptsC | Retrieve scripts for a load test in a project from LoadRunner Cloud. |
| projects_getLoadTestRunsC | Retrieve runs for a load test in a project from LoadRunner Cloud. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes targeting different resources (projects, test runs, scripts, responses, results, transactions), but 'get_active_test_runs' and 'test_runs_getRecentTestRuns' could cause confusion as both retrieve test runs with temporal filters. Descriptions clarify one gets active runs and the other recent runs, but the overlap exists.
Naming is inconsistent with mixed conventions: some use snake_case (e.g., 'get_active_test_runs'), others use camelCase (e.g., 'projects_getLoadTestRuns'), and verb styles vary (e.g., 'get' vs 'retrieve'). This lack of a predictable pattern makes the set harder to navigate.
With 9 tools, the count is well-scoped for a LoadRunner Cloud server, covering key operations like retrieving projects, tests, runs, scripts, responses, results, and transactions. Each tool appears to serve a specific function without bloat.
The tools provide good read-only coverage for monitoring and retrieving data (projects, tests, runs, scripts, responses, results, transactions), but there are notable gaps in CRUD operations. For a load testing domain, missing tools for creating, updating, or deleting tests/runs limit agent capabilities for full lifecycle management.