Runs a command in a throwaway Kubernetes pod and returns exit code, output and artifacts.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-inhuman-mcp-k8s-ephemeral-job": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Public OSS MCP server (Go, MIT) that spawns an ephemeral Kubernetes Job/pod from a caller-chosen image, runs a command inside it, returns exit_code / stdout / artifacts, and deletes the pod. The server builds the pod manifest in code — the caller passes parameters
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for kubernetes management commands
Upload, organize, search, and transform images, videos, and files with AI-powered tools.
Static infrastructure analysis via MCP: databases, AWS services, IaC, and code patterns.
Official Sevalla MCP — full PaaS API access through just 2 tools.
MCP Security Weekly
Get CVE alerts and security updates for io.github.inhuman/mcp-k8s-ephemeral-job and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
English | Русский
Public OSS MCP server (Go, MIT) that spawns an ephemeral Kubernetes Job/pod from a
caller-chosen image, runs a command inside it, returns exit_code / stdout / artifacts, and
deletes the pod. The server builds the pod manifest in code — the caller passes parameters
only, never raw YAML.
It is the "operating room" counterpart to mcp-exec (the
"scalpel"): where mcp-exec runs a single Python file in a locked-down, network-less sandbox in
milliseconds, this one spins up a full pod with the toolchain/image you choose, controlled
network (clone repos, pull deps), long tasks and file artifacts out. They complement each
other.
Works over three transports — stdio / HTTP / SSE — with an identical tool set everywhere
(official modelcontextprotocol/go-sdk).
run_job — run and waitInput: { image (required), command (required), files?, env?, limits?, timeout_s?, workdir?, clone? }
Output: { exit_code, stdout, stderr, duration_ms, status, artifacts, truncated }
status is one of succeeded / failed / timeout / error. A non-zero exit_code or a
timeout is a normal result, not a tool error. Only invalid input (empty image/command,
image not in the allowlist, bad file path) is a tool-call error.stdout carries the container's combined stdout+stderr — Kubernetes merges the two streams in
pod logs. stderr is reserved and always empty, so adding stream separation later stays
backward-compatible.truncated flag is set.submit_job / fetch_job — run in the backgroundsubmit_job takes the same arguments as run_job but returns a job_token immediately;
fetch_job collects the result later. This is what lets an agent start a long job (a full test
battery, a build) and keep working instead of idling inside one synchronous call for its whole
wall-clo