LoadRunner Cloud MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LoadRunner Cloud MCP Server get summary for test run 16287"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LRC-MCP Server
This project provides a Model Context Provider (MCP) server for integrating with LoadRunner Cloud (LRC) APIs. It enables automated, programmatic access to LRC resources and test data, making it easy to build performance engineering workflows, dashboards, and AI integrations.
Overview
The LRC-MCP Server exposes a set of tools for interacting with LoadRunner Cloud, including:
Retrieving projects, load tests, scripts, and test runs
Fetching transaction details, summaries, and HTTP responses for test runs
Automating performance data collection and reporting
The server is compatible with any MCP client, such as Claude Desktop or Cursor, and can be extended to support additional LRC APIs as needed.
Related MCP server: JMeter MCP Server (TypeScript Edition)
Getting Started
Prerequisites
Node.js (v18+ required, v20+ recommended)
npm (comes with Node.js)
Installation
Clone this repository and navigate to the project directory.
Install dependencies:
npm installCopy the example environment file and edit it with your real credentials:
cp .env.example .env # Then edit .env and fill in your LRC_TENANT_ID, LRC_CLIENT_ID, and LRC_CLIENT_SECRETThe
.env.examplefile provides a template for the required environment variables. You must create a.envfile (as above) and supply your actual credentials for the server to function.
Running the Server
Start the MCP server:
node mcpServer.jsYou can also run with Server-Sent Events (SSE) support:
node mcpServer.js --sseAvailable Tools
The following tools are available for interacting with LoadRunner Cloud:
get_projects: Retrieve all projects in a tenant.
test_runs_getActiveTestRuns: Get active test runs from LoadRunner Cloud.
test_runs_getTestRunTransactions: List all transaction information in a test run.
test_runs_getTestRunSummary: Get summary for a test run.
test_runs_getHttpResponses: Get HTTP responses for a test run.
projects_getLoadTests: Retrieve load tests for a project.
projects_getLoadTestScripts: Retrieve scripts for a load test in a project.
projects_getLoadTestRuns: Retrieve runs for a load test in a project.
Example Usage
You can call these tools from any MCP-compatible client. Example (JavaScript):
// Get all projects
await get_projects();
// Get load tests for a project
await projects_getLoadTests({ projectId: '10' });
// Get scripts for a load test in a project
await projects_getLoadTestScripts({ projectId: '10', loadTestId: '2159' });
// Get runs for a load test in a project
await projects_getLoadTestRuns({ projectId: '10', loadTestId: '2159' });
// Get HTTP responses for a test run
await test_runs_getHttpResponses({ runId: '16287' });Getting Absolute Paths (Shell & Windows)
To get the full path to node:
On Unix/Linux/macOS, run:
which nodeOn Windows PowerShell, run:
Get-Command node | Select-Object Source
To check the node version, run:
node --versionTo get the absolute path to mcpServer.js, run:
On Unix/Linux/macOS:
realpath mcpServer.jsOn Windows PowerShell (from the project directory):
Resolve-Path mcpServer.js
MCP Client Configuration
You can connect your MCP server to any MCP client. Below are instructions for Claude Desktop and Cursor.
Claude Desktop
Note the full path to node and the
mcpServer.jsfrom the previous step.Open Claude Desktop → Settings → Developers → Edit Config and add a new MCP server:
{ "mcpServers": { "<server_name>": { "command": "<absolute/path/to/node>", "args": ["<absolute/path/to/mcpServer.js>"] } } }Restart Claude Desktop to activate this change. Make sure the new MCP is turned on and has a green circle next to it.
Warning: If you don't supply an absolute path to a node version that is v18+, Claude (and other MCP clients) may fall back to another node version on the system of a previous version. In this case, the fetch API won't be present and tool calls will not work. If that happens, you can a) install a newer version of node and point to it in the command, or b) import node-fetch into each tool as fetch, making sure to also add the node-fetch dependency to your package.json.
Cursor
Note the full path to node and the
mcpServer.jsas above.In Cursor, go to Settings → AI Tools → MCP Servers (or similar MCP integration section).
Add a new MCP server configuration:
{ "command": "<absolute/path/to/node>", "args": ["<absolute/path/to/mcpServer.js>"] }Save and enable the server. Ensure it is running and available for tool calls in Cursor.
Docker Deployment
For production deployments, you can use Docker:
docker build -t lrc-mcp-server .About MCP
Model Context Provider (MCP) is a protocol for exposing programmatic tools to AI and automation clients. This server implements the MCP protocol for LoadRunner Cloud APIs.
For more information, see the source code and tool documentation.
Available Tools
9 toolsget_active_test_runsB
Get active test runs from LoadRunner Cloud.
Inputs: status, projectIds.
get_projectsB
Retrieve all projects in a tenant.
Inputs: no named parameters.
projects_getLoadTestRunsC
Retrieve runs for a load test in a project from LoadRunner Cloud.
Inputs: projectId (required), loadTestId (required).
projects_getLoadTestsC
Retrieve load tests for a project from LoadRunner Cloud.
Inputs: projectId (required).
projects_getLoadTestScriptsC
Retrieve scripts for a load test in a project from LoadRunner Cloud.
Inputs: projectId (required), loadTestId (required).
test_runs_getHttpResponsesC
Get HTTP responses for a test run from LoadRunner Cloud.
Inputs: runId (required).
test_runs_getRecentTestRunsB
Get recent test runs details for the last month from LoadRunner Cloud. Optionally filter by projectIds.
Inputs: projectIds.
test_runs_getTestRunResultsC
Get test run results from LoadRunner Cloud.
Inputs: runId (required).
test_runs_getTestRunTransactionsC
List all transaction information in a test run.
Inputs: runId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
- octoperfDeprecatedio.github.OctoPerf
Drive OctoPerf load testing from any AI agent: import, edit, validate, run scenarios, read metrics.
Load & browser performance testing — drive MaxoPerf from your AI agent with your API key.
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides programmatic access to BlazeMeter's performance testing platform through MCP tools. Enables users to retrieve test runs, analyze performance data, view error reports, and manage testing resources via natural language interactions.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically create, execute, and analyze Apache JMeter performance tests. It supports automated bottleneck detection, report generation, and distributed testing management through natural language.MIT
- FlicenseNot gradedqualityCmaintenanceIntegrates Apache JMeter with AI assistants to run and manage load tests through natural language. It enables users to execute test plans, parse results, inspect test structures, and compare performance metrics across different runs.-
- AlicenseAqualityDmaintenanceEnables AI agents to interact with HP ALM / Quality Center for QA workflows including test case management, test execution, defect tracking, and requirements management.342MIT