Reportportal MCP Server

The ReportPortal MCP Server is a middleware service that allows users to directly query and analyze ReportPortal's test execution results through chat tools such as GitHub Copilot.

Developer tools Monitoring #Test analysis #Middleware #API integration .Go

rating : 2 points

downloads : 17

update time : 2025-04-28

What is the ReportPortal MCP Server?

The ReportPortal MCP Server is a middleware service that serves as a bridge between the ReportPortal testing platform and AI assistants (such as GitHub Copilot, Claude, etc.). Through this service, users can query test execution results and analyze test data directly in the chat interface without logging in to the ReportPortal web - end.

How to use the ReportPortal MCP Server?

To use this service, you need to first deploy the MCP server and configure the connection with the ReportPortal instance. After that, users can query test data by sending requests in a specific format, and the server will return the results in a structured form.

Applicable scenarios

It is suitable for scenarios such as developers quickly viewing relevant test results during the coding process, testers referring to historical execution data when writing test cases, and project managers monitoring the project test status in real - time.

Main features

Test execution listSupports paged query of test execution records in ReportPortal and can be filtered by multiple conditions.

Test execution detailsGet detailed information of a specific test execution by name or ID.

Test item queryView all test items and their statuses included in a specific test execution.

Advanced filteringSupports filtering test data by multiple conditions such as status, time range, and attributes.

Advantages and limitations

Advantages

Get test results in the development environment without switching tools

Simplify the query process of test data

Support multiple filtering conditions for accurate problem location

Seamlessly integrate with common AI assistants

Limitations

Require additional deployment and maintenance of the MCP server

Have limited functions compared to the full ReportPortal web - end

Require configuration of API access permissions

How to use

Installation preparation

Ensure that Go 1.24.1 or a higher version is installed and prepare the access permissions for the ReportPortal instance.

Build the server

Clone the repository and build the executable file.

Configure environment variables

Set the ReportPortal connection parameters.

Start the server

Run the built executable file.

Usage examples

Query recent test executionsDevelopers want to know the results of the last 5 test executions.

Find failed testsTesters want to view the details of the recently failed test executions.

Analysis of specific test itemsDevelopers want to view the detailed execution history of specific test items.

Frequently Asked Questions

How to get the ReportPortal API token?

Which port does the server listen on by default?

What filtering conditions are supported?

Is there a limit to the page size of query results?

Related resources

ReportPortal official documentation

Complete documentation for the ReportPortal platform

GitHub repository

Source code of the MCP server

API reference

Detailed description of the ReportPortal API

🚀 ReportPortal MCP Server Report

This repository contains a ReportPortal MCP Server. It allows users to interact with ReportPortal directly from chats like GitHub Copilot / Claude / etc. to query and analyze test execution results.

🚀 Quick Start

The ReportPortal MCP Server enables users to interact with ReportPortal directly from chat interfaces such as GitHub Copilot or Claude. This facilitates seamless querying and analysis of test execution results, enhancing the efficiency of the testing process.

✨ Features

The ReportPortal MCP Server offers the following features:

List launches with pagination.
Get launch details by name.
Filter launches using various criteria.
View test execution reports.

📦 Installation

Prerequisites

Go 1.24.1 or higher.
A ReportPortal instance.

Build from Source

# Clone the repository
git clone https://github.com/reportportal/reportportal-mcp-server.git
cd reportportal-mcp-server

# Build the binary
go build -o reportportal-mcp-server ./cmd/reportportal-mcp-server

📚 Documentation

Configuration

The server is configured using environment variables:

Property	Details	Default Value
`RP_HOST`	ReportPortal service URL
`RP_PROJECT`	ReportPortal project name
`RP_TOKEN`	ReportPortal API token
`MCP_PORT`	Port to run the MCP server	`4389`

Usage

Start the Server

# Set the required environment variables
export RP_HOST="https://your-reportportal-instance.com"
export RP_PROJECT="your-project"
export RP_TOKEN="your-api-token"

# Run the server
./reportportal-mcp-server

Available Tools

List Launches

List ReportPortal launches with pagination support. Parameters:

page (optional): Page number (default: 1).
page-size (optional): Number of items per page (default: 20).

Get the Latest Launch by Name

Retrieve the latest launch with the specified name. Parameters:

launch: Name of the launch to search for.

Get the Latest Launch by Filter

Retrieve the latest launch that meets the specified filter criteria. Parameters:

name (optional): Filter by name.
description (optional): Filter by description.
uuid (optional): Filter by UUID.
status (optional): Filter by launch status (IN_PROGRESS, PASSED, FAILED, STOPPED, SKIPPED, INTERRUPTED).
start_time (optional): Filter by start time (Unix timestamp).
end_time (optional): Filter by end time (Unix timestamp).
attributes (optional): Filter by attributes (comma-separated key:value pairs).
mode (optional): Filter by launch mode (DEFAULT or DEBUG).
sort (optional): Sort direction and field (default: "desc(startTime)").