Antrieb

Validates AI infra code on real VMs. Self-corrects until it works. No containers, no sandboxes.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "antrieb": {
      "command": "npx",
      "args": [
        "-y",
        "antrieb"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Antrieb MCP Server

Instant disposable clusters for LLM-generated networks and infra.

Say an LLM writes a VyOS NAT config, an OpenWrt firewall rule set, or a bash script to harden a CentOS cluster. Where do you run it before it touches your environment? Antrieb gives the LLM a disposable multi-node cluster, with real VMs and real networking, to try what it generates. Break it, quickly reprovision, try again. No cleanup.

Same OS and appliances your LLM-generated code will target in production: CentOS Stream, Ubuntu, Debian, Alma, Alpine, VyOS, OPNsense, SONiC, OpenWrt. Multi-network topologies with per-NIC assignment. Not a container, not a microVM, not some unknown Linux — the same kernels and packages your real fleet runs.

Root access, private networking, passwordless SSH between nodes. Ten minutes per cluster. Clean slate every time. Instant clusters that change the economics of being wrong for LLMs.

Quick Start

Antrieb is a remote MCP server. Nothing to install. Add it to your config and start provisioning.

Claude Web / ChatGPT

With web-based AI clients, add Antrieb as a custom connector.

In claude.ai: go to Settings → Connectors, click Add custom connector. Enter:

Name: Antrieb
URL: https://antrieb.sh/mcp

Click Add, then Connect and sign in. Back in your chat, try something like:

Create a 3-node Kubernetes cluster, with node1 running both as control-plane and worker, and node2/node3 as pure workers. Install nginx with 3 pods and pod anti-affinity.

Walkthrough video: https://youtu.be/8nts8ol-yeA

MCP Clients (Claude Desktop, Claude Code, Codex, custom clients)

Get a free API key at antrieb.sh/dash, then add this to your MCP client config (e.g. .mcp.json for Claude Desktop):

Claude Code

Put this JSON in the current folder in a file called .mcp.json. Claude Code will find it automatically.

config.json

{
  "mcpServers": {
    "antrieb": {
      "type": "http",
      "url": "https://antrieb.sh/mcp",
      "headers": {
        "Authorization": "Bearer ant_YOUR_API_KEY"
      }
    }
  }
}

Codex

Put this TOML content in ./.codex/config.toml. Then set the ANTRIEB_TOKEN environment variable with your API key before launching Codex.

toml

 [mcp_servers.antrieb]
  url = "https://antrieb.sh/mcp"
  bearer_token_env_var = "ANTRIEB_TOKEN"

No local install, no dependencies, no Docker.

How It Works

Your LLM controls real VMs through 5 tools:

Code

1. provision  →  Spin up a cluster (sub-second per VM, declare custom networks and NICs)
2. exec       →  Run commands on any node (cluster-scoped env vars auto-injected)
3. save       →  Snapshot a node as an image, or save a runbook
4. search     →  Discover images, runbooks, or active clusters
5. delete     →  Destroy a cluster, or decommission a saved artifact

The LLM drives the entire workflow: provision a cluster, install software command by command, verify each step, and iterate until it works. Antrieb provides the infrastructure; the LLM provides the intelligence.

Example Workflow

Code

You: provision 3 ubuntu nodes and install nginx on all nodes


LLM: provision(cluster: ["ubuntu24.04 x3"])
→ { session_id: "abc12", nodes: ["node1", "node2", "node3"], provision_time_ms: 720 }

LLM: exec(session_id: "abc12", node: "node1", command: "apt-get update && apt-get install -y nginx")
→ { exit_code: 0, stdout: "..." }

LLM: exec(session_id: "abc12", node: "node1", command: "systemctl start nginx && curl -s localhost")
→ { exit_code: 0, stdout: "<html>Welcome to nginx...</html>" }

LLM: save(type: "image", session_id: "abc12", node: "node1", name: "my-nginx", commands: [...])
→ { ani: "antrieb:my-nginx:v1" }

LLM: delete(type: "cluster", name: "abc12")
→ { success: true }

Available Images

Base Images

ANI	Description
`ubuntu24.04`	Ubuntu 24.04 LTS: apt, bash, Python 3, curl, wget, jq
`almalinux9`	AlmaLinux 9 (RHEL-compatible): dnf, bash, Python 3
`centos-stream10`	CentOS Stream 10: dnf, bash, Python 3
`debian13`	Debian 13: apt, bash, Python 3, curl, wget, jq
`alpine`	Alpine Linux 3.23: apk, minimal, musl libc
`sonic`	SONiC: open-source network OS for data-center switches
`vyos`	VyOS: Linux-based router / firewall with a unified CLI
`openwrt`	OpenWrt 25.12: Linux-based firmware with UCI configuration
`opnsense`	OPNsense: FreeBSD-based firewall / router with web UI

Stack Images

Stack images are custom images created by enriching the base images with additional packages.

ANI	Description
`terraform-aws`	Terraform with real AWS (free-tier, Antrieb's credentials, Vault-brokered STS)
`ansible-controller`	Ansible control node with collections
`podman`	Podman, Buildah, Skopeo (rootless, Docker-API-compatible)
`mongodb`	MongoDB server image for database provisioning and integration tests
`postgresql`	PostgreSQL server image for SQL database tests
`vault`	HashiCorp Vault image for secrets workflows and Terraform-backed credentials
`mariadb`	MariaDB server image for MySQL-compatible database tests
`nginx`	NGINX image for web server and reverse-proxy scenarios
`helm-k3s`	K3s with Helm for lightweight Kubernetes scenarios
`asterisk-pbx`	Asterisk PBX image for SIP and telephony scenarios

Use search to discover all available images with full descriptions, or just specify a distro name and Antrieb picks the right one.

Cluster Networking

Networking is a first-class input to provision, not an afterthought. Every cluster is L2-isolated from every other cluster (even ones you own), with hostname resolution, passwordless SSH between its own nodes, and cluster-scoped env vars auto-injected into every exec call. What varies between runs is how nodes are wired and controlled by the optional networks and nics parameters on provision.

There are two modes: the default network (flat, one-subnet, internet-reachable) and declared networks (first-class multi-subnet, multi-NIC topologies).

Every cluster (both modes)

Hostname resolution: node1, node2, node3 in /etc/hosts on every node.
Passwordless SSH: a per-cluster ed25519 keypair distributed to all nodes. ssh node2 hostname just works.
L2 isolation: nodes across different clusters cannot reach each other, regardless of CIDR overlap or account.
Env vars on every exec: NODE_NAME, NODE_INDEX, NODE_IP, CLUSTER_HOSTS (multiline IP NAME — drop-in for /etc/hosts), CLUSTER_SSH_PUBKEY, CLUSTER_SSH_PRIVKEY.

Code

LLM: exec(node: "node1", command: "ssh node2 hostname")
→ { stdout: "node2" }

Default network (when `networks` / `nics` are omitted)

Code

LLM: provision(cluster: ["ubuntu24.04 x3"])

You get:

One auto-allocated /24 network named default, one NIC per node, DHCP-assigned IPs.
Egress to the internet via a curated port allowlist (HTTP, HTTPS, DNS, SSH, package managers). Arbitrary outbound is blocked.
No router VM, no firewall zones, no topology to configure. Nodes talk to each other and to the outside world.

Use this whenever the network isn't what you're testing — application-level work, distro-specific configuration, Ansible playbooks, CI pipelines, Kubernetes-on-three-ubuntus.

Declared networks (multi-network, multi-NIC)

Pass networks and nics when the topology itself is the thing under test: routers, firewalls, DMZs, isolated back-end subnets, dual-homed nodes, BGP meshes.

Code

LLM: provision(
  cluster: ["vyos", "ubuntu24.04", "ubuntu24.04"],
  networks: [
    { name: "wan", egress: true },
    { name: "lan", cidr: "10.10.1.0/24", egress: false }
  ],
  nics: {
    node1: [{ net: "wan" }, { net: "lan" }],   // vyos: dual-homed router
    node2: [{ net: "lan" }],                    // ubuntu backend
    node3: [{ net: "lan" }]                     // ubuntu backend
  }
)

Contract:

Each declared network is its own L2 segment with its own DHCP server and its own /24. CIDRs are auto-allocated when omitted; only /24 is supported.
egress: true — internet-reachable on the default port allowlist. egress: false — traffic stays inside the network; no default route out.
dhcp: true (default) — the platform assigns IPs. dhcp: false — you assign IPs (use this when a router VM owns addressing or you need precise /31 links).
NIC order matters. Each entry in nics.<node> becomes eth0, eth1, ... in the listed order.
.1 of every DHCP-enabled network is reserved for the platform bridge gateway. Router VMs should claim .254 (or DHCP-client) — assigning .1 to a VM causes ARP flip-flop.

This unlocks serious networking work: VyOS / OPNsense firewalls with WAN/LAN zones, SONiC as an L2 switch or L3 router, OpenWrt with its fw3 zone model, nginx behind a reverse-proxy LAN, BGP peering over /31 transit links, hairpin NAT, DNAT port-forwards. Full walkthroughs for each pattern live in the @antrieb/* runbook library.

Reusable topologies should be captured in runbooks. Networks are declared inline during provision; if the same topology matters across scenarios, save the topology, commands, and verification steps together as a runbook.

Example Network Labs

The default antrieb/* runbook library includes verified scenarios such as:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Antrieb

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "antrieb": { "command": "npx", "args": ["-y", "antrieb"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/antrieb?style=directory)](https://allmcps.com/mcp/antrieb)

HTML Embed

<a href="https://allmcps.com/mcp/antrieb"><img src="https://allmcps.com/api/badge/antrieb?style=directory" alt="Antrieb on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Antrieb →Install in Claude Desktop Install in Cursor Install in VS Code

Antrieb

Validates AI infra code on real VMs. Self-corrects until it works. No containers, no sandboxes.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "antrieb": {
      "command": "npx",
      "args": [
        "-y",
        "antrieb"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Antrieb MCP Server

Instant disposable clusters for LLM-generated networks and infra.

Root access, private networking, passwordless SSH between nodes. Ten minutes per cluster. Clean slate every time. Instant clusters that change the economics of being wrong for LLMs.

Quick Start

Antrieb is a remote MCP server. Nothing to install. Add it to your config and start provisioning.

Claude Web / ChatGPT

With web-based AI clients, add Antrieb as a custom connector.

In claude.ai: go to Settings → Connectors, click Add custom connector. Enter:

Name: Antrieb
URL: https://antrieb.sh/mcp

Click Add, then Connect and sign in. Back in your chat, try something like:

Create a 3-node Kubernetes cluster, with node1 running both as control-plane and worker, and node2/node3 as pure workers. Install nginx with 3 pods and pod anti-affinity.

Walkthrough video: https://youtu.be/8nts8ol-yeA

MCP Clients (Claude Desktop, Claude Code, Codex, custom clients)

Get a free API key at antrieb.sh/dash, then add this to your MCP client config (e.g. .mcp.json for Claude Desktop):

Claude Code

Put this JSON in the current folder in a file called .mcp.json. Claude Code will find it automatically.

config.json

{
  "mcpServers": {
    "antrieb": {
      "type": "http",
      "url": "https://antrieb.sh/mcp",
      "headers": {
        "Authorization": "Bearer ant_YOUR_API_KEY"
      }
    }
  }
}

Codex

Put this TOML content in ./.codex/config.toml. Then set the ANTRIEB_TOKEN environment variable with your API key before launching Codex.

toml

 [mcp_servers.antrieb]
  url = "https://antrieb.sh/mcp"
  bearer_token_env_var = "ANTRIEB_TOKEN"

No local install, no dependencies, no Docker.

How It Works

Your LLM controls real VMs through 5 tools:

Code

1. provision  →  Spin up a cluster (sub-second per VM, declare custom networks and NICs)
2. exec       →  Run commands on any node (cluster-scoped env vars auto-injected)
3. save       →  Snapshot a node as an image, or save a runbook
4. search     →  Discover images, runbooks, or active clusters
5. delete     →  Destroy a cluster, or decommission a saved artifact

Example Workflow

Code

You: provision 3 ubuntu nodes and install nginx on all nodes


LLM: provision(cluster: ["ubuntu24.04 x3"])
→ { session_id: "abc12", nodes: ["node1", "node2", "node3"], provision_time_ms: 720 }

LLM: exec(session_id: "abc12", node: "node1", command: "apt-get update && apt-get install -y nginx")
→ { exit_code: 0, stdout: "..." }

LLM: exec(session_id: "abc12", node: "node1", command: "systemctl start nginx && curl -s localhost")
→ { exit_code: 0, stdout: "<html>Welcome to nginx...</html>" }

LLM: save(type: "image", session_id: "abc12", node: "node1", name: "my-nginx", commands: [...])
→ { ani: "antrieb:my-nginx:v1" }

LLM: delete(type: "cluster", name: "abc12")
→ { success: true }

Available Images

Base Images

ANI	Description
`ubuntu24.04`	Ubuntu 24.04 LTS: apt, bash, Python 3, curl, wget, jq
`almalinux9`	AlmaLinux 9 (RHEL-compatible): dnf, bash, Python 3
`centos-stream10`	CentOS Stream 10: dnf, bash, Python 3
`debian13`	Debian 13: apt, bash, Python 3, curl, wget, jq
`alpine`	Alpine Linux 3.23: apk, minimal, musl libc
`sonic`	SONiC: open-source network OS for data-center switches
`vyos`	VyOS: Linux-based router / firewall with a unified CLI
`openwrt`	OpenWrt 25.12: Linux-based firmware with UCI configuration
`opnsense`	OPNsense: FreeBSD-based firewall / router with web UI

Stack Images

Stack images are custom images created by enriching the base images with additional packages.

ANI	Description
`terraform-aws`	Terraform with real AWS (free-tier, Antrieb's credentials, Vault-brokered STS)
`ansible-controller`	Ansible control node with collections
`podman`	Podman, Buildah, Skopeo (rootless, Docker-API-compatible)
`mongodb`	MongoDB server image for database provisioning and integration tests
`postgresql`	PostgreSQL server image for SQL database tests
`vault`	HashiCorp Vault image for secrets workflows and Terraform-backed credentials
`mariadb`	MariaDB server image for MySQL-compatible database tests
`nginx`	NGINX image for web server and reverse-proxy scenarios
`helm-k3s`	K3s with Helm for lightweight Kubernetes scenarios
`asterisk-pbx`	Asterisk PBX image for SIP and telephony scenarios

Use search to discover all available images with full descriptions, or just specify a distro name and Antrieb picks the right one.

Cluster Networking

There are two modes: the default network (flat, one-subnet, internet-reachable) and declared networks (first-class multi-subnet, multi-NIC topologies).

Every cluster (both modes)

Hostname resolution: node1, node2, node3 in /etc/hosts on every node.
Passwordless SSH: a per-cluster ed25519 keypair distributed to all nodes. ssh node2 hostname just works.
L2 isolation: nodes across different clusters cannot reach each other, regardless of CIDR overlap or account.
Env vars on every exec: NODE_NAME, NODE_INDEX, NODE_IP, CLUSTER_HOSTS (multiline IP NAME — drop-in for /etc/hosts), CLUSTER_SSH_PUBKEY, CLUSTER_SSH_PRIVKEY.

Code

LLM: exec(node: "node1", command: "ssh node2 hostname")
→ { stdout: "node2" }

Default network (when `networks` / `nics` are omitted)

Code

LLM: provision(cluster: ["ubuntu24.04 x3"])

You get:

One auto-allocated /24 network named default, one NIC per node, DHCP-assigned IPs.
Egress to the internet via a curated port allowlist (HTTP, HTTPS, DNS, SSH, package managers). Arbitrary outbound is blocked.
No router VM, no firewall zones, no topology to configure. Nodes talk to each other and to the outside world.

Use this whenever the network isn't what you're testing — application-level work, distro-specific configuration, Ansible playbooks, CI pipelines, Kubernetes-on-three-ubuntus.

Declared networks (multi-network, multi-NIC)

Pass networks and nics when the topology itself is the thing under test: routers, firewalls, DMZs, isolated back-end subnets, dual-homed nodes, BGP meshes.

Code

LLM: provision(
  cluster: ["vyos", "ubuntu24.04", "ubuntu24.04"],
  networks: [
    { name: "wan", egress: true },
    { name: "lan", cidr: "10.10.1.0/24", egress: false }
  ],
  nics: {
    node1: [{ net: "wan" }, { net: "lan" }],   // vyos: dual-homed router
    node2: [{ net: "lan" }],                    // ubuntu backend
    node3: [{ net: "lan" }]                     // ubuntu backend
  }
)

Contract:

Each declared network is its own L2 segment with its own DHCP server and its own /24. CIDRs are auto-allocated when omitted; only /24 is supported.
egress: true — internet-reachable on the default port allowlist. egress: false — traffic stays inside the network; no default route out.
dhcp: true (default) — the platform assigns IPs. dhcp: false — you assign IPs (use this when a router VM owns addressing or you need precise /31 links).
NIC order matters. Each entry in nics.<node> becomes eth0, eth1, ... in the listed order.
.1 of every DHCP-enabled network is reserved for the platform bridge gateway. Router VMs should claim .254 (or DHCP-client) — assigning .1 to a VM causes ARP flip-flop.

Example Network Labs

The default antrieb/* runbook library includes verified scenarios such as:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Antrieb

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "antrieb": { "command": "npx", "args": ["-y", "antrieb"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/antrieb?style=directory)](https://allmcps.com/mcp/antrieb)

HTML Embed

<a href="https://allmcps.com/mcp/antrieb"><img src="https://allmcps.com/api/badge/antrieb?style=directory" alt="Antrieb on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Featured

AllMCPs Server

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Antrieb →Install in Claude Desktop Install in Cursor Install in VS Code

Antrieb

Quick Install

Client Config & Setup

Documentation Overview

Antrieb MCP Server

Quick Start

Claude Web / ChatGPT

MCP Clients (Claude Desktop, Claude Code, Codex, custom clients)

Claude Code

Codex

How It Works

Example Workflow

Available Images

Base Images

Stack Images

Cluster Networking

Every cluster (both modes)

Default network (when networks / nics are omitted)

Declared networks (multi-network, multi-NIC)

Example Network Labs

Related MCP Servers

Reviews

Frequently Asked Questions about Antrieb

AllMCPs Directory Badge

Technical Specs & Signals

AllMCPs Server

Own this project?

Share & Embed

Explore more

Antrieb

Quick Install

Client Config & Setup

Documentation Overview

Antrieb MCP Server

Quick Start

Claude Web / ChatGPT

MCP Clients (Claude Desktop, Claude Code, Codex, custom clients)

Claude Code

Codex

How It Works

Example Workflow

Available Images

Base Images

Stack Images

Cluster Networking

Every cluster (both modes)

Default network (when networks / nics are omitted)

Declared networks (multi-network, multi-NIC)

Example Network Labs

Related MCP Servers

Reviews

Frequently Asked Questions about Antrieb

AllMCPs Directory Badge

Technical Specs & Signals

AllMCPs Server

Own this project?

Share & Embed

Explore more

Default network (when `networks` / `nics` are omitted)

Default network (when `networks` / `nics` are omitted)