cnv-lab-mcp
cnv-lab-mcp
MCP-Server zur Reservierung von Labor-Hardware in GLPI, zum Auslösen von CNV-Cluster-Deployments in Jenkins und zum Importieren von ACM-Spoke-Clustern. Es sind keine Instanz-URLs, Hardwarenamen oder Token fest kodiert – alles stammt aus Tool-Argumenten oder Umgebungsvariablen.
Zu Cursor hinzufügen
Related MCP server: quads-mcp
Voraussetzungen
Node.js >= 20
Ein persönlicher GLPI-API-Token (
My Settings→API tokens). OptionalGLPI_APP_TOKEN, falls die Instanz einen benötigt.Ein Jenkins-API-Token (
User→Configure→API Token) sowie den Kurz-Benutzernamen, nicht eine E-Mail-Adresse.user@example.comliefert 401;userfunktioniert.Das GLPI-Profil muss auf der Ziel-Entity ein
reservation-Recht ungleich Null haben.Das Jenkins-Konto benötigt Job/Build und Job/Read für die Jobs, die Sie auslösen werden.
Interne TLS / NODE_EXTRA_CA_CERTS
Der fetch von Node.js (undici) verwendet nicht den OS-/Schlüsselbund-CA-Speicher, wie es curl tut. Wenn curl funktioniert, aber der MCP-Server fetch failed meldet, setzen Sie NODE_EXTRA_CA_CERTS auf Ihr internes CA-Bundle und starten Sie Cursor neu:
export NODE_EXTRA_CA_CERTS=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pemTLS-Fehler werden getrennt von allgemeinen Netzwerkfehlern gemeldet, damit das nicht rätselhaft bleibt.
Konfiguration
Kopieren Sie .env.example und setzen Sie:
Variable | Erforderlich | Hinweise |
| ja | Mit oder ohne |
| ja | Persönlicher API-Token |
| nein | Nur falls die Instanz einen benötigt |
| ja | Jenkins-Root-URL |
| ja | Kurz-Benutzername (nicht E-Mail) |
| ja | API-Token |
Beispiel-Eintrag in mcp.json (Geheimnisse per 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}"
}
}
}
}Bis das Paket auf npm verfügbar ist, verweisen Sie mit args stattdessen auf dieses Repository:
"args": ["-y", "github:galkremer1/cnv-lab-mcp"]Tools
Reservierung:
list_reservable_items— GLPI-reservierbare Assets durchsuchenfind_available_cluster— Anforderungen abgleichen (strukturiert + Freitext-Kommentare) und nach dem frühesten freien Slot sortieren. Bucht nichts.check_availability— Reservierungen + Lücken für ein Elementreserve_cluster— ein Zeitfenster buchen; setztusers_idimmer aus der Sitzungcancel_reservation— eine Buchung freigeben
Jenkins:
trigger_jenkins_job— generischer Trigger;start_atwird zudelay=NNNsecget_build_status— Warteschlange/Build + Konsolenausgabeabort_build— einen Build stoppen
Clusterzugriff:
get_cluster_info— nicht vertrauliche Metadaten und Konsolen-/API-URLs aus*-data.zipget_cluster_kubeconfig—auth/kubeconfig+auth/kubeadmin-passwordnur im Speicher. Cluster-Admin-Zugangsdaten; geben Sie sie nicht im Chat wieder.
ACM:
import_spoke_cluster— ManagedCluster + KlusterletAddonConfig, Import-Manifeste auf den Spoke anwenden, Join abfragenget_managed_cluster_status— Hub-seitige Join-/Verfügbarkeits-Bedingungen
Szenarien (Bestätigung vor der Buchung):
list_scenariosplan_scenario— Cluster/Fenster/Parameter vorschlagen, nichts buchenexecute_scenario— aus einem Plan reservieren + auslösen
Eingebaute Szenarien liegen in src/scenarios/catalog.json und können per PR erweitert werden: basic-bm-cnv, acm-hub-and-spoke, sriov-cnv-cluster.
Entwicklung
npm install
npm test
npm run lint
npm run typecheck
npm run buildManueller Smoke-Test gegen echte Instanzen (nicht in CI ausgeführt):
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.tsSicherheit
.envist von Git ignoriert. Beispiele verwenden offensichtlich unechte Platzhalter.CI führt bei jedem Push/PR gitleaks aus.
Client-Fehler maskieren Token und protokollieren niemals die Werte von
Authorization/user_token.get_cluster_kubeconfiglädt die Zip-Datei in einen Buffer und extrahiert sie mit JSZip im Speicher. Es schreibt weder das Archiv nochauth/*auf die Festplatte.get_cluster_infoliest nurdeploydata.json,metadata.jsonundinstall-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-