World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Description from the maker (original English)
Create, test and break real Proxmox VE clusters in QEMU/KVM on the local host.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Passed 2/2 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Docker
SettingsDeveloperEdit Config
{
"mcpServers": {
"proxbase": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/virtbase/proxbase:0.4.1",
"mcp"
]
}
}
}Use Proxbase and tell me what you can do for me, then show me one thing✓ If Claude says it is using Proxbase or shows a Proxbase tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Proxbase yet
Proxbase runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Proxbase
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Docker on your computer first (one time)
One time only; it works for every server that needs Docker
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add proxbase -- docker run -i --rm ghcr.io/virtbase/proxbase:0.4.1 mcpYou should see Proxbase listed as connected
Use Proxbase and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Proxbase or shows a Proxbase tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Docker on your computer first (one time)
One time only; it works for every server that needs Docker
Use Proxbase and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Proxbase or shows a Proxbase tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Docker on your computer first (one time)
One time only; it works for every server that needs Docker
Use Proxbase and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Proxbase or shows a Proxbase tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add proxbase -- docker run -i --rm ghcr.io/virtbase/proxbase:0.4.1 mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"proxbase": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/virtbase/proxbase:0.4.1",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"proxbase": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/virtbase/proxbase:0.4.1",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"proxbase": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/virtbase/proxbase:0.4.1",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
oci: ghcr.io/virtbase/proxbase:0.4.1Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026
The registry name was verified with the GitHub account virtbase, which owns the repo
Code last changed yesterday
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.4.1) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: World Monitor, Claude Flow, Tldraw
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Real Proxmox VE clusters on your Linux machine in about three minutes, for labs, demos and CI.
Proxbase starts every node as a QEMU/KVM virtual machine, installs it from the official Proxmox VE ISO with the automated installer, and joins the nodes into a cluster through the Proxmox API, with ZFS or Ceph storage, internal networks and an API token ready for Terraform or Ansible. No root, no Docker, no manual clicks.
$ proxbase create lab --nodes 3
… created in 2m56s Cluster lab: ready, quorate: yes, switch: running NODE VM CLUSTER IP WEB UI SSH pve1 running online 10.10.10.11 https://127.0.0.1:18001 127.0.0.1:18101 pve2 running online 10.10.10.12 https://127.0.0.1:18002 127.0.0.1:18102 pve3 running online 10.10.10.13 https://127.0.0.1:18003 127.0.0.1:18103
HEALTH_OK.proxbase env for shells, JSON and the bpg/proxmox Terraform provider, -o json and --progress json for scripts, and a GitHub Action for CI that can cache a ready cluster as a template.proxbase mcp is an MCP server: agents create clusters, call the API, run commands on nodes, diagnose, reset to snapshots and inject faults through tools. A skill teaches them the workflow; in Claude Code: /plugin install proxbase --marketplace virtbase/proxbase.--golden clones nodes from a cached base image: a 3-node cluster in under a minute (Ceph: 1.5 minutes), with a unique identity per node.proxbase up runs a cluster in the foreground with clean shutdown and a health check.Requirements: Linux on amd64 with /dev/kvm, QEMU 7.2+ (qemu-system-x86_64, qemu-img) and about 4 GiB RAM per node. Nested virtualization is needed for guests inside the nodes.
go install github.com/virtbase/proxbase/cmd/proxbase@latest # or see docs/install.md
proxbase doctor # checks KVM, QEMU, memory, ports proxbase create lab --nodes 3
Then open https://127.0.0.1:18001 (user root, password from proxbase env lab), or:
proxbase ssh lab pve2 -- pvecm status
eval "$(proxbase env lab)" # PROXMOX_VE_ENDPOINT, PROXMOX_VE_API_TOKEN, … proxbase destroy lab --yes # removes everything
proxbase create ceph --nodes 3 --storage ceph # hyperconverged Ceph
proxbase create fast --nodes 3 --golden # clone from a cached base image proxbase create -f examples/networks.yaml # separate networks and VLANs proxbase node add lab --count 1 # grow the cluster proxbase node remove lab pve2 # shrink it again proxbase stop lab && proxbase snapshot save lab base proxbase snapshot restore lab base && proxbase start lab proxbase env lab --format terraform # provider block for bpg/proxmox proxbase fault partition lab pve3 # isolate a node, then: fault clear proxbase status lab --check # exit code for CI and health checks claude mcp add proxbase -- proxbase mcp # let an AI agent drive proxbase proxbase upgrade # install the latest release
In GitHub Actions:
- id: pve
uses: virtbase/proxbase@v0 # KVM, QEMU, cache, create; outputs endpoint, api-token, env-file
A cluster file looks like this (everything has a default):
apiVersion: proxbase.virtbase.com/v1alpha1
kind: Cluster name: lab nodes: count: 3 defaults: {cpus: 4, memory: 4G, dataDisks: [{size: 32G}]} networks:
storage: zfs: [{name: tank, raid: single}]
| Topic | |
|---|---|
| Getting started | First cluster, web UI, credentials |
| Installation | Packages, Homebrew, container image, verifying releases |
| Configuration | Every field, default and limit |
| Networking · Storage · Lifecycle | How it works and what to expect |
| Fault injection · Golden images | Breaking the cluster on purpose, faster creates |
| CI and automation · MCP server | GitHub Action, JSON progress, AI agents |
| Docker · CLI reference · Troubleshooting | |
| Architecture | Packages, create flow, state on disk |
| Examples | Ready-to-use cluster files for common setups |
Proxbase is young; the file format may change before v1.0. It is tested with Proxmox VE 9.2 on Debian 13 (QEMU 10.0, AMD). Clusters need a Linux host with KVM: macOS builds are experimental and Docker Desktop has no /dev/kvm. Nodes are reachable from the host through forwarded ports on 127.0.0.1; host-reachable bridge networking is designed but not implemented. Proxbase builds labs: it stores generated passwords and keys unencrypted in its state directory.
Issues and pull requests are welcome; see CONTRIBUTING.md and the code of conduct. Report security issues privately as described in SECURITY.md.