What features does ReportPortal MCP server provide?

Q: What features does ReportPortal MCP server provide?

Launch Management: Get and filter launches (test runs) with pagination; fetch launch details by name/ID; force-finish running launches; delete launches; run automated analyses on launches.. Test Item Analysis: Access test items within a launch by filter; view detailed test item information; view execution stats, failures, logs, and attachments.. Report Generation: Analyze launches to generate detailed test execution insights and structured reports.. Built-in Tools for Common Operations: Extensive set of built-in commands (e.g., get launches, last launch, logs, attachments, defect types, etc.) to drive interactive querying via MCP.. Prompts and Natural-Language Interaction: Includes predefined prompts (e.g., Analyze Launch) and example natural-language queries to guide interactions.. Deployment Options: Local deployment via Docker or pre-built binaries, plus remote HTTP server mode for centralized deployments.. MCP Protocol Compliance: Follows MCP guidelines, exposes JSON-RPC 2.0 endpoints and SSE streams; supports HTTP mode with /mcp endpoints.. Extensibility: Easily extend with new tools or prompts by adding code and YAML prompt files; prompts auto-load on startup.

ReportPortal MCP Server 2025: Features & Setup Guide

Overview

The ReportPortal MCP Server is a bridge between your ReportPortal instance and AI chat assistants (such as Claude Desktop, GitHub Copilot, Cursor). It follows the official MCP guidelines. It enables natural-language queries about test results by translating user questions into ReportPortal API operations and returning structured responses. For example, you can ask "What tests failed in the last run?" or "List the 5 most recent test runs," and the server will fetch data from ReportPortal. It supports local deployment via Docker or pre-built binaries, or connecting to a remote MCP server. In HTTP mode, it exposes MCP endpoints at /mcp (or /api/mcp) and provides info/health/status endpoints. It includes a built-in set of tools for common actions: listing launches, retrieving launch details, running auto analyses, obtaining test items, logs, attachments, and defect types. It also offers prompts and examples to guide prompts, and a path to extend the server by adding new tools or prompts via code or YAML prompts. It aims to be compatible with MCP-compatible AI tools and focuses on ease of integration.

Features

Launch Management

Get and filter launches (test runs) with pagination; fetch launch details by name/ID; force-finish running launches; delete launches; run automated analyses on launches.

Test Item Analysis

Access test items within a launch by filter; view detailed test item information; view execution stats, failures, logs, and attachments.

Report Generation

Analyze launches to generate detailed test execution insights and structured reports.

Built-in Tools for Common Operations

Extensive set of built-in commands (e.g., get launches, last launch, logs, attachments, defect types, etc.) to drive interactive querying via MCP.

Prompts and Natural-Language Interaction

Includes predefined prompts (e.g., Analyze Launch) and example natural-language queries to guide interactions.

Deployment Options

Local deployment via Docker or pre-built binaries, plus remote HTTP server mode for centralized deployments.

MCP Protocol Compliance

Follows MCP guidelines, exposes JSON-RPC 2.0 endpoints and SSE streams; supports HTTP mode with /mcp endpoints.

Extensibility

Easily extend with new tools or prompts by adding code and YAML prompt files; prompts auto-load on startup.