What can you do with this server?

The vmm-mcp-server provides an MCP interface to the VMM API, enabling management of network topologies, VMs, configurations, YAML/JSON conversion, and leases. Current state: Only vmm_list_topologies is exposed in the active server schema. The project defines many additional tools (per README): * Topology Management: List, launch, validate, bind/start/stop/unbind VMs, export/import/clone topologies. * Configuration Management: Upload configs, show active config, and manage a library of saved configs (list, get, save, remove). * YAML/JSON Conversion: Parse lab YAML to quickstart spec JSON, render JSON to YAML, and convert existing VMM configs to lab YAML. * Lease Management: Check lease status, schedule earlier unbind, and extend leases. All operations leverage the vmm-api CLI.

How do I use vmm-mcp-server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@vmm-mcp-server List all network topologies." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

vmm-mcp-server

by urao

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

vmm-mcp-server

An MCP server for VMM, a tool for creating and managing network topologies. It wraps the vmm-api CLI and exposes its subcommands as MCP tools so any MCP-compatible client (Claude Code, Claude Desktop, etc.) can drive VMM.

Tools

Tool	VMM CLI command	Description
`vmm_list_topologies`	`vmm-api ls`	List all network topologies known to VMM.
`vmm_launch_topology`	`vmm-api launch`	Configure, bind, and start a topology in one step.
`vmm_upload_config`	`vmm-api config`	Upload a topology config without binding/starting it.
`vmm_show_active_config`	`vmm-api config-print`	Display the currently active topology config.
`vmm_validate_topology`	`vmm-api validate`	Dry-run capacity check for a config, no deployment.
`vmm_bind_vms`	`vmm-api bind`	Launch VMs' QEMU processes, paused.
`vmm_start_vms`	`vmm-api start`	Start paused VMs (binds first if needed).
`vmm_stop_vms`	`vmm-api stop`	Pause QEMU emulation without deleting the process.
`vmm_unbind_vms`	`vmm-api unbind`	Release VMs (hard teardown, no guest shutdown).
`vmm_export_topology`	`vmm-api export`	Print a topology's userdb as JSON.
`vmm_import_topology`	`vmm-api import`	Recreate a topology from exported JSON.
`vmm_clone_topology`	`vmm-api clone`	Copy a topology's config into a new topo_id.
`vmm_yaml_parse`	`vmm-api yaml parse`	Lab YAML -> normalized quickstart spec JSON.
`vmm_yaml_render`	`vmm-api yaml render`	Quickstart spec JSON -> clean lab YAML.
`vmm_yaml_convert`	`vmm-api yaml convert`	Existing VMM config -> lab YAML.
`vmm_list_saved_configs`	`vmm-api configs list`	List your saved-config library.
`vmm_get_saved_config`	`vmm-api configs get`	Print one saved config.
`vmm_save_config`	`vmm-api configs save`	Store a config file into the saved-config library.
`vmm_remove_saved_config`	`vmm-api configs rm`	Delete a saved config.
`vmm_lease_status`	`vmm-api lease`	Show lease expiry and extensions used/remaining.
`vmm_schedule_unbind`	`vmm-api lease schedule`	Move auto-unbind earlier than the lease expiry.
`vmm_extend_lease`	`vmm-api extend`	Extend a topology's lease by 30 days.

More tools (e.g. auth) can be added as needed — see Adding a new tool.

Related MCP server: vsphere-mcp

Requirements

Node.js >= 18
The vmm-api CLI installed and available on PATH (or point VMM_API_BIN at it)

Install & build

npm install
npm run build

Configuration

The server reads two optional environment variables:

Variable	Default	Purpose
`VMM_API_BIN`	`vmm-api`	Path to the VMM CLI executable.
`VMM_API_TIMEOUT_MS`	`30000`	Timeout for each `vmm-api` invocation, in milliseconds.

Running

npm start

The server speaks MCP over stdio, so it's meant to be launched by an MCP client rather than run standalone. For example, in Claude Code's mcp config:

{
  "mcpServers": {
    "vmm": {
      "command": "node",
      "args": ["/absolute/path/to/vmm-mcp-server/dist/index.js"],
      "env": {
        "VMM_API_BIN": "/usr/local/bin/vmm-api"
      }
    }
  }
}

During development you can run it directly from TypeScript without building first:

npm run dev

Adding a new tool

Each tool is a small, self-contained module:

Create src/tools/<name>.ts exporting a VmmTool (see src/tools/types.ts) that calls runVmmApi([...]) from src/lib/vmmApi.ts with the right vmm-api args.
Register it by adding it to the array in src/tools/index.ts.

No changes to src/index.ts are needed — it registers whatever tools are listed there.

Project layout

src/
  index.ts              MCP server entry point (stdio transport, tool registration)
  lib/
    vmmApi.ts            Wrapper around spawning the vmm-api CLI
    args.ts              Helpers for building argv from flags (-x, --require, repeated -r, ...)
  tools/
    types.ts             Shared VmmTool interface + runAsToolResult() helper
    schemas.ts            Shared zod field definitions (groupId, requires, topoId, vmNames)
    listTopologies.ts    vmm_list_topologies      -> vmm-api ls
    launchTopology.ts    vmm_launch_topology      -> vmm-api launch
    uploadConfig.ts       vmm_upload_config        -> vmm-api config
    configPrint.ts         vmm_show_active_config   -> vmm-api config-print
    validateTopology.ts    vmm_validate_topology    -> vmm-api validate
    vmLifecycle.ts         vmm_bind_vms/start_vms/stop_vms/unbind_vms -> bind/start/stop/unbind
    exportTopology.ts      vmm_export_topology      -> vmm-api export
    importTopology.ts      vmm_import_topology      -> vmm-api import
    cloneTopology.ts       vmm_clone_topology       -> vmm-api clone
    yaml.ts                vmm_yaml_parse/render/convert -> vmm-api yaml ...
    savedConfigs.ts        vmm_*_saved_config(s)    -> vmm-api configs ...
    lease.ts               vmm_lease_status/schedule_unbind/extend_lease -> lease/extend
    index.ts               Registry of all tools

Available Tools

1 tool

vmm_list_topologiesList VMM topologiesA

List all network topologies known to VMM by running "vmm-api ls". Use this to discover existing topology names/IDs before creating, inspecting, or modifying one.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool runs 'vmm-api ls' and lists all topologies, which implies a non-destructive read-only operation. However, it does not explicitly state that no side effects occur or describe the output format, so it falls short of a perfect score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the action ('List all network topologies') and then provides the implementation method and usage context. Both sentences are concise and necessary, with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity—no parameters, no output schema, no sibling tools—the description fully covers what the tool does, how it does it, and when to use it. It provides all necessary context for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema is empty and there is no need for parameter explanations. Based on the guideline '0 params = baseline 4', this score is appropriate. The description adds value by indicating that the output provides names/IDs, but that is output semantics, not parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists all network topologies known to VMM, using the specific verb 'List' and resource 'network topologies known to VMM'. It also mentions the underlying command 'vmm-api ls', which adds precise context and leaves no ambiguity about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs using this tool to discover existing topology names/IDs before creating, inspecting, or modifying one. This is clear when-to-use guidance that helps the agent decide when to call this tool, even though there are no sibling tools to differentiate from.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updatev0.1.0Aug 6, 2026
- First observedvmm_list_topologies

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored 2026-08-06 05:30 across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with another. The purpose of vmm_list_topologies is clearly described and unambiguous.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern with a consistent namespace prefix (vmm_list_topologies), establishing a clear convention that is internally consistent.

Tool Count1/5

A single tool for a VMM server is an extreme mismatch. The description implies create, inspect, and modify operations that are entirely absent, making the tool surface far too thin for its apparent scope.

Completeness1/5

The server exposes only a list operation. There are no create, get, update, delete, or other management capabilities, leaving massive gaps that would prevent any meaningful workflow beyond discovery.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

jumpcloud-genaiOAuth
com.jumpcloud
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cloud Platforms Security Developer Tools
2
server B
io.cycloid.mcp
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Developer Tools CI/CD & DevOps Cloud Platforms
2
Airweave SearchOAuth
io.github.airweave-ai
MCP server for searching Airweave collections with natural language queries.
Search Art & Culture Open Data
25,729
Superserve
io.github.superserve-ai
MCP server for Superserve sandboxes: create, exec, and manage Firecracker microVMs
Virtualization Code Execution
2417

Related MCP Servers

mcp-proxmox
Virtualization Cloud Platforms Monitoring
antonio-mello-ai
A
license
A
quality
B
maintenance
MCP server for managing Proxmox VE clusters — provision VMs and containers, manage snapshots and backups, execute commands, browse storage, and monitor resources through natural language
Updated a month ago (2026-08-17 00:33 UTC)
34
107 PyPI
16
MIT
vsphere-mcp
Virtualization Cloud Platforms
fukui-yuto
A
license
Not graded
quality
D
maintenance
MCP server for VMware vSphere/vCenter operations, enabling natural language control of VMs, hosts, and infrastructure.
Updated 3 months ago (2026-06-22 17:24 UTC)
Apache 2.0
NetBox MCP Server
Networking & Infrastructure Developer Tools
epe105
F
license
Not graded
quality
D
maintenance
MCP server for interacting with NetBox API, enabling users to query and manage NetBox resources such as devices through natural language.
Updated a year ago (2025-10-29 17:51 UTC)
-
runn-mcp-server
Project Management Workplace & Productivity
gemini2026
F
license
Not graded
quality
C
maintenance
MCP server for the Runn API, enabling resource management and reporting through natural language.
Updated 8 months ago (2026-01-08 21:15 UTC)
-

vmm-mcp-server

Tools

Requirements

Install & build

Configuration

Running

Adding a new tool

Project layout

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

mcp-proxmox

vsphere-mcp

NetBox MCP Server

runn-mcp-server