Testkube MCP
Run, inspect and troubleshoot Testkube test workflows from an AI assistant
- Pricing
- Freemium
- Platforms
- API, self-hosted, Linux
- Runs
- Locally or Remotely
- Version
- 2.15.2
- Listing updated
- 2 days ago
About Testkube MCP
Testkube MCP is a freemium MCP server for developer tools. It can run locally on your machine or as a hosted remote server.
Testkube orchestrates tests inside Kubernetes clusters, and this server lets an assistant reach that setup: the registry entry says it manages test workflows, executions and artifacts. It runs as a stdio container image from the kubeshop organisation or as a remote streamable-HTTP endpoint scoped to an organisation and environment on api.testkube.io.
Authentication uses a Testkube access token plus organisation and environment IDs, with optional overrides for the control plane and dashboard URLs. The wider platform runs any kind of test (API, end-to-end, performance, security, infrastructure) and triggers them manually, on schedules, from CI or GitOps pipelines, on Kubernetes events or through MCP.
The repository README describes an MIT-licensed open-source agent for a single cluster and a commercial control plane that adds Testkube AI for workflow generation, failure investigation and remediation pull requests.
Install
Run in a terminal
claude mcp add testkube-mcp --env TK_ACCESS_TOKEN='<TK_ACCESS_TOKEN>' --env TK_ORG_ID='<TK_ORG_ID>' --env TK_ENV_ID='<TK_ENV_ID>' --env TK_MCP_SHTTP_AUTH_TOKEN='<TK_MCP_SHTTP_AUTH_TOKEN>' -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID -e TK_MCP_SHTTP_AUTH_TOKEN docker.io/kubeshop/mcp-server:2.15.2Add to claude_desktop_config.json
{
"mcpServers": {
"testkube-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"-e",
"TK_MCP_SHTTP_AUTH_TOKEN",
"docker.io/kubeshop/mcp-server:2.15.2"
],
"env": {
"TK_ACCESS_TOKEN": "<TK_ACCESS_TOKEN>",
"TK_ORG_ID": "<TK_ORG_ID>",
"TK_ENV_ID": "<TK_ENV_ID>",
"TK_MCP_SHTTP_AUTH_TOKEN": "<TK_MCP_SHTTP_AUTH_TOKEN>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"testkube-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"-e",
"TK_MCP_SHTTP_AUTH_TOKEN",
"docker.io/kubeshop/mcp-server:2.15.2"
],
"env": {
"TK_ACCESS_TOKEN": "<TK_ACCESS_TOKEN>",
"TK_ORG_ID": "<TK_ORG_ID>",
"TK_ENV_ID": "<TK_ENV_ID>",
"TK_MCP_SHTTP_AUTH_TOKEN": "<TK_MCP_SHTTP_AUTH_TOKEN>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"testkube-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"-e",
"TK_MCP_SHTTP_AUTH_TOKEN",
"docker.io/kubeshop/mcp-server:2.15.2"
],
"env": {
"TK_ACCESS_TOKEN": "<TK_ACCESS_TOKEN>",
"TK_ORG_ID": "<TK_ORG_ID>",
"TK_ENV_ID": "<TK_ENV_ID>",
"TK_MCP_SHTTP_AUTH_TOKEN": "<TK_MCP_SHTTP_AUTH_TOKEN>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"testkube-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"-e",
"TK_MCP_SHTTP_AUTH_TOKEN",
"docker.io/kubeshop/mcp-server:2.15.2"
],
"env": {
"TK_ACCESS_TOKEN": "<TK_ACCESS_TOKEN>",
"TK_ORG_ID": "<TK_ORG_ID>",
"TK_ENV_ID": "<TK_ENV_ID>",
"TK_MCP_SHTTP_AUTH_TOKEN": "<TK_MCP_SHTTP_AUTH_TOKEN>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"testkube-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"-e",
"TK_MCP_SHTTP_AUTH_TOKEN",
"docker.io/kubeshop/mcp-server:2.15.2"
],
"env": {
"TK_ACCESS_TOKEN": "<TK_ACCESS_TOKEN>",
"TK_ORG_ID": "<TK_ORG_ID>",
"TK_ENV_ID": "<TK_ENV_ID>",
"TK_MCP_SHTTP_AUTH_TOKEN": "<TK_MCP_SHTTP_AUTH_TOKEN>"
}
}
}
}Configuration
TK_ACCESS_TOKENTestkube access token for authenticationRequiredTK_ORG_IDTestkube organization IDRequiredTK_ENV_IDTestkube environment IDRequiredTK_CONTROL_PLANE_URLTestkube Control Plane URL (default: https://api.testkube.io)TK_DASHBOARD_URLTestkube Dashboard URLTK_DEBUGEnable debug mode (default: false)TK_MCP_SHTTP_AUTH_TOKENSeparate inbound bearer token, required only when explicitly using --transport=shttp; not needed for default stdio
What it does
- Workflow management
- Create and inspect Testkube test workflows through an assistant.
- Execution and artifact access
- Look up test runs, logs and artifacts for troubleshooting.
- Stdio or remote
- Run the container locally or connect to the hosted per-environment endpoint.
- Environment-scoped auth
- An access token with organisation and environment IDs limits what the server can see.
- Fits the wider platform
- Works alongside Testkube triggers, webhooks and the REST API.
Good for
- Ask why last night's end-to-end run failed
- Trigger a performance test workflow from a chat
- Pull artifacts from a failed execution into a debugging session
- Review which workflows exist in an environment
Pricing
Freemium
Open-source agent is MIT; commercial control plane has an online trial, prices not published
Testkube MCP FAQ
What credentials does it need?
TK_ACCESS_TOKEN, TK_ORG_ID and TK_ENV_ID are required; the control plane URL defaults to https://api.testkube.io.
Is there a remote endpoint?
Yes, a streamable-HTTP URL of the form api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp.
Is Testkube open source?
The README says the standalone agent is MIT-licensed; a commercial control plane adds multi-cluster dashboards, SSO and AI features.
Which test types does Testkube run?
API, end-to-end, performance, security and infrastructure tests, among others.
Is Testkube MCP free?
Testkube MCP has a free plan, with paid plans for more usage or features.
How do I add Testkube MCP to Claude Code?
Run this command in your terminal: claude mcp add testkube-mcp --env TK_ACCESS_TOKEN='<TK_ACCESS_TOKEN>' --env TK_ORG_ID='<TK_ORG_ID>' --env TK_ENV_ID='<TK_ENV_ID>' --env TK_MCP_SHTTP_AUTH_TOKEN='<TK_MCP_SHTTP_AUTH_TOKEN>' -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID -e TK_MCP_SHTTP_AUTH_TOKEN docker.io/kubeshop/mcp-server:2.15.2
What are the best alternatives to Testkube MCP?
The closest alternatives to Testkube MCP are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to Testkube MCP

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools