autogen-kubernetes-mcp-v0.6.0

What's Changed

Command-line Arguments

Command-line arguments are used when creating PodCommandLineCodeExecutor/PodJupyterCodeExecutor and MCP server.

type arguments: jupyter type creates PodJupyterCodeExecutor for python code executor tool.

MCP server have to run in same kubernetes cluster because PodJupyterCodeExecutor only uses service FQDN to connect jupyter server.

Not validated for non-text outputs yet.

flowchart LR
  subgraph K8sCluster["Kubernetes Cluster"]
    E[PodJupyterCodeExecutor]
    J[JupyterServerPod]
  end

  E --generate--> J

All the arguments are optional

Argument	Description	Default
type	Code Executor type, commandline(stateless), jupyter(stateful) supported
--host	MCP server host address	0.0.0.0
--port	MCP server port	8000
--kubeconfig	Path to the kubeconfig file	None(auto-detected)
--image	Pod container image name	None
--pod-name	Pod name	(auto-generated)
--timeout	Code execution timeout(seconds)	60
--workspace-path	Path inside the container where scripts are stored	/workspace
--namespace, -n	Kubernetes namespace for Pod creation	default
--volume	Kubernetes volume to mount into the Pod/container, accepts YAML format string, YAML file path	None
--pod-spec	Custom Pod spec definition(YAML format string, YAML file path)	None
--command	Custom executor container command	None
--args	Custom executor container arguments	None

example

commandline type

uvx autogen-kubernetes-mcp commandline --namespace my-namespace --image python:3.11-slim

python -m autogen_kubernetes_mcp commandline --namespace my-namespace --image python:3.11-slim

jupyter type

uvx autogen-kubernetes-mcp jupyter --namespace my-namespace --timeout 120

python -m autogen_kubernetes_mcp jupyter --namespace my-namespace --timeout 120

Full Changelog: v0.5.2...autogen-kubernetes-mcp-v0.6.0