mcpField
K
k6-mcp-server

k6-mcp-server

Local
github.com/MaximilianPMXDeveloper Tools0Updated 79w ago
Repository

About k6-mcp-server

k6-mcp-server is an MCP-based server that receives and processes data from the k6 load testing tool. It provides a POST endpoint for metric data and uses a plugin-oriented, event-driven design.

Key features

  1. 01Receives k6 data at POST /data
  2. 02Processes metric names, values, timestamps, and tags
  3. 03Returns success or validation error responses
  4. 04Loads configuration from config.yaml

Use cases

  1. 01Sending k6 metrics to a central service
  2. 02Handling and validating posted load-test data

MCP support

The project describes an MCP-based server with an event-driven and plugin architecture. Its documented `/data` endpoint receives k6 metric data.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

k6-mcp-server

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

API Documentation

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

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 received and processed."
}

Error (400 Bad Request):

Returned if the request body is invalid or missing required fields. The response body will provide details about the error.

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

Error (500 Internal Server Error):

Returned if there's an unexpected error during processing.

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

Configuration

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.