MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
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..
Website | Docs | Changelog | Blog | Slack | LinkedIn | X

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.
MIT-licensed, runs standalone in your Kubernetes cluster, no control plane required. Great for single-cluster setups, self-managed environments, and evaluating Testkube.
Check out the Testkube Open Source Overview to learn more about the open source deployment architecture.
The control plane connects every Testkube agent across clusters, teams, and environments into a single dashboard:
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
The Testkube Marketplace provides an open and ready-to-use catalog of Testkube Workflows for Infrastructure Testing - Read More.
Extensive documentation is available at docs.testkube.io.
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:
Shout-out to our contributors 🎉 - you're great!
Go to contribution document to read more how can you help us 🔥
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!
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
docker run -i --rm docker.io/kubeshop/mcp-server:2.14.2Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-kubeshop-testkube-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/kubeshop/mcp-server:2.14.2"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencedocker.io/kubeshop/mcp-server:2.14.2dockerio.github.kubeshop/testkube-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.