K6 MCP Server

🚀 k6-mcp Server Refactoring

Recreate the core event-driven and plugin-based Model Context Protocol (MCP) of the k6-mcp server. This project aims to provide a server that can receive and process data from the k6 load testing tool, potentially serving as a central coordination point or data aggregation service.

🚀 Quick Start

The k6-mcp server is designed to receive and handle data from the k6 load testing tool. It plays a crucial role in coordinating and aggregating data during load testing.

📚 Documentation

📄 API Documentation

The server exposes an API endpoint to receive data from k6. This section describes the expected request format and server responses.

Endpoint

POST /data

Request

Headers:

Content-Type: application/json

Body (JSON example):

{
  "metric_name": "my_custom_metric",
  "value": 123.45,
  "timestamp": 1678886400,  // Unix timestamp in seconds
  "tags": {
    "environment": "production",
    "region": "us-west-2"
  }
}

Response

Success (200 OK):

{
  "status": "success",
  "message": "Data has been received and processed."
}

Error (400 Bad Request, Invalid Request):

This error is returned if the request body is invalid or missing required fields. The response body will provide detailed information about the error.

{
  "status": "error",
  "message": "Invalid request body: missing 'metric_name' field."
}

Error (500 Internal Server Error):

This error is returned if an unexpected error occurs during processing.

{
  "status": "error",
  "message": "Internal server error."
}

⚙️ Configuration

The server's configuration is managed through the config.yaml file. Refer to the config.yaml file for available options.