原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Testkube MCP

作者:kubeshop版本 2.15.0i★ –i电脑或云端
注册名称io.github.kubeshop/testkube-mcp

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 电脑或云端
  • 传输方式: stdio, Streamable HTTP
  • 分类: 其他
  • 你需要填写:TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_MCP_SHTTP_AUTH_TOKEN

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
  • 需要你自己填写: TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_CONTROL_PLANE_URL, TK_DASHBOARD_URL, TK_DEBUG, TK_MCP_SHTTP_AUTH_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp

地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

或者在你的电脑上运行

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

运行前请先填写空着的值。

地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp

地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

这个地址需要填入你自己的值,所以我们无法替你读取工具列表。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 kubeshop 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    这个地址需要填入你自己的账户信息,所以我们无法替你检查

  • – 不适用

    使用 OAuth 登录

    这个地址需要填入你自己的账户信息,所以我们无法替你检查

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18444 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18444 个服务器的 80% 更新
  • 基础检查结果等于或优于此分类中其他 18444 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Testkube MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID, TK_MCP_SHTTP_AUTH_TOKEN

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(2.15.0)于10天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Tethered Trust

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

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

作者:formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

Remote Desktop Commander

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

作者:desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

Tethered Trust

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

作者:tetheredtrust.com非常新今天更新

在云端运行✓ tetheredtrust.com

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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!

问 PopNx