io.github.kubeshop/testkube-mcp

Official

by kubeshop · Go

MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants

io.github.kubeshop/testkube-mcp MCP Server

This MCP server provides access to Testkube for managing test workflows, executions, and artifacts via AI assistants. It centers on defining, running, and analyzing automated tests while using existing testing tools. It targets Kubernetes-based testing and supports CI/CD and GitOps-oriented environments.

🛠️ Key Features

Manage test workflows
Manage test executions
Manage test artifacts
Use existing testing tools

🚀 Use Cases

Automated testing in Kubernetes
CI/CD test execution and analysis
DevOps and GitOps testing workflows
Quality assurance and testing automation
Monitoring/testing outcomes as part of pipelines

⚡ Developer Benefits

Integration with AI agents for test management
Unified handling of workflows, executions, and artifacts
Supports testing tool reuse rather than replacement

⚠️ Limitations

No tool count or specific MCP tools are described in the provided data.

Topics

kubernetestestingtesting-toolscicddevopsmonitoringquality-assurancetesting-automationtestkubegitopstest-automationaiai-agents

README.md10 KBView on GitHub

The Open Testing Platform for AI-driven Engineering Teams

Testkube provides a single platform for defining, running and analyzing automated tests, using your existing testing tools/scripts, running in your Kubernetes infrastructure.

Trusted by Engineering Teams at CoreWeave, NVidia, Siemens, T-Mobile, Harvard, SwissCom, and many more..

Why Testkube?

Run any Tests : Execute any tests/tools/scripts at scale; API, E2E, Performance, Security, Infrastructure, etc. - Examples & Guides.
Trigger Tests whenever needed: Trigger tests manually, on schedules, from CI/CD/GitOps pipelines, on Kubernetes Events, via the REST API, through MCP, etc. - Read More.
See Everything: All test results, artifacts, logs and resource-metrics are aggregated for centralized troubleshooting and reporting - Read More.
Integrate Natively: Testkube integrates with existing tools and infrastructure using Webhooks, the Testkube REST API or the MCP Server - see Integration Examples.
Testkube AI: Use the Testkube MCP Server or native AI Agents for troubleshooting, analysis, remediation, etc - Read More
Enterprise Ready: SSO/SCIM, RBAC, Teams, Resource-Groups, Audit-logs, etc. - Read More.

Testkube Dashboard

See it in action: Open the interactive TestWorkflows showcase to see how a workflow builds up from a single test to a fully orchestrated pipeline.

Two ways to run Testkube

Open Source Agent - this repo.

MIT-licensed, runs standalone in your Kubernetes cluster, no control plane required. Great for single-cluster setups, self-managed environments, and evaluating Testkube.

The Helm or CLI Installation will make it easy to deploy the agent into your target cluster.
The Quickstart is the easiest way to set up Testkube and run your first tests.

Check out the Testkube Open Source Overview to learn more about the open source deployment architecture.

Commercial Control Plane

The control plane connects every Testkube agent across clusters, teams, and environments into a single dashboard:

One control plane, unlimited clusters - orchestrate and analyze tests across clusters and regions
Testkube AI - workflow generation, failure investigation, remediation PRs
Enterprise-grade - SSO/SCIM, RBAC, audit logs, SLA-backed support

Check out the Installation Overview to learn more about different ways to deploy and run the Testkube Control Plane.

The online Trial is the easiest way to try the commercial Testkube offering - Get Started

Marketplace

The Testkube Marketplace provides an open and ready-to-use catalog of Testkube Workflows for Infrastructure Testing - Read More.

Documentation

Extensive documentation is available at docs.testkube.io.

Contributing

Check out our Contributors Guide and the Agent Architecture to find your way around our codebase and process.

If you want to contribute code, this reading order works well:

CONTRIBUTING.md - contribution workflow, coding standards, and PR process
DEVELOPMENT.md - local setup with Tilt and day-to-day development loop
ARCHITECTURE.md - high-level system design and key code paths

Shout-out to our contributors 🎉 - you're great!

⭐️ @lreimer - K6 executor Gradle executor Maven executor
⭐️ @jdborneman-terminus - Ginkgo executor
️⭐️ @abhishek9686
⭐️ @ancosma
⭐️ @Stupremee
⭐️ @artem-zherdiev-ingio
⭐️ @chooco13 - Playwright executor

Go to contribution document to read more how can you help us 🔥

Feedback

Whether Testkube helps you or not, we would love to help and hear from you. Please join us on Slack to ask questions and let us know how we can make Testkube even better!

Install

Configuration

Environment variables

TK_ACCESS_TOKENrequiredsecret

Testkube access token for authentication

TK_ORG_IDrequired

Testkube organization ID

TK_ENV_IDrequired

Testkube environment ID

TK_CONTROL_PLANE_URL

Testkube Control Plane URL (default: https://api.testkube.io)

TK_DASHBOARD_URL

Testkube Dashboard URL

TK_DEBUG

Enable debug mode (default: false)

TK_MCP_TRANSPORT

MCP transport type: stdio or shttp (default: stdio)

TK_MCP_SHTTP_HOST

SHTTP host when using shttp transport

TK_MCP_SHTTP_PORT

SHTTP port when using shttp transport

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "testkube-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/kubeshop/mcp-server:2.9.1"
      ],
      "env": {
        "TK_ACCESS_TOKEN": "<YOUR_TK_ACCESS_TOKEN>",
        "TK_ORG_ID": "<YOUR_TK_ORG_ID>",
        "TK_ENV_ID": "<YOUR_TK_ENV_ID>",
        "TK_CONTROL_PLANE_URL": "<YOUR_TK_CONTROL_PLANE_URL>",
        "TK_DASHBOARD_URL": "<YOUR_TK_DASHBOARD_URL>",
        "TK_DEBUG": "<YOUR_TK_DEBUG>",
        "TK_MCP_TRANSPORT": "<YOUR_TK_MCP_TRANSPORT>",
        "TK_MCP_SHTTP_HOST": "<YOUR_TK_MCP_SHTTP_HOST>",
        "TK_MCP_SHTTP_PORT": "<YOUR_TK_MCP_SHTTP_PORT>"
      }
    }
  }
}