Xen Orchestra MCP server

Name: Xen Orchestra MCP server
Author: Vates

Query and, if enabled, manage XCP-ng pools, hosts, VMs and backups through Xen Orchestra

Official · Vates TypeScript Local · stdio Cloud platforms DevOps and monitoring

GitHub npm Website

47 popularity score ★ 996 ↓ 163/wk

Connect your client

Local (npm)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.

Or add it by command or config

It needs XO_URL, XO_TOKEN. Replace each <NAME> with your value.

Claude CodeTerminal

claude mcp add xen-orchestra -e XO_URL=<XO_URL> -e XO_TOKEN=<XO_TOKEN> -- npx -y @xen-orchestra/mcp

Claude Desktopclaude_desktop_config.json

{
  "mcpServers": {
    "xen-orchestra": {
      "command": "npx",
      "args": [
        "-y",
        "@xen-orchestra/mcp"
      ],
      "env": {
        "XO_URL": "<XO_URL>",
        "XO_TOKEN": "<XO_TOKEN>"
      }
    }
  }
}

Cursor~/.cursor/mcp.json

{
  "mcpServers": {
    "xen-orchestra": {
      "command": "npx",
      "args": [
        "-y",
        "@xen-orchestra/mcp"
      ],
      "env": {
        "XO_URL": "<XO_URL>",
        "XO_TOKEN": "<XO_TOKEN>"
      }
    }
  }
}

VS Code.vscode/mcp.json

{
  "servers": {
    "xen-orchestra": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@xen-orchestra/mcp"
      ],
      "env": {
        "XO_URL": "<XO_URL>",
        "XO_TOKEN": "<XO_TOKEN>"
      }
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.xen-orchestra]
command = "npx"
args = ["-y", "@xen-orchestra/mcp"]

[mcp_servers.xen-orchestra.env]
XO_URL = "<XO_URL>"
XO_TOKEN = "<XO_TOKEN>"

Gemini CLITerminal

gemini mcp add --scope user -e XO_URL=<XO_URL> -e XO_TOKEN=<XO_TOKEN> xen-orchestra npx -- -y @xen-orchestra/mcp

Settings 7

`XO_URL`	Required: Address of the Xen Orchestra server, e.g. https://xo.example.com.
`XO_TOKEN`	Required: XO authentication token; or set XO_USERNAME and XO_PASSWORD instead. The token wins when both are set.
`XO_USERNAME`	Optional: XO admin user, used when no token is given.
`XO_PASSWORD`	Optional: Password for XO_USERNAME.
`XO_MCP_ENABLE_ACTIONS`	Optional: Set to 1 to add the write {domain}_action tools; read-only otherwise.
`XO_MCP_DENY_LIST`	Optional: Comma-separated operationIds to drop, e.g. DeleteVm,HardShutdownVm.
`HTTPS_PROXY`	Optional: Outbound proxy for HTTPS requests (HTTP_PROXY and NO_PROXY are also read).

What it does

@xen-orchestra/mcp is Vates' own MCP server for Xen Orchestra (XO), the web management layer for XCP-ng and XenServer. It runs on your machine over stdio and talks to an XO instance through its REST API, so an assistant can answer questions about pools, hosts, VMs, storage repositories, networks, backup jobs, alarms and tasks.

Its tools are not a fixed list. At start it downloads the OpenAPI spec from your XO server (/rest/v0/docs/swagger.json) and creates one {domain}_query tool per resource group, each taking an operation name plus optional id, filter, fields and limit. A newer XO therefore brings new tools without a new package release. Three utility tools are always present: a connection check, a documentation search and an infrastructure summary.

By default it only reads. Setting XO_MCP_ENABLE_ACTIONS=1 adds a {domain}_action tool per group for create, update and delete operations, from snapshots to VM deletion or a pool emergency shutdown. Each action first returns a preview and a one-time confirm_token that must be sent back within five minutes before anything runs. XO_MCP_DENY_LIST removes named operations entirely.

In the code (src/xo-client.mts), every request to XO is cut off after 30 seconds and the start-up check that MCP is enabled on the server after 10 seconds; a token is sent as XO's authenticationToken cookie, a username and password as HTTP Basic auth.

What it needs

Runtime	Node.js 20+

Node.js 20 or later (the docs launch it with npx). A running Xen Orchestra 6.5 or later with the REST API enabled; older versions fail at start with 'Unable to verify MCP status (HTTP 404)'. An XO account: either an authentication token (made on the XO /user page or with xo-cli create-token) or a username and password of a user with admin rights. The XO admin must not have turned MCP off in xo-server's config ([mcp] enabled = false).

Limits

Read-only unless XO_MCP_ENABLE_ACTIONS=1 is set. Stats endpoints and binary downloads (.xva, .ova, .vhd, .raw exports) are not exposed as tools. The tool list depends on the XO version it connects to, so the domains listed here are those of a current xo-server. One process serves one XO instance; several instances need one entry each. Proxy support is Basic auth only (no NTLM or Kerberos) and NO_PROXY takes no CIDR ranges. If an admin disables MCP on the XO side, the server exits at start with 'MCP disabled by admin'. Each request to XO times out after 30 seconds.

Who it suits

Suits XCP-ng / Xen Orchestra administrators on XO 6.5 or later who want to ask about their infrastructure, inventory and backup status in plain language, with the option to allow guarded changes behind a confirm step. Because it is from Vates and builds its tools from XO's own API spec, it tracks the product closely. Not for older XO releases, for VMware, Proxmox or plain Xen without XO, or for pulling performance stats and disk exports, which it leaves to the REST API directly.

Tools 32

check_connection: Checks that the configured XO server can be reached and signed in to
search_documentation: Searches and fetches pages of the Xen Orchestra documentation
get_infrastructure_summary: Builds a markdown overview of pools, hosts and VMs
pools_query: Reads pools
hosts_query: Reads hosts
vms_query: Reads VMs, templates, snapshots and controllers
vdis_query: Reads virtual disks and their snapshots
srs_query: Reads storage repositories
vbds_query: Reads VM-to-disk attachments
pbds_query: Reads host-to-storage connections
networks_query: Reads networks
vifs_query: Reads VM network interfaces
pifs_query: Reads host physical interfaces
backup_jobs_query: Reads backup jobs
backup_logs_query: Reads backup run logs
restore_logs_query: Reads restore logs
backup_repositories_query: Reads backup repositories
backup_archives_query: Reads backup archives
schedules_query: Reads job schedules
users_query: Reads XO users
groups_query: Reads XO user groups
servers_query: Reads the pool servers XO is connected to
alarms_query: Reads alarms
messages_query: Reads XAPI messages
events_query: Reads events
tasks_query: Reads running and past tasks
proxies_query: Reads XO proxies
pgpus_query: Reads physical GPUs
pcis_query: Reads PCI devices
sms_query: Reads storage managers
xoa_query: Reads XOA appliance information
docs_query: Reads the REST API's own documentation endpoints

Popularity

47 popularity score, on our list (the bar is 36)

★ 996 ↓ 163/wk

GitHub stars, whole repository	996	17.7 points
Stars in 30 days	+4	3.5 points
npm downloads, last week	163	17.7 points
Official server	Yes	8 points

It lives in the folder @xen-orchestra/mcp of vatesfr/xen-orchestra, which holds more than this server. Its stars are the whole repository's, so in the score they never count for more than its own downloads.

Measured 2026-11-07. How the score works.

Where it is published

Code	vatesfr/xen-orchestra/@xen-orchestra/mcp ★ 996, the whole repository
npm	@xen-orchestra/mcp 1.4.3, 2026-09-25

What it can reach

Runs	On your machine
Reaches	Cloud resources, The internet, Your account at a service
Changes things	Yes: it can write, send, create or delete
Sign-in	An API key or token
Licence	AGPL-3.0-or-later (npm)
Last code change	2026-10-28

Runs locally under Node and connects to the XO server you name, with a token or an admin username and password; it can see whatever that account can see. With default settings only read tools are created. With XO_MCP_ENABLE_ACTIONS=1 it can create, change and delete VMs, snapshots, backups and other objects, up to a pool emergency shutdown, each gated by a preview and a one-time confirm token valid for five minutes. Its makers state that the MCP exposure tags limit what the assistant is offered, not what the account may do: XO's own RBAC/ACL is the access control, so a least-privileged account limits the reach. search_documentation fetches Xen Orchestra's public docs. An XO admin can switch MCP off server-side.

Over time

GitHub stars, whole repository 996 +4

997992

10 Oct 20267 Nov 2026

npm downloads a week 163 +140 (+609 %)

2.2k18

9 Mar 20267 Nov 2026

Before the site measured it, read from npm's daily download counts.

Popularity score 47 −15 (−24 %)

6240

10 Oct 20267 Nov 2026

What is rising across the directory

Sources

Page checked 2026-10-14.

Badge for your README

Shows this server's rank in its category, and stars for a server that runs on your machine. It updates every hour.

MarkdownREADME.md

[![Xen Orchestra MCP server on EveryMCPServer](https://everymcpserver.com/badge/xen-orchestra.svg)](https://everymcpserver.com/servers/xen-orchestra)

Connect your client

Add in one click

Or add it by command or config

Settings 7

What it does

What it needs

Limits

Who it suits

Tools 32

Similar servers

Kubernetes MCP Server

StackQL MCP Server

Azure MCP Server

Pulumi MCP Server

MCP Server Kubernetes

Harness MCP Server