chore(mcp): remove the mcp

This MCP is unmaintained and old compared with datumctl-mcp so it is
time to send this on vacation!

Author: gianarb

README.md

@@ -12,7 +12,6 @@ Use `datumctl` to manage your Datum Cloud resources, authenticate securely, and
 *   **Multi-User Support:** Manage credentials for multiple Datum Cloud user accounts.
 *   **Resource Management:** Interact with Datum Cloud resources (e.g., list organizations).
 *   **Kubernetes Integration:** Seamlessly configure `kubectl` to use your Datum Cloud credentials for accessing Kubernetes clusters.
-*   **MCP Server (optional):** Start an MCP server (`datumctl mcp`) for Datum Cloud so AI agents (e.g., Claude) can discover resources, inspect schemas, validate manifests, and perform CRUD operations via server-side dry-run.
 *   **Cross-Platform:** Pre-built binaries available for Linux, macOS, and Windows.
 
 ## Getting Started
@@ -46,10 +45,6 @@ See the [Installation Guide](https://www.datum.net/docs/quickstart/datumctl/) fo
     ```
     Now you can use `kubectl` to interact with your Datum Cloud control plane.
 
-### MCP Setup
-
-MCP can target either an **organization** or **project** control plane. For maximum flexibility, we recommend starting with an organization context.
-
 **A) If you already have a project:**
 ```bash
 # Ensure your kube context points at an organization control plane
@@ -82,75 +77,6 @@ kubectl wait --for=condition=Ready --timeout=15m project/$PRJ_ID
 echo "Project ready: $PRJ_ID"
 ```
 
-#### MCP subcommand (optional)
-
-Start the Model Context Protocol (MCP) server targeting a specific Datum Cloud context:
-```bash
-# Exactly one of --organization or --project is required.
-datumctl mcp --organization <org-id> --namespace <ns> [--port 8080]
-# or
-datumctl mcp --project <project-id> --namespace <ns> [--port 8080]
-```
-
-##### Available Tools
-
-- **Discovery:** `list_crds`, `get_crd` - Discover and inspect Custom Resource Definitions
-- **Validation:** `validate_yaml` - Validate manifests via server-side dry-run
-- **Context:** `change_context` - Switch between organization and project contexts
-- **CRUD Operations:** `create_resource`, `get_resource`, `update_resource`, `delete_resource`, `list_resources`
-- **Safety:** All write operations default to dry-run mode; use `dryRun: false` to apply changes
-
-##### Startup & safety
-
-- **Preflight:** On startup, `datumctl mcp` verifies connectivity and auth by calling Kubernetes discovery (e.g., `GET /version`). If this check fails, the server exits.
-- **Dry-run by default:** All write operations use server-side dry-run (`dryRun=true`) by default for safety.
-
-> [!NOTE]
-> The MCP server builds its own Kubernetes connection for the selected Datum context; it does **not** depend on your local kubeconfig or `--kube-context`. Provide either `--organization` or `--project`.
-
-##### Scope: organization vs. project
-
-> [!IMPORTANT]
-> **Organization scope** provides access to all projects within the organization and allows switching between them using `change_context`.  
-> **Project scope** provides direct access to project-specific resources but limits visibility to that single project.
-
-**Recommended (organization scope)**
-```bash
-datumctl mcp --organization <org-id> --namespace <ns> [--port 8080]
-```
-
-##### Claude config (macOS)
-```json
-{
-  "mcpServers": {
-    "datum_mcp": {
-      "command": "/absolute/path/to/datumctl",
-      "args": ["mcp", "--organization", "your-org-id", "--namespace", "default"]
-    }
-  }
-}
-```
-
-**Project scope (alternative)**
-```bash
-datumctl mcp --project <project-id> --namespace <ns> [--port 8080]
-```
-
-**HTTP debug (if `--port` is set):**
-```bash
-# List CRDs
-curl -s localhost:8080/datum/list_crds | jq
-
-# List resources
-curl -s localhost:8080/datum/list_resources -H 'Content-Type: application/json' -d '{"kind":"Project"}' | jq
-
-# Validate a YAML file (wrap safely into JSON)
-printf '{"yaml":%s}\n' "$(jq -Rs . </path/to/file.yaml)" | curl -s -X POST localhost:8080/datum/validate_yaml -H 'Content-Type: application/json' -d @- | jq
-```
-
-For more detailed tool setup instructions, refer to the official
-[Set Up Tools](https://docs.datum.net/docs/tasks/tools/) guide on docs.datum.net.
-
 ## Documentation
 
 For comprehensive user and developer guides, including detailed command references and authentication flow explanations, please see the [**Documentation**](./docs/README.md).

go.mod

@@ -16,14 +16,12 @@ require (
 	go.miloapis.com/activity v0.3.1
 	go.miloapis.com/milo v0.21.0
 	golang.org/x/oauth2 v0.36.0
-	k8s.io/apiextensions-apiserver v0.35.2
 	k8s.io/apimachinery v0.35.2
 	k8s.io/cli-runtime v0.35.2
 	k8s.io/client-go v0.35.2
 	k8s.io/component-base v0.35.2
 	k8s.io/kubectl v0.35.2
 	sigs.k8s.io/controller-runtime v0.23.3
-	sigs.k8s.io/yaml v1.6.0
 )
 
 require (
@@ -101,6 +99,7 @@ require (
 	gopkg.in/evanphx/json-patch.v4 v4.13.0 // indirect
 	gopkg.in/inf.v0 v0.9.1 // indirect
 	k8s.io/api v0.35.2 // indirect
+	k8s.io/apiextensions-apiserver v0.35.2 // indirect
 	k8s.io/apiserver v0.35.2 // indirect
 	k8s.io/component-helpers v0.35.2 // indirect
 	k8s.io/klog/v2 v2.130.1 // indirect
@@ -113,4 +112,5 @@ require (
 	sigs.k8s.io/kustomize/kyaml v0.21.0 // indirect
 	sigs.k8s.io/randfill v1.0.0 // indirect
 	sigs.k8s.io/structured-merge-diff/v6 v6.3.2-0.20260122202528-d9cc6641c482 // indirect
+	sigs.k8s.io/yaml v1.6.0 // indirect
 )