LRC

A Node.js MCP server that exposes LoadRunner Cloud APIs for automated access to projects, tests, runs, and HTTP data.

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "pbandreddy-loadrunner-cloud-mcp-server": {
      "command": "node",
      "args": [
        "mcpServer.js"
      ],
      "env": {
        "LRC_CLIENT_ID": "YOUR_CLIENT_ID",
        "LRC_TENANT_ID": "YOUR_TENANT_ID",
        "LRC_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

You can run a dedicated MCP server to interact with LoadRunner Cloud APIs from any MCP client. This server exposes a set of tools you can call programmatically to retrieve projects, load tests, scripts, test runs, and HTTP responses, enabling automated performance workflows, dashboards, and AI integrations.

How to use

You connect an MCP client to the server by configuring an MCP server entry that points to the local or remote runtime. Start the local server with Node.js and then call the available tools from your MCP client. The server supports both standard continuous operation and Server-Sent Events (SSE) mode for real-time updates.

How to install

Prerequisites: Install Node.js (v18+ required, v20+ recommended) and npm comes with Node.js.

Step by step install and run:

# 1) Install dependencies
npm install

# 2) (Optional) Copy example environment and fill credentials
cp .env.example .env
# Edit .env and fill in LRC_TENANT_ID, LRC_CLIENT_ID, LRC_CLIENT_SECRET

# 3) Start the MCP server
node mcpServer.js

# 4) Start with SSE support (optional)
node mcpServer.js --sse

Note: Ensure you run these commands from the project directory where the server files reside.

## Additional sections

MCP server configuration and environment variables are provided to help you connect your MCP client. The server is designed to work with any MCP client and can be extended to support additional APIs as needed.

Environment variables you need to supply in your runtime configuration are shown in the example. Create a .env file with these values to enable authenticated access to LoadRunner Cloud.

## Server configuration examples

json { "mcpServers": { "lrc_mcp": { "type": "stdio", "command": "node", "args": ["mcpServer.js"] } }, "envVars": { "LRC_TENANT_ID": "YOUR_TENANT_ID", "LRC_CLIENT_ID": "YOUR_CLIENT_ID", "LRC_CLIENT_SECRET": "YOUR_CLIENT_SECRET" } }

## Notes

Two common usage patterns are provided: a plain run with normal tool calls and an SSE-enabled run that streams events to your MCP client. Both patterns allow you to retrieve projects, load tests, scripts, test runs, and HTTP responses, enabling automated workflows.

## Available tools

### get\_projects

Retrieve all projects within a tenant.

### test\_runs\_getActiveTestRuns

Fetch currently active test runs from LoadRunner Cloud.

### test\_runs\_getTestRunTransactions

List all transaction information associated with a test run.

### test\_runs\_getTestRunSummary

Obtain a summary for a specific test run.

### test\_runs\_getHttpResponses

Retrieve HTTP responses collected for a test run.

### projects\_getLoadTests

Retrieve load tests within a project.

### projects\_getLoadTestScripts

Retrieve scripts for a load test in a project.

### projects\_getLoadTestRuns

Retrieve runs for a load test in a project.