Skip to content
PluginStats

@calltelemetry/ct-lab-mcp weekly downloads statistics

By calltelemetry · npm · MCP servers

Expanded Model Context Protocol (MCP) server for Call Telemetry lab, fleet, and appliance management across Proxmox VE (ESXi is retired).

View on npm Fresh · Oct 28, 2026

@calltelemetry/ct-lab-mcp has 9,922 recorded weekly downloads on npm, ranking #1006 of 2,644 tracked listings.

Weekly downloads
9,922
Official API · Oct 26, 2026
7-day growth
—
Insufficient history
30-day growth
—
Insufficient history
90-day growth
—
Insufficient history
Rank
#1006
Among tracked npm listings

About @calltelemetry/ct-lab-mcp

@calltelemetry/ct-lab-mcp

Model Context Protocol (MCP) Server for Unified Call Telemetry Lab, Fleet, and Appliance Management across Proxmox VE (ESXi is retired)

NPM Version License: MIT TypeScript Node Version

@calltelemetry/ct-lab-mcp is the single public MCP façade for Call Telemetry lab operations. It exposes high-level hypervisor management (Proxmox VE only; ESXi was retired 2026-10-15), disposable VM workflows, and secure appliance diagnostics while delegating canonical asset identity, lease ownership, and release-line policy to the private lab-inventory CLI supplied by ct-meta.


Architecture

AI Clients (Claude Desktop / Cursor / Web / AI Agents)
                  │
                  ▼
       [MCP Server / Transports]
       ├── Stdio Transport (stdout JSON-RPC, stderr SafeLogger)
       └── Express SSE Transport (/sse, /messages, /health)
                  │
                  ▼
         [MCP Tool Registry]
  ├── list_hosts          (Proxmox capacity: live free RAM/CPU/disk, health; 8GB unit estimates are deprecated)
  ├── list_inventory      (Unified VM fleet inventory with Linear tags)
  ├── claim_slot          (DEPRECATED alias -> create_appliance_claim; slot retirement ADR (REL-1746))
  ├── release_slot        (DEPRECATED alias -> delete_appliance_claim)
  ├── find_slot / list_slots (DEPRECATED aliases -> list_hosts / list_appliance_claims)
  ├── purge_slots         (RETIRED: explicit SLOT_VERB_RETIRED error; use list_expired_vms / cleanup_expired_vms)
  ├── provision_vm        (Disposable VM provisioning on Proxmox)
  ├── proxmox_quick_provision (Size-driven Proxmox fleet plan/apply; host=auto ranks by free RAM then disk)
  ├── pin_pool_slots      (RETIRED: explicit SLOT_VERB_RETIRED error; pass webImage to proxmox_quick_provision)
  ├── vm_action           (Power lifecycle with non-bypassable safety guardrails)
  ├── host_maintenance_shutdown (Guarded whole-host drain and graceful shutdown)
  ├── lab_mission         (Canonical manifest-bound multi-phase mission)
  ├── lab_dev             (Canonical leased remote-development lifecycle)
  ├── list_appliance_claims (Kubernetes ApplianceClaim CRD fleet discovery)
  ├── create_appliance_claim (Declarative CRD provisioning; profile=demo|bare|bundle; demo/bundle allocate node, vmid, vmName and targetIp from the canonical lab inventory and return `allocation`; bundle installs the exact release bundle with install-exact-release.sh, no OVA; bare tracks an existing guest with explicit vmid+vmName; node defaults to auto: least-loaded eligible Proxmox host, recorded in calltelemetry.com/placement)
  ├── list_held_claims    (Read-only: claims the operator holds instead of destroying, from its audit report)
  ├── lab_capacity        (Read-only: per node free RAM, the reserve and the claims holding RAM, grouped active/expired/paused/held/deleting/wedged/fixture)
  ├── release_appliance_claim_without_destroy (Ask the operator to drop a claim and leave the guest; honoured only for a template, absent guest or guest-less claim)
  ├── renew_appliance_claim (Extend a claim TTL; never shortens)
  ├── claimed_import_qcow (Image to claimed guest: claim-first bare claim, then canonical vm provision --source published-qcow)
  ├── delete_appliance_claim (Operator teardown trigger via CRD finalizer)
  ├── sideload_appliance_runner (Isolated runner commands & container overrides)
  ├── get_appliance_id    (Hardware UUID -> CT-APP-XXXX-XXXX-XXXX derivation)
  ├── sideload_license    (Standardized calltelemetry-license-v2 envelope)
  ├── verify_appliance_demo (Automated 5-point demo verification gate)
  ├── appliance_update    (Plan/apply a release update of a claimed guest via canonical lab-inventory vm update)
  ├── uat_credential      (Executor-mediated UAT credential injection: claim-authorized grant of an opaque single-use handle; redeem runs the executor-configured UAT runner with the credential in the child env only; the value is never returned)
  └── appliance_exec      (RETIRED: refuses with CANONICAL_PHYSICAL_SLOT_AUTHORITY_REQUIRED; see appliance_update, uat_access)
                  │
  ┌───────────────┼───────────────┬───────────────────┐
  ▼               ▼               ▼                   ▼
[MultiHypervisor] [Slot Engine]   [Safety Guardrails] [Appliance SSH]
  └── Proxmox VE   ├── ProxmoxLab  ├── Proxmox fixtures ├── ssh2 port 2222
      (lab, mini,  │   (2x8GB max) │   (100-104, 9000s) ├── cli.sh / db vacuum
       ibm64)      ├── ProxmoxMini └── CUCM, CUBE,      ├── migrate / logs
                   │   (4x8GB max)     Runners, K8s     └── Redaction Engine
                   └── ProxmoxIbm64
                          │
                          ▼
            [Lab Credential Resolver]
            ├── Tier 1: Process Environment (LAB_PROXMOX_*, LAB_VM_*)
            ├── Tier 2: Doppler REST API v3 (DOPPLER_TOKEN)
            └── Tier 3: In-Memory Mock Fallback / Offline Dev

In a governed ct-meta installation there is only one registered MCP server: @calltelemetry/ct-lab-mcp. The Python lab-inventory program remains a private canonical policy engine behind the Node façade; it is not registered as a second public MCP. Set CT_LAB_CANONICAL_REQUIRED=1 to fail closed rather than use the legacy Node VMID/name slot state when the bridge is unavailable.


Key Features…

Description from the npm listing.

  • mcp
  • model-context-protocol
  • proxmox
  • hypervisor
  • slot-scheduler
  • doppler
  • calltelemetry
  • appliance
  • ssh

README badge

Show your rank in a README or on your website. The badge updates automatically.

Charts

Images: 30d · 1y · all time · 1600×900 dark

Adoption over time

@calltelemetry/ct-lab-mcp weekly downloads on npm, last 90 days: 9,922 weekly downloads as of Oct 26, 2026.@calltelemetry/ct-lab-mcpWeekly downloads on npm · Last 90 days9,922downloads / week8.5K9K9.5K10K10.5K11KJul 28Aug 12Aug 27Sep 11Sep 26Oct 11Oct 26downloads / weekOct 26, 2026 – Oct 26, 2026 · 1 observations · Updated Oct 26, 2026pluginstats.com
@calltelemetry/ct-lab-mcp weekly downloads on npm, last 90 days: 9,922 weekly downloads as of Oct 26, 2026.

7/30/90-day growth

@calltelemetry/ct-lab-mcp weekly downloads growth on npm: 7-day growth unavailable, 30-day growth unavailable, 90-day growth unavailable.@calltelemetry/ct-lab-mcpWeekly downloads growth on npm9,922downloads / week now7-day growthinsufficient historyInsufficient history30-day growthinsufficient historyInsufficient history90-day growthinsufficient historyInsufficient historyGrowth vs. nearest observation to each baseline date · Updated Oct 26, 2026pluginstats.com
@calltelemetry/ct-lab-mcp weekly downloads growth on npm: 7-day growth unavailable, 30-day growth unavailable, 90-day growth unavailable.

Ranking history

@calltelemetry/ct-lab-mcp npm ranking history: currently #1006 (by weekly downloads).@calltelemetry/ct-lab-mcpnpm ranking · by weekly downloads · Last 90 days#1006current rank#1004#1005#1006#1007#1008Jul 30Aug 14Aug 29Sep 13Sep 28Oct 13Oct 28rankOct 28, 2026 – Oct 28, 2026 · 1 observations · Updated Oct 26, 2026pluginstats.com
@calltelemetry/ct-lab-mcp npm ranking history: currently #1006 (by weekly downloads).

Listing placement

All npm2,642 listings · 133 pages · 1,322 shown · page 54, #17 (overall #1,077)
All npm: every listing in weekly downloads order

Listing placement

MCP servers361 listings · 19 pages · page 11, #5 (overall #205)
MCP servers: every listing in weekly downloads order

Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.

Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.

Recent observations

Full history (1)
Recent weekly downloads observations for @calltelemetry/ct-lab-mcp
Date (UTC)Weekly downloadsChange vs. previous
9,922—

Similar npm MCP servers plugins

All 20 @calltelemetry/ct-lab-mcp alternatives

Data source

Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.

Listing: https://www.npmjs.com/package/@calltelemetry/ct-lab-mcp. First seen Oct 28, 2026; last successful collection Oct 28, 2026. See the methodology.