k6-mcp-server

What is k6-mcp-server?

k6-mcp-server is an event-driven server based on the Model Context Protocol (MCP) that receives and processes data from the k6 load testing tool. It can act as a central coordination point or data aggregation service for k6 test results.

How to use k6-mcp-server?

Configure the server via config.yaml, then run the server to expose the POST /data endpoint. k6 sends JSON payloads with metric data to this endpoint, and the server responds with success or error status.

Key features of k6-mcp-server

• Event-driven and plugin architecture based on MCP
• Accepts and processes data from k6 load testing
• Acts as central coordination and aggregation service
• Exposes a simple POST /data endpoint for metrics
• Configurable through a config.yaml file

Use cases of k6-mcp-server

• Aggregate metrics from multiple k6 test runs into a single server
• Coordinate distributed k6 load testing across instances
• Centralize real-time k6 data for monitoring and analysis
• Store and process k6 metrics for post-test reporting

FAQ from k6-mcp-server

What does k6-mcp-server do?

It accepts and processes data from k6 load testing tool via a POST /data endpoint, acting as a central coordination or aggregation service.

What is the expected request format?

The server expects a JSON body with metric_name (string), value (number), timestamp (Unix seconds), and an optional tags object.

What configuration does it use?

The server is configured via a config.yaml file that manages its runtime options.

What happens if the request is invalid?

The server returns a 400 Bad Request with a JSON error message describing missing or invalid fields.

What transport does the server use?

The server uses HTTP with a single POST endpoint at /data that accepts JSON payloads.