### Start the ReportPortal MCP Server

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Executes the built MCP server binary to start the service.

```bash
./reportportal-mcp-server
```

--------------------------------

### Install Go Task

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Installs the Go Task v3 command-line tool, used for managing development tasks.

```bash
go install github.com/go-task/task/v3/cmd/task@latest
```

--------------------------------

### Binary Installation Configuration

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Configuration for running the ReportPortal MCP Server using pre-built binaries. This specifies the path to the binary and required environment variables for ReportPortal connection.

```json
{
  "reportportal": {
    "command": "/path/to/reportportal-mcp-server-binary",
    "args": ["stdio"],
    "env": {
      "RP_API_TOKEN": "your-api-token",
      "RP_HOST": "https://your-reportportal-instance.com",
      "RP_PROJECT": "YourProjectInReportPortal"
    }
  }
}
```

--------------------------------

### ReportPortal MCP Server Docker Run Command

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Example Docker command to run the ReportPortal MCP Server, including setting necessary environment variables for API token, host, and project.

```bash
docker run -i --rm -e RP_API_TOKEN=your-api-token -e RP_HOST=https://your-reportportal-instance.com -e RP_PROJECT=YourProjectInReportPortal reportportal/mcp-server
```

--------------------------------

### Docker Installation Configuration

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Configuration for running the ReportPortal MCP Server via Docker. This includes the command to execute and environment variables required for connecting to a ReportPortal instance.

```json
{
  "reportportal": {
    "command": "docker",
    "args": [
      "run",
      "-i",
      "--rm",
      "-e",
      "RP_API_TOKEN",
      "-e",
      "RP_HOST",
      "-e",
      "RP_PROJECT",
      "reportportal/mcp-server"
    ],
    "env": {
      "RP_API_TOKEN": "your-api-token",
      "RP_HOST": "https://your-reportportal-instance.com",
      "RP_PROJECT": "YourProjectInReportPortal"
    }
  }
}
```

--------------------------------

### Build ReportPortal MCP Server

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Instructions for building the ReportPortal MCP Server from source, including prerequisites.

```bash
Prerequisites:
- Go 1.24.1 or later
- A ReportPortal instance

Building from Source:
```bash
# Add build commands here if available
```
```

--------------------------------

### Clone and Build ReportPortal MCP Server

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Steps to clone the ReportPortal MCP Server repository and build the executable binary using Go.

```bash
git clone https://github.com/reportportal/reportportal-mcp-server.git
cd reportportal-mcp-server

go build -o reportportal-mcp-server ./cmd/reportportal-mcp-server
```

--------------------------------

### Development Tasks for ReportPortal MCP Server

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Common development tasks using the Go Task tool, including fetching dependencies, building, testing, and running linters.

```bash
# Install Go dependencies
task deps

# Build the project
task build

# Run tests
task test

# Build with Docker
task docker:build

# Lint the code
task lint

# Format the code
task fmt
```

--------------------------------

### Extend Server: Adding New Tools

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Illustrates how to add a new tool to the ReportPortal MCP Server by implementing a new method in a resource file and registering it in the `NewServer` function.

```go
// In your resource file (e.g., launches.go)
func (lr *LaunchResources) toolNewFeature() (tool mcp.Tool, handler server.ToolHandlerFunc) {
    // Implement your tool
}

// In server.go
func NewServer(...) *server.MCPServer {
    // ...
    s.AddTool(launches.toolNewFeature())
    // ...
}
```

--------------------------------

### Extend Server: Adding New Prompts

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Explains how to add new prompts by creating YAML files in the `prompts` folder, which are automatically loaded by the server on startup.

```yaml
# Example: prompts/my_custom_prompt.yaml
# Define your prompt logic and parameters here.
# The server will automatically load this file.
```

--------------------------------

### VS Code GitHub Copilot MCP Server Configuration

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Configuration for integrating the ReportPortal MCP Server with GitHub Copilot in VS Code. Users need to open user configuration and add the server details.

```json
{
  "servers": {
    "reportportal": {
      // choose the Docker or binary configuration from the section above
    }
  }
}
```

--------------------------------

### ReportPortal Launch Management Commands

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Provides a comprehensive list of commands for managing ReportPortal launches, including filtering, retrieving, analyzing, and deleting launches.

```APIDOC
Get Launches by filter:
  Lists ReportPortal launches with pagination by filter.
  Parameters:
    - name (optional): Filter by launch name.
    - description (optional): Filter by launch description.
    - owner (optional): Filter by launch owner.
    - number (optional): Filter by launch number.
    - start_time (optional): Filter by launch start time.
    - end_time (optional): Filter by launch end time.
    - attributes (optional): Filter by launch attributes.
    - sort (optional): Sort order for launches.
    - page (optional): Page number for pagination.
    - page-size (optional): Number of items per page.

Get Last Launch by Name:
  Retrieves the most recent launch by name.
  Parameters:
    - name: The name of the launch to retrieve.

Run Auto Analysis:
  Runs auto analysis on a launch.
  Parameters:
    - launch_id: The ID of the launch to analyze.
    - analyzer_mode (optional): The mode for the analyzer.
    - analyzer_type (optional): The type of the analyzer.
    - analyzer_item_modes (optional): Modes for analyzer items.

Run Unique Error Analysis:
  Runs unique error analysis on a launch.
  Parameters:
    - launch_id: The ID of the launch to analyze.
    - remove_numbers (optional): Whether to remove numbers during analysis.

Force Finish Launch:
  Forces a launch to finish.
  Parameters:
    - launch_id: The ID of the launch to force finish.

Delete Launch:
  Deletes a specific launch.
  Parameters:
    - launch_id: The ID of the launch to delete.

Get Suites by filter:
  Lists test suites for a specific launch.
  Parameters:
    - launch-id (required): The ID of the launch.
    - name (optional): Filter by suite name.
    - description (optional): Filter by suite description.
    - start_time_from (optional): Filter by suite start time from.
    - start_time_to (optional): Filter by suite start time to.
    - attributes (optional): Filter by suite attributes.
    - parent_id (optional): Filter by parent suite ID.
    - sort (optional): Sort order for suites.
    - page (optional): Page number for pagination.
    - page-size (optional): Number of items per page.

Get Test Items by filter:
  Lists test items for a specific launch.
  Parameters:
    - launch-id (required): The ID of the launch.
    - name (optional): Filter by test item name.
    - description (optional): Filter by test item description.
    - status (optional): Filter by test item status.
    - has_retries (optional): Filter by whether test item has retries.
    - start_time_from (optional): Filter by test item start time from.
    - start_time_to (optional): Filter by test item start time to.
    - attributes (optional): Filter by test item attributes.
    - parent_id (optional): Filter by parent test item ID.
    - defect_comment (optional): Filter by defect comment.
    - auto_analyzed (optional): Filter by auto-analyzed status.
    - ignored_in_aa (optional): Filter by ignored in auto-analysis status.
    - pattern_name (optional): Filter by pattern name.
    - ticket_id (optional): Filter by ticket ID.
    - sort (optional): Sort order for test items.
    - page (optional): Page number for pagination.
    - page-size (optional): Number of items per page.

Get Logs by filter:
  Lists logs for a specific test item or nested step.
  Parameters:
    - parent-id (required): The ID of the parent test item or step.
    - log_level (optional): Filter by log level.
    - log_content (optional): Filter by log content.
    - logs_with_attachments (optional): Filter for logs with attachments.
    - status (optional): Filter by log status.
    - sort (optional): Sort order for logs.
    - page (optional): Page number for pagination.
    - page-size (optional): Number of items per page.

Get Attachment by ID:
  Retrieves an attachment binary by id.
  Parameters:
    - attachment_id: The ID of the attachment to retrieve.

Get Test Item by ID:
  Retrieves details of a specific test item.
  Parameters:
    - test_item_id: The ID of the test item to retrieve.
```

--------------------------------

### JetBrains IDEs GitHub Copilot MCP Server Configuration

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Configuration for connecting the ReportPortal MCP Server to GitHub Copilot within JetBrains IDEs. This involves editing settings and saving the mcp.json file.

```json
{
  "servers": {
    "reportportal": {
      // choose the Docker or binary configuration from the section above
    }
  }
}
```

--------------------------------

### ReportPortal Prompt: Analyze Launch

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Analyzes a ReportPortal launch, providing detailed information about test results, failures, and statistics. Requires the launch ID as a parameter.

```APIDOC
Analyze Launch:
  Analyzes a ReportPortal launch and provides detailed information about test results, failures, and statistics.
  Parameters:
    - launch_id: ID of the launch to analyze.
  Reference:
    - https://github.com/reportportal/reportportal-mcp-server/blob/main/internal/reportportal/prompts/launch.yaml
```

--------------------------------

### Configure ReportPortal MCP Server Environment Variables

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Sets the necessary environment variables for the MCP server to connect to ReportPortal, including host, project, and API token.

```bash
export RP_HOST="https://your-reportportal-instance.com"
export RP_PROJECT="YourProjectInReportPortal"
export RP_API_TOKEN="your-api-token"
```

--------------------------------

### Cursor MCP Server Configuration

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Configuration for setting up the ReportPortal MCP Server within the Cursor AI Code Editor. This involves adding a new global MCP server entry.

```json
{
  "mcpServers": {
    "reportportal": {
      // choose the Docker or binary configuration from the section above
    }
  }
}
```

--------------------------------

### Debug ReportPortal MCP Server with MCP Inspector

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Uses the MCP Inspector tool to test and debug the MCP server locally, either via npx or a Task command.

```bash
# Using npx
npx @modelcontextprotocol/inspector docker run -i --rm -e "RP_API_TOKEN=$RP_API_TOKEN" -e "RP_PROJECT=$RP_PROJECT" -e "RP_HOST=$RP_HOST" reportportal-mcp-server

# Using Task command
task inspector
```

--------------------------------

### Claude Desktop MCP Server Configuration

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Configuration snippet to add the ReportPortal MCP Server to Claude Desktop's settings. This allows Claude Desktop to connect to and query the ReportPortal MCP Server.

```json
{
  "mcpServers": {
    "reportportal": {
      // choose the Docker or binary configuration from the section above
    }
  }
}
```

--------------------------------

### Claude Code CLI Add MCP Server Command

Source: https://github.com/reportportal/reportportal-mcp-server/blob/main/README.md

Command to add the ReportPortal MCP Server to the Claude Code CLI using a JSON configuration. This enables querying ReportPortal data through the CLI.

```bash
claude mcp add-json reportportal '{"command": "docker", "args": ["run", "-i", "--rm", "-e", "RP_API_TOKEN", "-e", "RP_HOST", "-e", "RP_PROJECT", "reportportal/mcp-server"], "env": {"RP_API_TOKEN": "your-api-token", "RP_HOST": "https://your-reportportal-instance.com", "RP_PROJECT": "YourProjectInReportPortal"}}'
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.