Performance Co-Pilot vs ESXi Read-Only Diagnostics
Performance Co-Pilot is an MCP server published by major. Marketplaces we read that list it: 1 (Official MCP Registry). ESXi Read-Only Diagnostics is an MCP server published by nicolasboattini. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Performance Co-Pilot |  ESXi Read-Only Diagnostics |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.1 Downloads/month (PyPI): 185 Downloads/week (PyPI): 53 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (PyPI): 249 Downloads/week (PyPI): 31 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Performance Co-Pilot | ESXi Read-Only Diagnostics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (pcp-mcp) | On your machine (esxi-readonly-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 5, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/major/pcp-mcp | github.com/nicolasboattini/esxi-readonly-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Performance Co-Pilot
Query system performance metrics via MCP - CPU, memory, disk I/O, network, processes
ESXi Read-Only Diagnostics
Read-only VMware ESXi diagnostics: CPU Ready, disk latency, snapshots, real space, hardware health.
How to run each
Performance Co-Pilot As a local MCP server: PyPI package
claude mcp add --transport stdio pcp -- uvx pcp-mcpESXi Read-Only Diagnostics As a local MCP server: PyPI package
claude mcp add --env "ESXI_HOST=<YOUR_ESXI_HOST>" --env "ESXI_PASSWORD=<YOUR_ESXI_PASSWORD>" --env "ESXI_USER=<YOUR_ESXI_USER>" --transport stdio esxi-readonly-mcp -- uvx esxi-readonly-mcpRequires: ESXI_HOST, ESXI_PASSWORD (secret), ESXI_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Performance Co-Pilot asks for
PCP_HOSTPCP_PORTPCP_TARGET_HOST
Only ESXi Read-Only Diagnostics asks for
ESXI_HOSTESXI_PASSWORD (secret)ESXI_PORTESXI_USERESXI_VERIFY_SSL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Performance Co-Pilot · What it can do: ESXi Read-Only Diagnostics · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.