Testkube MCP Server is Testkube's official MCP entry point for AI-driven engineering teams running automated tests on Kubernetes, covering test workflows, executions, and artifacts. It supports both a locally run OCI image over stdio and a hosted streamable-http remote endpoint, gated by a Testkube access token plus organization and environment credentials, with documentation at https://docs.testkube.io/articles/mcp-overview. The source does not enumerate individual tools, so the tool list is empty.
Testkube MCP Server is maintained by Testkube and lets AI assistants manage Testkube test workflows, executions, and artifacts. It is available in two forms: a locally run OCI image, docker.io/kubeshop/mcp-server:latest, using stdio transport, and a hosted streamable-http remote at https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp. The remote endpoint requires organization_id (for example tkcorg_xxxxxxx) and environment_id (for example tkcenv_xxxxxxx). The local image requires TK_ACCESS_TOKEN, TK_ORG_ID, and TK_ENV_ID, with optional TK_CONTROL_PLANE_URL, TK_DASHBOARD_URL, TK_DEBUG, TK_MCP_TRANSPORT, TK_MCP_SHTTP_HOST, and TK_MCP_SHTTP_PORT. It suits teams running automated tests on Kubernetes that want to trigger tests, inspect results and artifacts, and troubleshoot from an AI assistant. It is not suitable for users without a Testkube organization/environment or those unwilling to give an AI client access to a test access token.