TF

testing-farm/mcp

Developer tools

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

1 stars 3 forks 品質 53 トレンド 5Apache-2.0

An MCP (Model Context Protocol) server for interacting with the Testing Farm service. This server provides tools to submit FMF-based test requests and list available composes for testing.

概要

An MCP (Model Context Protocol) server for interacting with the Testing Farm service. This server provides tools to submit FMF-based test requests and list available composes for testing. - : Submit test requests to Testing Farm - : Retrieve available OS composes for testing from public or redhat ranches - : Built with static typing - : Fully asynchronous API client using httpx - : Container images available This will run the MCP server with the stdio transport. If you wanna run it via HTTP using the sse transport, you can change the default container command: This will run the MCP server on port 9001 inside the container and it will be exposed out of the container. This project uses uv for package management. Set the Testing Farm API token as an environment variable: Submit a FMF test request to Testing Farm.

README

以下は原文 README の抜粋です。原文を見る。

Testing Farm MCP Server

An MCP (Model Context Protocol) server for interacting with the Testing Farm service. This server provides tools to submit FMF-based test requests and list available composes for testing.

Features

  • Submit Test Requests: Submit test requests to Testing Farm
  • List Composes: Retrieve available OS composes for testing from public or redhat ranches
  • Full Type Safety: Built with static typing
  • Async Support: Fully asynchronous API client using httpx
  • Container Ready: Container images available

Installation

# Pull the latest container image
podman pull ghcr.io/thrix/testing-farm-mcp:latest

# Run the MCP server
podman run -i --rm -e TESTING_FARM_API_TOKEN="your-api-token-here" ghcr.io/thrix/testing-farm-mcp:latest

This will run the MCP server with the stdio transport.

If you wanna run it via HTTP using the sse transport, you can change the default container command:

podman run -i --rm -e TESTING_FARM_API_TOKEN="your-api-token-here" -p 9001:9001 ghcr.io/thrix/testing-farm-mcp:latest \
  fastmcp run --transport sse --host 0.0.0.0 --port 9001 testing_farm_mcp/server.py

This will run the MCP server on port 9001 inside the container and it will be exposed out of the container.

Option 2: Local Development

This project uses uv for package management.

# Clone the repository
git clone https://github.com/thrix/testing-farm-mcp.git
cd testing-farm-mcp

# Install dependencies
just install

Option 3: Using ToolHive

# Using ToolHive from Stacklok
systemctl start --user podman.socket
thv secret set TESTING_FARM_API_TOKEN
thv run ghcr.io/thrix/testing-farm-mcp:latest

Configuration

Set the Testing Farm API token as an environment variable:

export TESTING_FARM_API_TOKEN="your-api-token-here"

Usage

Running the MCP Server

just start

Available Tools

submit_request

Submit a FMF test request to Testing Farm.

Parameters:

  • url (required): Git repository URL containing FMF metadata
  • ref (optional): Branch, tag, or commit to test
  • merge_sha (optional): Target commit SHA for merge testing
  • path (optional): Path to metadata tree root
  • plan_name (optional): Specific test plan to execute
  • plan_filter (optional): Filter for tmt plans
  • test_name (optional): Specific test to execute
  • test_filter (optional): Filter for tmt tests
  • environments (optional): Test environment configurations
GitHub で README 全文を見る

インストール

This server does not publish a one-line install command.

Open the repository installation guide MCP 初心者?mcpskill.org のガイドから始めましょう →