cnv-lab-mcp

MCP server for reserving lab hardware in GLPI, triggering CNV cluster deployments in Jenkins, and importing ACM spoke clusters. No instance URLs, hardware names, or tokens are hardcoded — everything comes from tool arguments or environment variables.

Add to Cursor

Related MCP server: DCI MCP Server

Prerequisites

• Node.js >= 20

• A GLPI personal API token (My Settings → API tokens). Optional GLPI_APP_TOKEN if the instance requires one.

• A Jenkins API token (User → Configure → API Token) plus the short username, not an email. user@example.com returns 401; user works.

• GLPI profile must have a non-zero reservation right on the target entity.

• Jenkins account needs Job/Build and Job/Read on jobs you will trigger.

Internal TLS / NODE_EXTRA_CA_CERTS

Node's fetch (undici) does not use the OS/keychain CA store the way curl does. If curl works but the MCP server reports fetch failed, set NODE_EXTRA_CA_CERTS to your internal CA bundle and restart Cursor:

export NODE_EXTRA_CA_CERTS=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem

TLS errors are reported separately from generic network failures so this is not mysterious.

Configure

Copy .env.example and set:

Example mcp.json entry (secrets via env interpolation):

{
  "mcpServers": {
    "cnv-lab-mcp": {
      "command": "npx",
      "args": ["-y", "cnv-lab-mcp"],
      "env": {
        "GLPI_BASE_URL": "https://glpi.example.internal",
        "GLPI_USER_TOKEN": "${env:GLPI_USER_TOKEN}",
        "JENKINS_BASE_URL": "https://jenkins.example.internal",
        "JENKINS_USER": "${env:JENKINS_USER}",
        "JENKINS_API_TOKEN": "${env:JENKINS_API_TOKEN}",
        "NODE_EXTRA_CA_CERTS": "${env:NODE_EXTRA_CA_CERTS}"
      }
    }
  }
}

Until the package is on npm, point args at this repo instead:

"args": ["-y", "github:galkremer1/cnv-lab-mcp"]

Tools

Reservation:

• list_reservable_items — browse GLPI reservable assets

• find_available_cluster — match requirements (structured + free-text comments) and rank by earliest free slot. Does not book.

• check_availability — reservations + gaps for one item

• reserve_cluster — book a window; always sets users_id from the session

• cancel_reservation — release a booking

Jenkins:

• trigger_jenkins_job — generic trigger; start_at becomes delay=NNNsec

• get_build_status — queue/build + console tail

• abort_build — stop a build

Cluster access:

• get_cluster_info — non-sensitive metadata and console/API URLs from *-data.zip

• get_cluster_kubeconfig — auth/kubeconfig + auth/kubeadmin-password in memory only. Cluster-admin credentials; do not echo them back in chat.

ACM:

• import_spoke_cluster — ManagedCluster + KlusterletAddonConfig, apply import manifests to the spoke, poll join

• get_managed_cluster_status — hub-side join/available conditions

Scenarios (confirm-before-booking):

• list_scenarios

• plan_scenario — propose clusters/windows/parameters, book nothing

• execute_scenario — reserve + trigger from a plan

Built-in scenarios live in src/scenarios/catalog.json and can be extended by PR: basic-bm-cnv, acm-hub-and-spoke, sriov-cnv-cluster.

Development

npm install
npm test
npm run lint
npm run typecheck
npm run build

Manual smoke test against real instances (not run in CI):

npx tsx scripts/smoke.ts
SMOKE_JOB=deploy-ocp-bare-metal-cluster-with-abi-cnv-5.0 SMOKE_CLUSTER=example-cluster npx tsx scripts/smoke.ts

Security

• .env is gitignored. Examples use obviously fake placeholders.

• CI runs gitleaks on every push/PR.

• Client errors redact tokens and never log Authorization / user_token values.

• get_cluster_kubeconfig downloads the zip into a Buffer and extracts with JSZip in memory. It never writes the archive or auth/* to disk.

• get_cluster_info only reads deploydata.json, metadata.json, and install-config.backup.yaml.