Testkube MCP Server

[olensmar]

---

name: Add a new MCP server
about: Requests for adding a new MCP server to the Docker Catalog
title: "Official Testkube MCP Server"
labels: submission
assignees: ""

Hope I got this right 😅

MCP Server Information

Testkube
https://github.com/kubeshop/testkube - in the build/mcp-server folder
Exposes Testkubes' test execution and orchestration capabilities for AI automation

Basic Requirements

• Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license)
• MCP Compliant: Implements MCP API specification
• Active Development: Recent commits and maintained
• Docker Artifact: Dockerfile (in the build/mcp-server folder)
• Documentation: Basic README and setup instructions (in the build/mcp-server folder)
• Security Contact: Method for reporting security issues

Submitter Checklist

• This server meets the basic requirements listed above
• I understand this will undergo automated and manual review.
• I have tested the MCP Server using task validate -- --name SERVER_NAME
• I have built the MCP Server using task build -- --tools SERVER_NAME

[olensmar]

I couldn't find a way to specify the path to the Dockerfile in our repo (/build/mcp-server/Dockerfile), so I provided our own Docker image on DockerHub instead - if there is a way to provide this then I'm happy to update accordingly 🙏

[olensmar]

Question: our mcp-server supports both stdio and shttp - with stdio being default. Should we provide run configuration for shttp also / instead?

[ipedrazas]

Hey, to add the path of your Dockerfile, you just need to add the directory attribute in your source object:

source:
  project: https://github.com/kubeshop/testkube
  directory: build/mcp-server

To add the shttp configuration, adding an environment variable would be the easiest.

[olensmar]

thanks @ipedrazas - updating!