Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Kairon

de zyvoraiversión 0.10.2i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.zyvorai/kairon

Instalar

Resumen

Descripción del creador (original en inglés)

Inspect Kairon VMs, network policy and VM-edge flows from an agent. Read-only by default.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Otros
  • Debes completar: KAIRON_KUBE_URL, KAIRON_KUBE_TOKEN, KAIRON_UI_TOKEN, KAIRON_LLM_API_KEY

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
  • Debes completar tú: KAIRON_KUBE_URL, KAIRON_KUBE_TOKEN, KAIRON_KUBE_CA, KAIRON_KUBE_INSECURE, KAIRON_UI_URL, KAIRON_UI_TOKEN, KAIRON_UI_CA, KAIRON_UI_INSECURE, KAIRON_LLM_URL, KAIRON_LLM_MODEL, KAIRON_LLM_API_KEY, KAIRON_MCP_TENANT

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "kairon": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "KAIRON_KUBE_URL",
        "-e",
        "KAIRON_KUBE_TOKEN",
        "-e",
        "KAIRON_KUBE_CA",
        "-e",
        "KAIRON_KUBE_INSECURE",
        "-e",
        "KAIRON_UI_URL",
        "-e",
        "KAIRON_UI_TOKEN",
        "-e",
        "KAIRON_UI_CA",
        "-e",
        "KAIRON_UI_INSECURE",
        "-e",
        "KAIRON_LLM_URL",
        "-e",
        "KAIRON_LLM_MODEL",
        "-e",
        "KAIRON_LLM_API_KEY",
        "-e",
        "KAIRON_MCP_TENANT",
        "ghcr.io/zyvorai/kairon-mcp:v0.10.2"
      ],
      "env": {
        "KAIRON_KUBE_URL": "your-value",
        "KAIRON_KUBE_TOKEN": "your-value",
        "KAIRON_KUBE_CA": "your-value",
        "KAIRON_KUBE_INSECURE": "your-value",
        "KAIRON_UI_URL": "your-value",
        "KAIRON_UI_TOKEN": "your-value",
        "KAIRON_UI_CA": "your-value",
        "KAIRON_UI_INSECURE": "your-value",
        "KAIRON_LLM_URL": "your-value",
        "KAIRON_LLM_MODEL": "your-value",
        "KAIRON_LLM_API_KEY": "your-value",
        "KAIRON_MCP_TENANT": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add kairon --env KAIRON_KUBE_URL=your-value --env KAIRON_KUBE_TOKEN=your-value --env KAIRON_KUBE_CA=your-value --env KAIRON_KUBE_INSECURE=your-value --env KAIRON_UI_URL=your-value --env KAIRON_UI_TOKEN=your-value --env KAIRON_UI_CA=your-value --env KAIRON_UI_INSECURE=your-value --env KAIRON_LLM_URL=your-value --env KAIRON_LLM_MODEL=your-value --env KAIRON_LLM_API_KEY=your-value --env KAIRON_MCP_TENANT=your-value -- docker run -i --rm -e KAIRON_KUBE_URL -e KAIRON_KUBE_TOKEN -e KAIRON_KUBE_CA -e KAIRON_KUBE_INSECURE -e KAIRON_UI_URL -e KAIRON_UI_TOKEN -e KAIRON_UI_CA -e KAIRON_UI_INSECURE -e KAIRON_LLM_URL -e KAIRON_LLM_MODEL -e KAIRON_LLM_API_KEY -e KAIRON_MCP_TENANT ghcr.io/zyvorai/kairon-mcp:v0.10.2

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "kairon": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "KAIRON_KUBE_URL",
        "-e",
        "KAIRON_KUBE_TOKEN",
        "-e",
        "KAIRON_KUBE_CA",
        "-e",
        "KAIRON_KUBE_INSECURE",
        "-e",
        "KAIRON_UI_URL",
        "-e",
        "KAIRON_UI_TOKEN",
        "-e",
        "KAIRON_UI_CA",
        "-e",
        "KAIRON_UI_INSECURE",
        "-e",
        "KAIRON_LLM_URL",
        "-e",
        "KAIRON_LLM_MODEL",
        "-e",
        "KAIRON_LLM_API_KEY",
        "-e",
        "KAIRON_MCP_TENANT",
        "ghcr.io/zyvorai/kairon-mcp:v0.10.2"
      ],
      "env": {
        "KAIRON_KUBE_URL": "your-value",
        "KAIRON_KUBE_TOKEN": "your-value",
        "KAIRON_KUBE_CA": "your-value",
        "KAIRON_KUBE_INSECURE": "your-value",
        "KAIRON_UI_URL": "your-value",
        "KAIRON_UI_TOKEN": "your-value",
        "KAIRON_UI_CA": "your-value",
        "KAIRON_UI_INSECURE": "your-value",
        "KAIRON_LLM_URL": "your-value",
        "KAIRON_LLM_MODEL": "your-value",
        "KAIRON_LLM_API_KEY": "your-value",
        "KAIRON_MCP_TENANT": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "kairon": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "KAIRON_KUBE_URL",
        "-e",
        "KAIRON_KUBE_TOKEN",
        "-e",
        "KAIRON_KUBE_CA",
        "-e",
        "KAIRON_KUBE_INSECURE",
        "-e",
        "KAIRON_UI_URL",
        "-e",
        "KAIRON_UI_TOKEN",
        "-e",
        "KAIRON_UI_CA",
        "-e",
        "KAIRON_UI_INSECURE",
        "-e",
        "KAIRON_LLM_URL",
        "-e",
        "KAIRON_LLM_MODEL",
        "-e",
        "KAIRON_LLM_API_KEY",
        "-e",
        "KAIRON_MCP_TENANT",
        "ghcr.io/zyvorai/kairon-mcp:v0.10.2"
      ],
      "env": {
        "KAIRON_KUBE_URL": "your-value",
        "KAIRON_KUBE_TOKEN": "your-value",
        "KAIRON_KUBE_CA": "your-value",
        "KAIRON_KUBE_INSECURE": "your-value",
        "KAIRON_UI_URL": "your-value",
        "KAIRON_UI_TOKEN": "your-value",
        "KAIRON_UI_CA": "your-value",
        "KAIRON_UI_INSECURE": "your-value",
        "KAIRON_LLM_URL": "your-value",
        "KAIRON_LLM_MODEL": "your-value",
        "KAIRON_LLM_API_KEY": "your-value",
        "KAIRON_MCP_TENANT": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • KAIRON_KUBE_URL obligatorio env
    Kubernetes API server URL, e.g. https://k8s.example:6443. The server only offers read tools unless --allow-write is appended to the container arguments; the image never sets it.
  • KAIRON_KUBE_TOKEN secreto obligatorio env
    Bearer token for the Kubernetes API. Bind it to a Role with only the verbs the agent needs (get/list on machines for read-only use).
  • KAIRON_KUBE_CA env
    Path, inside the container, of the CA bundle for the Kubernetes API (mount it). Leave unset to use system roots.
  • KAIRON_KUBE_INSECURE env
    Set to "true" to skip TLS verification of the Kubernetes API. Lab use only.
  • KAIRON_UI_URL env
    Base URL of kairon-ui; needed by the machine_network tool (network flows, drops, capture sessions).
  • KAIRON_UI_TOKEN secreto env
    Bearer token for kairon-ui.
  • KAIRON_UI_CA env
    Path, inside the container, of the CA certificate for a self-signed kairon-ui (mount it).
  • KAIRON_UI_INSECURE env
    Set to "true" to skip TLS verification of kairon-ui. Lab use only.
  • KAIRON_LLM_URL env
    OpenAI-compatible endpoint for the optional ask tool and the summary in diagnose.
  • KAIRON_LLM_MODEL env
    Model name sent to KAIRON_LLM_URL.
  • KAIRON_LLM_API_KEY secreto env
    API key for KAIRON_LLM_URL.
  • KAIRON_MCP_TENANT env
    Scope the claim tools, diagnose and ask to this tenant.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub zyvorai, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 18438 servidores de esta categoría
  • Publicado en el registro más recientemente que el 68% de los otros 18438 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 18438 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Kairon?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: KAIRON_KUBE_URL, KAIRON_KUBE_TOKEN, KAIRON_UI_TOKEN, KAIRON_LLM_API_KEY

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.10.2) llegó al registro hace 21 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Tethered Trust

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

de formulahendryInicial↓ 66/sem★ 440Actualizado hace 14 meses

Se ejecuta en tu computadora

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

de desktop-commanderEn crecimiento★ 211Actualizado hace 3 días

Se ejecuta en la nube✓ desktopcommander.app

Tethered Trust

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

de tetheredtrust.comMuy nuevoActualizado hoy

Se ejecuta en la nube✓ tetheredtrust.com

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

Kairon

VMs that don't pretend to be Pods.

Real virtual machines, scheduled by Kubernetes, run straight on KVM. No virt-launcher pod per VM, no libvirt in the hot path, no operator zoo. A Machine is desired state, kairon-controller places it, and kairon-node runs it on FluxVM with QEMU, Cloud Hypervisor, Firecracker or FluxVM's own hypervisor.

Zero pods per VM · Four hypervisors, one CRD · eBPF on every VM edge · No silent split-brain · AI agents built in (MCP)

Dashboard tour captured against the local sample-data stack ( how ), not a production cluster.


What's new

Experimental operations: Kairon Rehearsal tests upgrades on isolated CSI copies. Advanced operations adds health-gated configuration change plans, application recovery verification, traffic/RTT placement recommendations, and incident reproduction with fix verification. Includes runnable scenarios and failure-path tests. VM/CSI and host-isolation hardware qualification is still pending.

New since v0.6.0 (latest tag: v0.10.2; the rows down to incident bundles are new in v0.10.0):

Agent sessions (experimental)An AgentSession is a FluxVM agent session: a sandbox VM with a git workspace, a compiled egress/filesystem/process policy, budgets, checkpoints, live forks and an event ledger, scheduled and quota-counted like a Machine. Commands can wait for an admin's approval; chunked uploads, an interactive shell, credential grants the guest never sees, and the Mac guest's screen. kaironctl session, session_* MCP tools, both SDKs and a dashboard page. Mac nodes on FluxVM 0.4.8+. Guide →
Coming from virtctlkaironctl covers virtctl's verbs: console and VNC (with screenshots), restart/soft-reboot, exports and memory dumps, guest info, SSH keys and passwords, expose, freeze, guestfs, cdrom, create clone, objectgraph, --dry-run -o yaml, wait. CLI →
Self-test: is it all working?kaironctl selftest (or the dashboard's Self-test page) boots a tiny CirrOS VM and proves power, network, hotplug, snapshot-restore and more, with live coloured logs and a PASS / FAIL / SKIP table. deploy-remote.sh --self-test runs it right after a deploy. Guide →
Deploy without building locallydeploy-remote.sh --remote-build copies a small source tarball and compiles on the host, so a laptop needs no Go, no Node and no build cache. Fastest path →
HTTPS by defaultThe dashboard and the VNC console relay serve TLS out of the box (generated or bring-your-own certificate); plain HTTP is a named opt-out. Dashboard guide →
Mac Fabric (experimental)Several Macs as one pool: each publishes its chip, macOS, Rosetta, nested virtualization and Thunderbolt Bridge; spec.apple places vz Machines by them, and a MacNetwork gives Machines on different Macs one private network over Thunderbolt. Run against simulated Macs so far. Guide →
Cross-cluster DR (experimental)A MachineProtectionPlan replicates a group of Machines to S3 and keeps their specs and restore points on a second cluster, with RPO and RTO objectives. kaironctl dr failover brings them up there in dependency order, --planned with nothing lost; kaironctl dr test restores copies into an isolated network while production runs, also on a schedule. Machines keep their VirtualNetwork addresses and DNS names follow the active site through external-dns. Guide →
vGPU profiles and GPU health (experimental)spec.devices[].profile gives a Machine a slice of a GPU (NVIDIA vGPU or MIG-backed profile) instead of a whole one, scheduled by free instances and GPU memory, created when the Machine starts and returned when it stops; unhealthy GPUs are skipped. Guide →
Accelerator profiles (experimental)A cluster-scoped MachineAcceleratorProfile names an accelerator shape (count, vendor or vGPU profile, memory per device, one PCIe root for peer to peer, one NUMA node, an RDMA NIC next to the GPUs); Machines ask for it with spec.accelerators. The profile's status says how many more Machines fit on each node. Guide →
Node maintenance and DRS (experimental)kaironctl node maintenance enter NODE cordons a node, migrates its Machines away, and stops or hibernates the ones with nowhere to go; exit puts everything back. DRS (`-drs-mode recommendautomatic) evens out reserved CPU and memory across nodes, or moves Machines off nodes whose measured CPU, memory or IO pressure (PSI) is high, and kaironctl drs plan` previews it. Guide →
Per-disk I/O QoSIOPS and bandwidth limits on a Machine's root and data disks (io.throttle), with bursts, enforced by QEMU and changed live on a running Machine. Guide →
NVMe-oF storage (experimental)Kairon's CSI driver provisions nvme-tcp and nvme-rdma volumes through the kernel NVMe target with native multipath; raw Block volumes boot Machines in place and attach as data disks with per-disk QEMU I/O. Guide →
Hibernate (experimental)spec.powerState: Hibernated saves RAM and device state to disk and frees the node; resume continues the same boot, on its own node or a compatible one with shared storage. Guide →
Virtual networks (experimental)VirtualNetwork: isolated IPv4 networks routed in eBPF with a Geneve overlay, per-network gateway, egress SNAT and floating IPs. Guide →
Elastic memory (experimental)Run more Machine memory than the node has: guaranteed minimums, a virtio-balloon reclaim loop and a KaironMemoryPressure signal the scheduler respects. Guide →
Topology-aware placement (experimental)NUMA, GPU, NIC and NVMe locality: the scheduler picks the node, exact CPUs, NUMA memory and PCI devices together. Guide →
Incident bundles (experimental)kaironctl diagnose machine --deep: one redacted tar.gz with the Machine's cluster state plus QMP, cgroup, console, dataplane and pcap from its node, and an opt-in guest memory dump. Guide →
Lifecycle, diagnostics and namespaces (v0.9)kaironctl doctor, connectivity test, logs, events, sysdump, config, history/rollback; kaironctl upgrade keeps your previous Helm values. The dashboard has a namespace selector, an all-namespaces Machines view and bulk Start/Stop. Release notes →
`v1` API and new dashboardkairon.zyvor.dev/v1 is the storage version (v1beta1/v1alpha1 served, deprecated). The dashboard is redesigned and gains Storage (Atlas), Pools & claims, Images and Backups pages; kairon-ui now listens on :18082. Guide →
Native macOS nodekairon-node registers an Apple silicon Mac as a Node and runs backend: vz Machines through FluxVM. Verified on an M4; multi-Mac clusters not yet. Guide → · Mac cluster →
Developer ecosystem kitPython and TypeScript SDKs, digest-pinned recipes, disposable-VM GitHub Actions, Terraform composition. Kit →
Fleet automation (experimental)Opt-in Redfish fencing, balancing, autoscaling, backup and recovery plans, template claims, usage CSV and a Fleet dashboard. Guide →
Kairon vs KubeVirt benchmarkSame node, same guest, one script driving both; method and raw JSON in docs/benchmarks.
Import from VMwarekaironctl import ova streams an OVA once, reads vCPU, memory and firmware from the OVF, and FluxVM converts and repairs the disk. Guide →
Warm pools and claimsMachinePool keeps booted Machines ready; a MachineClaim binds one in a single reconcile tick, with per-claim egress allowlists. Guide →
VM forkkaironctl fork and the MCP fork_machine tool fork a running Machine through FluxVM. Guide →
Agent sandboxes (experimental)spec.lifecycle pauses idle Machines and wakes them on connect, deletes them after a max lifetime; paused warm pools, per-claim usage, and Sandbox classes in both SDKs. Guide →
BackupsMachineBackup and MachineBackupRestore with guest filesystem freeze, plus Atlas S3 backup jobs for Atlas volumes. Incremental S3 backups with policies and GFS retention (experimental). Guide →
Live disks and NICsHot-attach PVC disks and hot-add or remove extra NICs on running Machines (kaironctl disk, kaironctl nic). Guide →
Tenant fencekairon.zyvor.dev/tenant-fence turns spec.tenant into an east-west deny of other tenants' guest addresses in the namespace. Guide →
Preemption by HaltAn opted-in high-priority Machine that can't be placed halts an opted-in lower-priority one, and it resumes when the preemptor leaves. Guide →

| Hotplug survives restart | A stop/start boots at the hotplugged CPU and memory; hotplug-persist writes it back into spec.

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx