Comparison

Temporal vs io.github.kubeshop/testkube-mcp

Temporal is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.kubeshop/testkube-mcp is an MCP server published by kubeshop. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace	Temporal	io.github.kubeshop/testkube-mcp
Docker MCP Catalog	Listed Version: sha256:24aeaca7c458 Forks (GitHub): 20 Pulls (Docker Hub): 41 363 Stars (Docker Hub): 2 Stars (GitHub): 60 Not marked · First seen 2026-10-11	Listed Version: sha256:43aa88f2d416 Forks (GitHub): 180 Pulls (Docker Hub): 33 640 Stars (Docker Hub): 0 Stars (GitHub): 1 669 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 2.14.0 Forks (GitHub): 180 Stars (GitHub): 1 669 Not marked · First seen 2026-10-11

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Temporal vs io.github.kubeshop/testkube-mcp
Fact	Temporal	io.github.kubeshop/testkube-mcp
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	60 (worse)	1 669 (better)
Pulls (Docker Hub) (differs)	41 363 (better)	33 640 (worse)
Forks (GitHub) (differs)	20 (worse)	180 (better)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/temporal)	Remote server or your machine
Transport (differs)	stdio	Streamable HTTP, stdio
Tools it declares (differs)	29	28
Environment variables it asks for (differs)	6, secrets among them: 1	9, secrets among them: 1
Licence (differs)	Apache-2.0	NOASSERTION
Repository (differs)	github.com/gethosthewalrus/temporal-mcp	github.com/kubeshop/testkube
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 32 h ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Temporal

In its own words, on Docker MCP Catalog:

Manage Temporal workflows, schedules, namespaces, task queues, and workflow execution history from MCP clients.

io.github.kubeshop/testkube-mcp

In its own words, on Official MCP Registry:

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

How to run each

Temporal As a local MCP server: Docker image

Claude Code

claude mcp add --env "TEMPORAL_API_KEY=<YOUR_TEMPORAL_API_KEY>" --transport stdio temporal -- docker run -i --rm -e TEMPORAL_API_KEY mcp/temporal

Requires: TEMPORAL_API_KEY (secret)

io.github.kubeshop/testkube-mcp As a local MCP server: Docker image

Claude Code

claude mcp add --env "TK_ACCESS_TOKEN=<YOUR_TK_ACCESS_TOKEN>" --env "TK_ENV_ID=<YOUR_TK_ENV_ID>" --env "TK_ORG_ID=<YOUR_TK_ORG_ID>" --transport stdio testkube -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ENV_ID -e TK_ORG_ID mcp/testkube

Requires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.kubeshop/testkube-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

Only Temporal declares

batch_cancel
batch_cancel_activities
batch_signal
batch_terminate
batch_terminate_activities
cancel_activity
cancel_workflow
continue_as_new
count_activities
create_schedule
delete_schedule
describe_activity

Show the remaining 16

describe_workflow
execute_activity
get_activity_result
get_workflow_history
get_workflow_result
list_activities
list_schedules
pause_schedule
query_workflow
signal_workflow
start_activity
start_workflow
terminate_activity
terminate_workflow
trigger_schedule
unpause_schedule

Only io.github.kubeshop/testkube-mcp declares

abort_workflow_execution
build_dashboard_url
create_workflow
create_workflowtemplate
fetch_execution_logs
get_execution_info
get_execution_schema
get_workflow
get_workflow_definition
get_workflow_execution_metrics
get_workflow_metrics
get_workflow_resource_history

Show the remaining 15

get_workflow_schema
get_workflowtemplate_definition
list_agents
list_artifacts
list_executions
list_labels
list_resource_groups
list_workflowtemplates
lookup_execution_id
read_artifact
run_workflow
update_execution_tags
update_workflow
update_workflowtemplate
wait_for_executions

Both declare

list_workflows

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Temporal asks for

TEMPORAL_API_KEY (secret)
TEMPORAL_HOST
TEMPORAL_NAMESPACE
TEMPORAL_TLS_CLIENT_CERT_PATH
TEMPORAL_TLS_CLIENT_KEY_PATH
TEMPORAL_TLS_ENABLED

Only io.github.kubeshop/testkube-mcp asks for

TK_ACCESS_TOKEN (secret)
TK_CONTROL_PLANE_URL
TK_DASHBOARD_URL
TK_DEBUG
TK_ENV_ID (secret)
TK_MCP_SHTTP_HOST
TK_MCP_SHTTP_PORT
TK_MCP_TRANSPORT
TK_ORG_ID (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Temporal · What it can do: io.github.kubeshop/testkube-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on 2026-10-17. We publish no contact details for plugin publishers.