Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Testkube MCP

by kubeshopversion 2.15.0i★ –iComputer or cloud
Registry nameio.github.kubeshop/testkube-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_MCP_SHTTP_AUTH_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_CONTROL_PLANE_URL, TK_DASHBOARD_URL, TK_DEBUG, TK_MCP_SHTTP_AUTH_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "testkube": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TK_ACCESS_TOKEN",
        "-e",
        "TK_ORG_ID",
        "-e",
        "TK_ENV_ID",
        "-e",
        "TK_CONTROL_PLANE_URL",
        "-e",
        "TK_DASHBOARD_URL",
        "-e",
        "TK_DEBUG",
        "-e",
        "TK_MCP_SHTTP_AUTH_TOKEN",
        "docker.io/kubeshop/mcp-server:2.15.0"
      ],
      "env": {
        "TK_ACCESS_TOKEN": "your-value",
        "TK_ORG_ID": "your-value",
        "TK_ENV_ID": "your-value",
        "TK_CONTROL_PLANE_URL": "your-value",
        "TK_DASHBOARD_URL": "your-value",
        "TK_DEBUG": "your-value",
        "TK_MCP_SHTTP_AUTH_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http testkube 'https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp'

Or run it on your computer

claude mcp add testkube --env TK_ACCESS_TOKEN=your-value --env TK_ORG_ID=your-value --env TK_ENV_ID=your-value --env TK_CONTROL_PLANE_URL=your-value --env TK_DASHBOARD_URL=your-value --env TK_DEBUG=your-value --env TK_MCP_SHTTP_AUTH_TOKEN=your-value -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID -e TK_CONTROL_PLANE_URL -e TK_DASHBOARD_URL -e TK_DEBUG -e TK_MCP_SHTTP_AUTH_TOKEN docker.io/kubeshop/mcp-server:2.15.0

Fill in the empty values before running it.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "testkube": {
      "url": "https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "testkube": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TK_ACCESS_TOKEN",
        "-e",
        "TK_ORG_ID",
        "-e",
        "TK_ENV_ID",
        "-e",
        "TK_CONTROL_PLANE_URL",
        "-e",
        "TK_DASHBOARD_URL",
        "-e",
        "TK_DEBUG",
        "-e",
        "TK_MCP_SHTTP_AUTH_TOKEN",
        "docker.io/kubeshop/mcp-server:2.15.0"
      ],
      "env": {
        "TK_ACCESS_TOKEN": "your-value",
        "TK_ORG_ID": "your-value",
        "TK_ENV_ID": "your-value",
        "TK_CONTROL_PLANE_URL": "your-value",
        "TK_DASHBOARD_URL": "your-value",
        "TK_DEBUG": "your-value",
        "TK_MCP_SHTTP_AUTH_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "testkube": {
      "type": "http",
      "url": "https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "testkube": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TK_ACCESS_TOKEN",
        "-e",
        "TK_ORG_ID",
        "-e",
        "TK_ENV_ID",
        "-e",
        "TK_CONTROL_PLANE_URL",
        "-e",
        "TK_DASHBOARD_URL",
        "-e",
        "TK_DEBUG",
        "-e",
        "TK_MCP_SHTTP_AUTH_TOKEN",
        "docker.io/kubeshop/mcp-server:2.15.0"
      ],
      "env": {
        "TK_ACCESS_TOKEN": "your-value",
        "TK_ORG_ID": "your-value",
        "TK_ENV_ID": "your-value",
        "TK_CONTROL_PLANE_URL": "your-value",
        "TK_DASHBOARD_URL": "your-value",
        "TK_DEBUG": "your-value",
        "TK_MCP_SHTTP_AUTH_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • TK_ACCESS_TOKEN secret required env
    Testkube access token for authentication
  • TK_ORG_ID required env
    Testkube organization ID
  • TK_ENV_ID required env
    Testkube environment ID
  • TK_CONTROL_PLANE_URL env
    Testkube Control Plane URL (default: https://api.testkube.io)
  • TK_DASHBOARD_URL env
    Testkube Dashboard URL
  • TK_DEBUG env
    Enable debug mode (default: false)
  • TK_MCP_SHTTP_AUTH_TOKEN secret env
    Separate inbound bearer token, required only when explicitly using --transport=shttp; not needed for default stdio

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The address needs your own values, so we cannot read the tool list for you.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kubeshop, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    The address needs your own account values, so we cannot check it for you

  • – Not applicable

    Sign-in with OAuth

    The address needs your own account values, so we cannot check it for you

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 18436 servers in this category
  • Published to the registry more recently than 80% of the other 18436 servers in this category
  • Basic checks equal to or better than 100% of the other 18436 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Testkube MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_MCP_SHTTP_AUTH_TOKEN

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.15.0) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 3 days ago
Install

Tethered Trust

by tetheredtrust.com

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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!

Ask PopNx