Testkube Mcp
- 1.6k repo stars
- Updated July 27, 2026
- kubeshop/testkube
io.github.kubeshop/testkube-mcp is a MCP server that lets AI assistants manage Testkube test workflows, executions, and artifacts via the control plane API.
About
io.github.kubeshop/testkube-mcp is a Model Context Protocol server that connects AI assistants to the Testkube control plane so developers and small teams can manage test workflows, start or review executions, and work with artifacts through natural language. You install it when Kubernetes or cloud-native testing is already part of your pipeline and you want agents to answer questions like which workflow failed last night or fetch logs without opening another dashboard tab. Configuration centers on a Testkube access token, organization ID, and environment ID, with optional overrides for API and dashboard URLs. It matters for discipline: agents can propose reruns, summarize flaky suites, and keep release checklists honest before you tag a version. This is an MCP integration into Testkube, not a replacement for defining tests in your repo.
- Manage Testkube test workflows and executions from Claude Code, Cursor, or Codex via stdio MCP
- Authenticate with TK_ACCESS_TOKEN plus org and environment IDs against the Testkube control plane
- Run against docker.io/kubeshop/mcp-server:2.9.1 or configure TK_CONTROL_PLANE_URL and dashboard URLs
- Surface execution status and artifacts for AI-assisted triage after CI or pre-release gates
- Pairs with Kubernetes-native Testkube setups indie teams already use for API and integration suites
Testkube Mcp by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
claude mcp add TestkubeMcp -- npx -y kubeshop/testkubeAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1.6k |
|---|---|
| Last updated | July 27, 2026 |
| Repository | kubeshop/testkube ↗ |
What it does
Let your coding agent trigger Testkube workflows, inspect executions, and pull test artifacts without leaving the editor.
Who is it for?
Best when you're shipping on Kubernetes and already use Testkube and want agent-driven visibility into workflows and executions.
Skip if: Skip if you have no Testkube org or and only need local unit tests without a control plane.
What you get
After you register the server with your token and env IDs, your agent can query and drive Testkube workflows and artifacts from the same session where you fix code.
- Agent-callable access to Testkube workflow and execution operations
- Artifact and run context surfaced inside the coding session
- Reduced context switching between agent chat and Testkube dashboard
By the numbers
- Server schema version 2.9.1
- OCI package docker.io/kubeshop/mcp-server:2.9.1 with stdio transport
- Required secrets: TK_ACCESS_TOKEN; required IDs: TK_ORG_ID, TK_ENV_ID
README.md
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:
- CONTRIBUTING.md - contribution workflow, coding standards, and PR process
- DEVELOPMENT.md - local setup with Tilt and day-to-day development loop
- ARCHITECTURE.md - high-level system design and key code paths
Shout-out to our contributors 🎉 - you're great!
- ⭐️ @lreimer - K6 executor Gradle executor Maven executor
- ⭐️ @jdborneman-terminus - Ginkgo executor
- ️⭐️ @abhishek9686
- ⭐️ @ancosma
- ⭐️ @Stupremee
- ⭐️ @artem-zherdiev-ingio
- ⭐️ @chooco13 - Playwright executor
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!
Recommended MCP Servers
0piFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.
100Hires AI ATS & Recruitment SoftwareOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.
123elec McpInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.
1stayHotel booking MCP server.2
2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.43D MeshWeaverMesh spatial optimizer reducing geometric overhead in 3D assets.How it compares
MCP bridge to Testkube’s test orchestration API, not an agent skill that writes test cases for you.
FAQ
Who is testkube-mcp for?
and small-team developers on Testkube who want Claude Code, Cursor, or Codex to inspect and manage test workflows without leaving the agent.
When should I use testkube-mcp?
Use it during Ship when you gate releases on Testkube executions and need the agent to check status, artifacts, or workflow config on demand.
How do I add testkube-mcp to my agent?
Run the kubeshop MCP server image or stdio package, set TK_ACCESS_TOKEN, TK_ORG_ID, and TK_ENV_ID, then add the server entry in your client’s MCP config.