🚀 ⚡️ k6-mcp-server

Created By
QAInsightsa year ago
k6 MCP server
Overview

What is k6-mcp-server?

k6-mcp-server is a Model Context Protocol (MCP) server implementation designed for running k6 load tests, enabling users to efficiently conduct performance testing.

How to use k6-mcp-server?

To use k6-mcp-server, clone the repository, install the required dependencies, and set up environment variables if needed. Create a k6 test script and configure the MCP server to run your tests.

Key features of k6-mcp-server?

  • Simple integration with the Model Context Protocol framework
  • Support for custom test durations and virtual users (VUs)
  • Easy-to-use API for running k6 load tests
  • Configurable through environment variables
  • Real-time test execution output

Use cases of k6-mcp-server?

  1. LLM powered results analysis
  2. Effective debugging of load tests

FAQ from k6-mcp-server?

  • What are the prerequisites for using k6-mcp-server?

You need Python 3.12 or higher, the k6 load testing tool, and the uv package manager installed.

  • How do I run a test with custom options?

You can use the execute_k6_test_with_options function to specify your desired duration and number of virtual users.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
QAInsights
Star
8
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago