cnv-lab-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cnv-lab-mcp Find an available cluster for a 2-day test starting Monday."
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.
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: quads-mcp
Prerequisites
Node.js >= 20
A GLPI personal API token (
My Settings→API tokens). OptionalGLPI_APP_TOKENif the instance requires one.A Jenkins API token (
User→Configure→API Token) plus the short username, not an email.user@example.comreturns 401;userworks.GLPI profile must have a non-zero
reservationright 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.pemTLS errors are reported separately from generic network failures so this is not mysterious.
Configure
Copy .env.example and set:
Variable | Required | Notes |
| yes | With or without |
| yes | Personal API token |
| no | Only if the instance requires it |
| yes | Jenkins root URL |
| yes | Short username (not email) |
| yes | API token |
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 assetsfind_available_cluster— match requirements (structured + free-text comments) and rank by earliest free slot. Does not book.check_availability— reservations + gaps for one itemreserve_cluster— book a window; always setsusers_idfrom the sessioncancel_reservation— release a booking
Jenkins:
trigger_jenkins_job— generic trigger;start_atbecomesdelay=NNNsecget_build_status— queue/build + console tailabort_build— stop a build
Cluster access:
get_cluster_info— non-sensitive metadata and console/API URLs from*-data.zipget_cluster_kubeconfig—auth/kubeconfig+auth/kubeadmin-passwordin 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 joinget_managed_cluster_status— hub-side join/available conditions
Scenarios (confirm-before-booking):
list_scenariosplan_scenario— propose clusters/windows/parameters, book nothingexecute_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 buildManual 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.tsSecurity
.envis gitignored. Examples use obviously fake placeholders.CI runs gitleaks on every push/PR.
Client errors redact tokens and never log
Authorization/user_tokenvalues.get_cluster_kubeconfigdownloads the zip into a Buffer and extracts with JSZip in memory. It never writes the archive orauth/*to disk.get_cluster_infoonly readsdeploydata.json,metadata.json, andinstall-config.backup.yaml.
Available Tools
15 toolsabort_buildA
Stop a running or queued Jenkins build (job/{name}/{build}/stop).
Inputs: job_name (required), build_number (required).
cancel_reservationB
Delete/release a GLPI reservation by id.
Inputs: reservation_id (required).
check_availabilityA
Fetch the full reservation list for one ReservationItem (paginated correctly) and compute free gaps / the first slot of duration_minutes.
Inputs: reservation_item_id (required), earliest_start, duration_minutes.
execute_scenarioA
Execute a plan from plan_scenario: reserve each role, trigger Jenkins jobs (delayed if start is in the future). ACM import runs only if wait_timeout_seconds is set and builds complete.
Inputs: plan (required), wait_timeout_seconds.
find_available_clusterA
Find reservable clusters matching requirements and rank them by earliest free slot of duration_minutes. Proposes slots only — does not book.
Inputs: duration_minutes (required), limit, itemtype, requirements, +1 more.
get_build_statusB
Poll Jenkins queue/build state. Returns building/result and a console-log tail.
Inputs: job_name (required), queue_id, build_number.
get_cluster_infoA
Return non-sensitive cluster metadata from a deploy job *-data.zip (deploydata.json, metadata.json, console/API URLs). Does not read kubeconfig or kubeadmin-password.
Inputs: job_name (required), build_number, cluster_name.
get_cluster_kubeconfigA
Extract auth/kubeconfig and auth/kubeadmin-password from a deploy job *-data.zip in memory. Returns cluster-admin credentials — do not echo them back in chat.
Inputs: job_name (required), build_number, cluster_name.
get_managed_cluster_statusB
Read ManagedCluster join/available conditions from the hub.
Inputs: cluster_name (required), hub_kubeconfig (required).
import_spoke_clusterA
Import a spoke into an ACM hub: create ManagedCluster + KlusterletAddonConfig, fetch the generated import Secret, apply manifests to the spoke, poll until Joined/Available.
Inputs: cluster_name (required), hub_kubeconfig (required), spoke_kubeconfig (required), timeout_seconds.
list_reservable_itemsB
Search GLPI for reservable assets (default itemtype Peripheral). Returns id, name, comment/capability text, and linked ReservationItem id.
Inputs: filter, itemtype.
list_scenariosA
List built-in end-to-end scenario presets (id, name, description, overridable fields).
Inputs: no named parameters.
plan_scenarioA
Resolve a scenario into a concrete unbooked plan (candidate clusters, windows, Jenkins parameters). Books and triggers nothing.
Inputs: scenario_id (required), overrides.
reserve_clusterA
Create a GLPI reservation. Always sets users_id from the authenticated session. Re-validates for conflicts immediately before booking.
Inputs: reservation_item_id (required), end, start, comment, +1 more.
trigger_jenkins_jobA
Trigger a Jenkins job with parameters. If start_at is in the future, passes delay=NNNsec so the build does not start immediately.
Inputs: job_name (required), start_at, parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Most tools have distinct resource-action targets, but a few boundaries could be sharper: check_availability and find_available_cluster both deal with availability, and get_cluster_info vs. get_cluster_kubeconfig both extract from the same deploy artifact. Descriptions clarify the difference well enough that an agent can usually choose correctly.
All 15 tool names follow a consistent snake_case verb_noun convention (list, check, find, reserve, cancel, trigger, get, abort, import, plan, execute). There are no camelCase names, vague single verbs, or arbitrary suffixes.
Fifteen tools is at the upper end of the ideal range but appropriate for the server's scope: reservation management, Jenkins build control, cluster artifact access, ACM import/monitoring, and scenario orchestration. Each tool covers a distinct step and no tool feels redundant.
The core path from finding/reserving assets, triggering and monitoring builds, extracting cluster credentials, and importing a spoke into ACM is covered. However, the lifecycle lacks cleanup operations (e.g., deleting/detaching a ManagedCluster, removing an imported spoke) and there is no dedicated way to list or look up existing reservations before canceling.
Maintenance
Related MCP Connectors
MCP server for GLPI: tickets, ITIL, assets, knowledge base. GLPI 10/11. Not affiliated with Teclib'.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
MCP server for Appcircle mobile CI/CD platform.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for automating VLP lab VM operations, exposing VM management tools to AI agents like Cursor and Claude Code.-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.MIT
- FlicenseAqualityDmaintenanceAn MCP server for OpenShift Baremetal IPI cluster provisioning, allowing users to generate and validate install-config.yaml files, test BMC connectivity, validate networks, and manage cluster installation lifecycle.24-
- FlicenseAqualityDmaintenanceMCP server for IBM Technology Zone: manage reservations end-to-end and search the catalog from Claude.11-