Testkube
mcpotherio.docker.mcp/testkube · vd392deb5bf68
- Listed as io.github.kubeshop/testkube-mcp: another feed's entry of the same server. This one stays reachable, with its own record, tools and recipes, but the server list and the search show that one.
The Testkube MCP Server exposes continuous testing capabilities (test orchestration, execution, troubleshooting and anlysis) to AI tools and workflows
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
#!/usr/bin/env bash
# testkube (io.docker.mcp/testkube), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-testkube.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-testkube -p 127.0.0.1:${PORT}:8000 -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID mcp/testkube
[Unit]
Description=MCP server testkube (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/testkube
WorkingDirectory=/var/lib/mcp/testkube
ExecStart=/opt/mcp/my-agent/bin/testkube.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/testkube
[Install]
WantedBy=multi-user.target
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
docker run --rm -p 127.0.0.1:8101:8000 -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID mcp/testkube
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T23:18:34+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
testkube:
image: mcp/testkube
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
instead.'
environment:
TK_ACCESS_TOKEN: ${TK_ACCESS_TOKEN}
TK_ORG_ID: ${TK_ORG_ID}
TK_ENV_ID: ${TK_ENV_ID}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T23:18:34+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: testkube
namespace: mcp
labels: &id001
app: testkube
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: testkube
image: mcp/testkube
ports:
- containerPort: 8000
name: http
env:
- name: TK_ACCESS_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TK_ACCESS_TOKEN
- name: TK_ORG_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TK_ORG_ID
- name: TK_ENV_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TK_ENV_ID
---
apiVersion: v1
kind: Service
metadata:
name: testkube
namespace: mcp
spec:
selector:
app: testkube
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-18T23:18:34+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
testkube:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: testkube
image: mcp/testkube
ports:
- containerPort: 8000
name: http
env:
- name: TK_ACCESS_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TK_ACCESS_TOKEN
- name: TK_ORG_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TK_ORG_ID
- name: TK_ENV_ID
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TK_ENV_ID
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsdocker run -i --rm -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID mcp/testkube
{
"mcpServers": {
"testkube": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"mcp/testkube"
],
"env": {
"TK_ACCESS_TOKEN": "${TK_ACCESS_TOKEN}",
"TK_ORG_ID": "${TK_ORG_ID}",
"TK_ENV_ID": "${TK_ENV_ID}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add testkube -e "TK_ACCESS_TOKEN=${TK_ACCESS_TOKEN}" -e "TK_ORG_ID=${TK_ORG_ID}" -e "TK_ENV_ID=${TK_ENV_ID}" -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ORG_ID -e TK_ENV_ID mcp/testkube
{
"mcpServers": {
"testkube": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"mcp/testkube"
],
"env": {
"TK_ACCESS_TOKEN": "${TK_ACCESS_TOKEN}",
"TK_ORG_ID": "${TK_ORG_ID}",
"TK_ENV_ID": "${TK_ENV_ID}"
}
}
}
}
{
"servers": {
"testkube": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TK_ACCESS_TOKEN",
"-e",
"TK_ORG_ID",
"-e",
"TK_ENV_ID",
"mcp/testkube"
],
"env": {
"TK_ACCESS_TOKEN": "${TK_ACCESS_TOKEN}",
"TK_ORG_ID": "${TK_ORG_ID}",
"TK_ENV_ID": "${TK_ENV_ID}"
}
}
}
}
name: my-agent target: local servers: - hub: io.docker.mcp/testkube
- listed as io.github.kubeshop/testkube-mcp: another feed's entry of the same server, which the catalogue shows instead
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.