English Français العربية

io.github.kubeshop/testkube-mcp

Official registry AI and agents

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http testkube-mcp 'https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "testkube-mcp": {
            "type": "http",
            "url": "https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp"
        }
    }
}
OCI package docker.io/kubeshop/mcp-server:2.15.0
Claude Code 
claude mcp add testkube-mcp -e 'TK_ACCESS_TOKEN=<your tk_access_token>' -e 'TK_ORG_ID=<TK_ORG_ID>' -e 'TK_ENV_ID=<TK_ENV_ID>' -e 'TK_CONTROL_PLANE_URL=<TK_CONTROL_PLANE_URL>' -e 'TK_DASHBOARD_URL=<TK_DASHBOARD_URL>' -e 'TK_DEBUG=<TK_DEBUG>' -e 'TK_MCP_SHTTP_AUTH_TOKEN=<your tk_mcp_shttp_auth_token>' -- docker run -i --rm docker.io/kubeshop/mcp-server:2.15.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "testkube-mcp": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "docker.io/kubeshop/mcp-server:2.15.0"
            ],
            "env": {
                "TK_ACCESS_TOKEN": "<your tk_access_token>",
                "TK_ORG_ID": "<TK_ORG_ID>",
                "TK_ENV_ID": "<TK_ENV_ID>",
                "TK_CONTROL_PLANE_URL": "<TK_CONTROL_PLANE_URL>",
                "TK_DASHBOARD_URL": "<TK_DASHBOARD_URL>",
                "TK_DEBUG": "<TK_DEBUG>",
                "TK_MCP_SHTTP_AUTH_TOKEN": "<your tk_mcp_shttp_auth_token>"
            }
        }
    }
}

Environment variables

  • TK_ACCESS_TOKEN required secret Testkube access token for authentication
  • TK_ORG_ID required Testkube organization ID
  • TK_ENV_ID required 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_SHTTP_AUTH_TOKEN secret Separate inbound bearer token, required only when explicitly using --transport=shttp; not needed for default stdio

Documentation

From the project's README on GitHub, refreshed weekly. Links open 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..

Website | Docs | Changelog | Blog | Slack | LinkedIn | X

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.

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:

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

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

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!

Frequently asked questions

What is io.github.kubeshop/testkube-mcp?

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

How do I install io.github.kubeshop/testkube-mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http testkube-mcp 'https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.kubeshop/testkube-mcp need an API key?

Yes. It expects TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_MCP_SHTTP_AUTH_TOKEN, which you set in its configuration.

Is io.github.kubeshop/testkube-mcp open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.kubeshop/testkube-mcp?

It is published by kubeshop. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.