DynamicEnv MCP Server

What is DynamicEnv MCP Server?

DynamicEnv MCP Server is a high-performance Kubernetes MCP server that provides an AI-friendly API interface over DynamicEnv Custom Resources. It enables real-time tracking, intelligent debugging, and simplified cleanup for dynamic environments used in development, testing, and ephemeral workloads. Built with an async-first architecture, it integrates seamlessly with the Model Context Protocol (MCP) to empower developers and AI agents to manage K8s-based environments safely and efficiently.

How to use DynamicEnv MCP Server?

Clone the repository, create a Python virtual environment, and install dependencies with uv pip install -e .. Then install MCP tools (pip install "mcp[cli]") and start the server using mcp dev server.py, mcp install server.py, or mcp run server.py. The core CLI tools are List (view DynamicEnvs with filtering), Status (inspect deployments, pods, logs), and Delete (safely remove a DynamicEnv instance).

Key features of DynamicEnv MCP Server

• List and filter DynamicEnv instances by namespace, state, or deployment status
• Live status monitoring with async updates and progress reporting
• Safe deletion of environments with dependency checks
• Secure K8s authentication using in-cluster or kubeconfig credentials
• Pod insights, deployment health, and optional log access
• AI-ready interface via the Model Context Protocol

Use cases of DynamicEnv MCP Server

• Managing dynamic environments for development and testing workflows
• Automating cleanup of ephemeral environments in CI/CD pipelines
• Enabling AI-driven DevOps tools to monitor and debug K8s resources
• Providing real-time observability for multi-service dynamic environments

FAQ from DynamicEnv MCP Server

What is a DynamicEnv?

DynamicEnv is a Kubernetes Custom Resource (CRD) that encapsulates an entire dynamic environment setup, including multiple interdependent services, service-specific configurations, routing rules, and resource constraints.

What are the runtime requirements?

The server requires Python 3.9 or later and a Kubernetes cluster. Authentication can be done via in-cluster credentials or a local kubeconfig file.

How does the server handle authentication?

It uses secure K8s authentication methods, supporting both in-cluster (service account) and kubeconfig-based credentials.

What CLI tools are provided?

The core tools are List (view and filter DynamicEnvs), Status (inspect deployments, pods, and logs), and Delete (safely remove a DynamicEnv instance with dependency checks).

Is the server AI‑ready?

Yes, it implements the Model Context Protocol (MCP), allowing AI tools to subscribe to real-time updates, manage long-running operations with progress tracking, and work safely via validation and structured context.