
Testkube MCP server
https://api.testkube.io/organizations/%7Borganization_id%7D/environments/%7Benvironment_id%7D/mcpkubeshop/testkubeLets your AI assistant create, run and debug Testkube test workflows, read logs and artifacts, and manage Insights boards.
This is Testkube's own MCP server for its test orchestration platform. The easiest way is the hosted address, which signs you in with OAuth in your browser. You can also run it with the Testkube CLI or the Docker image.
Your assistant can write and run test workflows, read logs and artifacts, and build Insights boards. Workflows run real steps on your Testkube runners, so it needs care.
Good for
- QA and platform engineers who run tests on Kubernetes with Testkube
- Developers who want an agent to debug failed test runs
- Teams that track test reliability and performance trends
Works in
14 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports hosted MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports hosted MCP servers.
Install testkube MCP
Claude Code
- 1
Copy this prompt.
Add the testkube MCP server to Claude Code. Run this command: claude mcp add --transport http testkube https://api.testkube.io/organizations/<organization_id>/environments/<environment_id>/mcp Ask me for TK_ACCESS_TOKEN, TK_ORG_ID, TK_ENV_ID and only put the values in that config, nowhere else. Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Testkube account, Organization and environment IDs.
Replace <organization_id> and <environment_id> with the IDs from your Testkube dashboard. The hosted endpoint signs you in with OAuth in the browser, and Testkube names Claude Code, VS Code and Cursor for it. Docker runs the kubeshop/mcp-server image and needs an API token, which cannot use the board tools.
From the vendor's docs. Source.
Tools
Lists your test workflows
Lists Testkube test workflows with filters for resource group, labels and text, and returns names, descriptions and recent status.
Try: “List my test workflows and their recent execution status.”
Read ·
list_workflowsShows one workflow in detail
Returns one workflow with its execution history, health metrics and current status.
Try: “How is the api-tests workflow doing?”
Read ·
get_workflowShows a workflow's YAML
Returns the full YAML definition of a workflow, including steps and the config options it accepts.
Try: “Show me the YAML of the api-tests workflow.”
Read ·
get_workflow_definitionShows workflow reliability numbers
Returns execution counts, health scores, pass rates and performance data for a workflow.
Try: “What is the pass rate of api-tests over time?”
Read ·
get_workflow_metricsCreates a test workflow
Creates a workflow from YAML. It can be run right away, and its steps run in your environment.
Try: “Create a workflow that runs my Python API tests.”
Runs code ·
create_workflowChanges a test workflow
Replaces an existing workflow with a new YAML definition, and it takes effect immediately.
Try: “Update api-tests to use the latest Python image.”
Runs code ·
update_workflowRuns a test workflow
Starts a workflow, with optional config values and a chosen runner. The workflow's steps run on your Testkube runner.
Try: “Run api-tests on the staging runner.”
Runs code ·
run_workflowLists workflow templates
Lists reusable workflow templates with names, descriptions and labels.
Try: “What workflow templates do we have?”
Read ·
list_workflowtemplatesShows a template's YAML
Returns the full YAML of one workflow template.
Try: “Show the YAML of the k6 template.”
Read ·
get_workflowtemplate_definitionCreates a workflow template
Creates a reusable template from YAML. Workflows can use it right away.
Try: “Create a template for k6 performance tests.”
Write ·
create_workflowtemplateChanges a workflow template
Replaces a template's definition. Workflows that use the template pick up the change.
Try: “Update the k6 template to a newer image.”
Write ·
update_workflowtemplateSearches many workflow definitions
Runs a JSONPath query across all workflow definitions, for example to find which use a certain image. It only registers when the control plane supports it.
Try: “Which workflows use the node:18 image?”
Read ·
query_workflowsSearches many execution records
Runs a JSONPath query across execution records from many workflows, such as all failures or durations. It only registers when the control plane supports it.
Try: “Show all failed executions from the last week.”
Read ·
query_executionsShows the workflow YAML schema
Returns the fields and types a TestWorkflow definition allows.
Try: “What fields can a TestWorkflow have?”
Read ·
get_workflow_schemaShows the execution data schema
Returns the fields and types of execution data, to help write queries.
Try: “What does an execution record contain?”
Read ·
get_execution_schemaLists labels and values
Lists workflow labels and their values, useful for filtering other calls.
Try: “What labels are used on my workflows?”
Read ·
list_labelsLists resource groups
Lists the resource groups in your organization.
Try: “Which resource groups exist?”
Read ·
list_resource_groupsLists runners
Lists the agents (runners) that can run workflows, with type, capabilities and status.
Try: “Which runners can I run tests on?”
Read ·
list_agentsReads execution logs
Returns the last 100 lines of an execution's logs by default, and can search the full log by text.
Try: “Show the logs of the last failed api-tests run.”
Read ·
fetch_execution_logsLists test executions
Lists executions with filters for workflow, status, dates, labels, tags and text.
Try: “Show failed executions from yesterday.”
Read ·
list_executionsFinds an execution id by name
Looks up an execution's id from its name.
Try: “What is the id of execution api-tests-123?”
Read ·
lookup_execution_idShows one execution in detail
Returns status, timing, results, configuration and workers of an execution, and the failing step for one that did not pass.
Try: “Why did execution api-tests-123 fail?”
Read ·
get_execution_infoShows resource use of one run
Returns CPU, memory, disk and network metrics over time for a single execution.
Try: “Show CPU and memory use for execution api-tests-123.”
Read ·
get_workflow_execution_metricsCompares resource use across runs
Computes statistics, trends and outliers for CPU, memory, disk and network across recent runs of a workflow.
Try: “Is api-tests using more memory over time?”
Read ·
get_workflow_resource_historyWaits for runs to finish
Polls a list of executions until they finish and returns their final status.
Try: “Run both workflows and wait until they finish.”
Read ·
wait_for_executionsStops a running execution
Aborts a running execution and marks it aborted.
Try: “Abort the stuck api-tests run.”
Delete ·
abort_workflow_executionSets tags on an execution
Replaces all tags on an execution with the ones you give. An empty set clears them.
Try: “Tag this run env=prod and bug=found.”
Write ·
update_execution_tagsLists files from a run
Lists the files, reports and logs an execution produced.
Try: “What artifacts did execution api-tests-123 produce?”
Read ·
list_artifactsReads an artifact file
Returns up to 200 lines of an artifact per request, and a summary for binary files.
Try: “Read the junit report from that run.”
Read ·
read_artifactFinds available test metrics
Lists the metric series parsed from k6, JMeter, Artillery, JUnit and Influx reports.
Try: “Which performance metrics are tracked?”
Read ·
list_insight_seriesLists metric names
Lists the distinct metric keys available, such as 95th percentile response time.
Try: “What metric names can I query?”
Read ·
list_insight_metric_keysCharts a metric over time
Returns a metric as a time series so you can see values and trends.
Try: “Show p95 response time for the last month.”
Read ·
get_insight_metric_seriesFinds runs behind a metric
Lists the executions that produced a given metric, newest first.
Try: “Which runs produced that latency spike?”
Read ·
list_insight_executionsLists Insights boards
Lists the dashboards visible to you, shared and private.
Try: “What Insights boards do I have?”
Read ·
list_boardsShows a board and its reports
Returns a board with its reports in order and its layout.
Try: “Show the contents of the API health board.”
Read ·
get_boardRuns a board's reports
Runs each report's query and returns the numbers with the query and date range used.
Try: “Render the API health board for last month.”
Read ·
render_boardCreates a board
Creates an empty dashboard, shared with the organization unless you make it private.
Try: “Create a private board called API health.”
Write ·
create_boardChanges a board
Changes a board's name, description, slug, visibility or layout.
Try: “Make the API health board shared.”
Write ·
update_boardAdds a report to a board
Adds a pass/fail, executions, workflows or time-series chart to a board.
Try: “Add a pass/fail chart for api-tests to the board.”
Write ·
add_board_reportChanges a report
Changes a report's name, description, kind or settings, merging new settings into the old ones.
Try: “Rename the report to Weekly pass rate.”
Write ·
update_board_reportRemoves a report
Removes a report from a board. This cannot be undone.
Try: “Remove the latency report from the board.”
Delete ·
remove_board_reportDeletes a board
Permanently deletes a board and all its reports. A shared board needs an organization admin.
Try: “Delete the old API health board.”
Delete ·
delete_boardBuilds a dashboard link
Builds a link to a workflow or an execution in the Testkube dashboard, optionally to a log step.
Try: “Give me a link to the failed run.”
Read ·
build_dashboard_url
Read from the source code
Permissions
high risk · 5 things to watch · 1 advisory
High risk
It can create and run test workflows that execute steps on your runners, and it can delete boards and abort runs. Use an environment you can afford to lose, and keep your client set to ask before it creates or runs a workflow.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It can create and run workflows that execute code
create_workflow, update_workflow and run_workflow write and start workflows whose steps run on your Testkube runners. There is no read-only switch, so approve each call. github.com
It can delete boards and abort runs
delete_board removes a board and all its reports for good, and abort_workflow_execution stops a running test. Deleting a shared board needs an organization admin. docs.testkube.io
Docker tokens cannot use the board tools
Board tools need a signed-in user, so they fail with an API token in Docker. This is a feature limit, but it also means a hosted OAuth login carries your full user rights. docs.testkube.io
The server sends usage events to Testkube
Telemetry is on by default and sends the tool name, duration and error status. You can turn it off in the Testkube CLI config. github.com
Standalone HTTP mode needs its own token
The optional shttp mode binds to localhost by default and requires a separate inbound bearer token (TK_MCP_SHTTP_AUTH_TOKEN). Bind externally only behind TLS. github.com
Security advisories
Technical details
| Talks to | api.testkube.io |
|---|---|
| Scopes |
|
Questions
Is the Testkube MCP server official?
Yes. Testkube (Kubeshop) builds it in its own repository, and the docs describe it as the Testkube MCP server.
Do I need an API key?
Not for the hosted endpoint, which signs you in with OAuth in the browser. The Docker image needs a Testkube access token, an organization ID and an environment ID. The CLI uses testkube login or an API key.
What is the Testkube MCP server URL?
It is https://api.testkube.io/organizations/<organization_id>/environments/<environment_id>/mcp. Fill in the IDs from your Testkube dashboard.
Hosted, CLI or Docker, which should I pick?
Testkube recommends the hosted endpoint because it needs no install. Use the CLI for local development, and Docker for CI pipelines or containers.
Can it run read-only?
No read-only switch is documented. Most tools read, but workflow, template and board tools write, and run_workflow starts test steps.
Can it delete things?
Yes. It can delete an Insights board with all its reports and remove a single report, and it can abort running executions. It has no tool to delete workflows.
Why are the board tools missing or failing?
Board tools need a signed-in user, so they fail with an API token. Use the hosted endpoint or the CLI after testkube login.
Is the page showing every tool?
It shows all 43 tools the 2.15.0 server can register. Two query tools only register when your control plane supports them, and the insight tools return an error on an older control plane.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
kubeshop/mcp-server- Registry
- Docker
- Endpoint
https://api.testkube.io/organizations/%7Borganization_id%7D/environments/%7Benvironment_id%7D/mcp- Transport
- stdio, Streamable HTTP
- Auth
- OAuth
- Version
- 2.15.0
- License
- MIT
- Last commit
- Oct 31, 2026
- Open issues
- 19
- Listed in
- Official MCP registry, Docker MCP Catalog
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 5Hide
- Testkube MCP Server docs · docs.testkube.io
- Testkube hosted MCP endpoint · docs.testkube.io
- Testkube MCP package README (2.15.0) · github.com
- Testkube MCP server source (2.15.0) · github.com
- Testkube MCP Docker README · github.com