proliant-mcp 0.6.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,416 @@
1
+ Metadata-Version: 2.4
2
+ Name: proliant-mcp
3
+ Version: 0.6.1
4
+ Summary: MCP server for HPE compute: read-only tools for ProLiant iLO (Redfish), HPE Compute Ops Management (GreenLake) and HPE OneView / Synergy
5
+ Keywords: mcp,hpe,proliant,ilo,redfish,oneview,synergy,compute-ops-management,greenlake,fastmcp,ai-agent
6
+ Author: hjma29
7
+ License-Expression: MIT
8
+ Classifier: Development Status :: 4 - Beta
9
+ Classifier: Intended Audience :: System Administrators
10
+ Classifier: Operating System :: OS Independent
11
+ Classifier: Programming Language :: Python :: 3
12
+ Classifier: Topic :: System :: Systems Administration
13
+ Requires-Dist: fastmcp>=4.2.0
14
+ Requires-Dist: httpx>=0.27
15
+ Requires-Python: >=3.12
16
+ Project-URL: Homepage, https://github.com/hjma29/proliant-mcp
17
+ Project-URL: Repository, https://github.com/hjma29/proliant-mcp
18
+ Project-URL: Changelog, https://github.com/hjma29/proliant-mcp/blob/main/CHANGELOG.md
19
+ Project-URL: Issues, https://github.com/hjma29/proliant-mcp/issues
20
+ Description-Content-Type: text/markdown
21
+
22
+ # proliant-mcp
23
+
24
+ An [MCP](https://modelcontextprotocol.io) server for **HPE compute**, built with
25
+ [FastMCP](https://gofastmcp.com). It gives AI assistants and agents (GitHub
26
+ Copilot, Claude, Google ADK, ...) live, read-only access to three HPE
27
+ management sources:
28
+
29
+ | Source | What it is | Scope | Tools |
30
+ |---|---|---|---|
31
+ | **HPE iLO** (Redfish) | The management processor in every ProLiant server | One server, deepest detail | unprefixed (`get_server_summary`, ...) |
32
+ | **HPE Compute Ops Management** (COM) | HPE GreenLake cloud service for ProLiant fleets | Whole fleet, any site | `com_*` |
33
+ | **HPE OneView** | On-prem appliance for ProLiant / Synergy (Synergy Composer) | Servers, profiles, frames, interconnects | `oneview_*` |
34
+
35
+ Ask things like *"which servers in COM are critical and why"*, *"any active
36
+ OneView alerts on the Synergy frame"*, or *"what switch port is dl345-gen12's
37
+ NIC on"*, and the assistant answers from live data. Every tool returns
38
+ compact JSON shaped for an AI model, not a human table.
39
+
40
+ Tested against iLO 5/6/7 (Synergy 480 Gen10, DL380 Gen11, DL325/DL345 Gen12),
41
+ Synergy Composer2 running OneView 11.10, and COM (`us-west`). The COM and OneView
42
+ logic comes from [proliant-cli](https://github.com/hjma29/proliant-cli), the
43
+ human-facing CLI for the same three sources.
44
+
45
+ > Status: **v0.6, read-only.** Nothing in this version changes a server. See [CHANGELOG.md](https://github.com/hjma29/proliant-mcp/blob/main/CHANGELOG.md).
46
+
47
+ ## Tools
48
+
49
+ **Start here:** `list_servers` returns every configured iLO, OneView appliance and COM account.
50
+
51
+ ### iLO (one server)
52
+
53
+ | Tool | What it returns |
54
+ |---|---|
55
+ | `get_server_summary` | Model, product ID, serial, power and POST state, health, UID, BIOS and iLO version, CPU/memory totals |
56
+ | `get_fleet_summary` | `get_server_summary` for all configured iLOs in parallel; failures are per server |
57
+ | `get_ilo_info` | iLO model and firmware version/date, license, COM connection status, iLO IP/MAC/DHCP/DNS |
58
+ | `get_health` | Overall and per-subsystem health, fan and power-supply redundancy |
59
+ | `get_firmware_inventory` | Every firmware component and version |
60
+ | `get_processors` | CPUs and GPUs |
61
+ | `get_memory` | Total, populated/empty slots, each DIMM |
62
+ | `get_storage` | Controllers, drives, RAID volumes |
63
+ | `get_network_adapters` | NICs, ports, MACs, link, LLDP neighbor (switch and port) |
64
+ | `get_event_log` | Newest IML (hardware) or IEL (iLO) entries, filter by severity |
65
+ | `redfish_get` | Raw read-only GET of any `/redfish/v1/...` resource |
66
+
67
+ ### HPE Compute Ops Management (fleet)
68
+
69
+ | Tool | What it returns |
70
+ |---|---|
71
+ | `com_get_overview` | Fleet report: counts by health, power, connection, generation, model; servers needing attention; disconnected servers; soonest subscription expirations; active alerts by severity |
72
+ | `com_list_servers` | Every COM server (filter by health, connected, name): serial, model, health, power, iLO, OS, subscription, firmware bundle. `include_hardware` adds CPU and GPU columns |
73
+ | `com_list_gpus` | GPU report for the whole fleet in one call: per server model, iLO firmware, CPU and GPUs, totals by GPU model, servers with no cached inventory |
74
+ | `com_get_server` | One server by name, serial, iLO IP or id: per-subsystem health, firmware inventory, CPU and GPUs (with serial numbers), last firmware update, active alerts |
75
+ | `com_list_alerts` | Newest alerts, uncleared by default; filter by server and severity |
76
+ | `com_list_jobs` | Newest jobs (firmware updates, inventory, OneView sync) with state and result |
77
+ | `com_list_groups` | Server groups, members and firmware / iLO-settings compliance |
78
+ | `com_list_firmware_bundles` | SPPs and patch bundles available in COM |
79
+ | `com_api_get` | Raw read-only GET of any `/compute-ops-mgmt/...` resource (secrets redacted) |
80
+
81
+ ### HPE OneView / Synergy
82
+
83
+ | Tool | What it returns |
84
+ |---|---|
85
+ | `oneview_get_appliance` | Appliance model and version, appliance resource health, resource counts, server status, active alerts by severity |
86
+ | `oneview_list_server_hardware` | Servers: status, power, profile, enclosure/bay, CPU, memory, ROM, OS, iLO |
87
+ | `oneview_get_server_hardware` | One server by name, OS hostname, serial or iLO IP: firmware components and active alerts |
88
+ | `oneview_list_server_profiles` | Profiles: assigned hardware, template and compliance, firmware baseline |
89
+ | `oneview_list_alerts` | Newest alerts (active by default) with corrective action |
90
+ | `oneview_list_enclosures` | Synergy frames: status, bays, Composers, power, PSUs, failed fans |
91
+ | `oneview_list_interconnects` | Virtual Connect / switch modules: model, firmware, status, IP |
92
+ | `oneview_list_firmware_baselines` | SPP / Synergy Service Packs uploaded to OneView |
93
+ | `oneview_rest_get` | Raw read-only GET of any `/rest/...` resource (sessions and users blocked, secrets redacted) |
94
+
95
+ ### Setup (pop-ups in the chat)
96
+
97
+ | Tool | What it does |
98
+ |---|---|
99
+ | `add_server` | Add one iLO or OneView: pop-up for type, address, name and user name, then a secure page for the password; the login is checked before saving |
100
+ | `import_inventory` | Import many from an `.ini` or `.csv` file whose path you type in a pop-up; optional shared password and login checks |
101
+ | `com_login` | Sign in to HPE GreenLake with pop-ups (email, then Okta Verify number or a secure password page); creates a GreenLake API client for you (see Configure > HPE Compute Ops Management) |
102
+
103
+ Every other tool is annotated `readOnlyHint`. The setup tools change no server: `add_server` and
104
+ `import_inventory` only edit the inventory file on this computer, and `com_login` also creates a
105
+ GreenLake API client. None of them takes a password (or, for `import_inventory`, a file path) as an
106
+ argument, so the AI cannot see a password or choose which file is read.
107
+
108
+ ## Install
109
+
110
+ The only prerequisite is [uv](https://docs.astral.sh/uv/), which also fetches
111
+ Python 3.12+ when needed. **No git, no admin rights and no clone are required**;
112
+ CI proves this on clean Windows, Linux and macOS machines.
113
+
114
+ ### Windows (PowerShell)
115
+
116
+ ```powershell
117
+ # 1. Install uv for your user only (no admin). Or: winget install --id astral-sh.uv
118
+ powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
119
+ ```
120
+
121
+ Open a **new** PowerShell window, then check that it installs and starts (should print `proliant-mcp <version>: 33 tools` and `(up to date)`):
122
+
123
+ ```powershell
124
+ uvx proliant-mcp@latest --check
125
+ ```
126
+
127
+ ### macOS / Linux
128
+
129
+ ```bash
130
+ curl -LsSf https://astral.sh/uv/install.sh | sh
131
+ uvx proliant-mcp@latest --check
132
+ ```
133
+
134
+ Configure at least one iLO, OneView appliance or COM account (next section), then check that each one accepts the login:
135
+
136
+ ```bash
137
+ uvx proliant-mcp@latest --check --connect
138
+ ```
139
+
140
+ It prints each iLO (model, iLO version), OneView appliance (model, software version) and
141
+ COM account (server count), or the reason a login failed.
142
+
143
+ ### Add it to your AI client (stdio)
144
+
145
+ VS Code / GitHub Copilot (**MCP: Open User Configuration**), Claude Desktop
146
+ (**Settings > Developer > Edit Config**) and other clients all take the same command:
147
+
148
+ ```json
149
+ {"servers": {"proliant": {"type": "stdio", "command": "uvx", "args": ["proliant-mcp@latest"]}}}
150
+ ```
151
+
152
+ Claude Desktop uses the top-level key `mcpServers` instead of `servers`. Credentials come from
153
+ your inventory file (next section), so none go in this JSON. If the client cannot find `uvx`,
154
+ restart it after installing uv, or use the full path (`%USERPROFILE%\.local\bin\uvx.exe`).
155
+
156
+ ### Update
157
+
158
+ `proliant-mcp@latest` makes `uvx` check [PyPI](https://pypi.org/project/proliant-mcp/) for a new
159
+ release each time the AI client starts the server (a fraction of a second when nothing changed).
160
+ To update, **restart the AI client** (in VS Code: **MCP: List Servers > proliant > Restart**).
161
+ Plain `proliant-mcp` without `@latest` keeps using the copy `uvx` cached first.
162
+
163
+ - **What's new:** [CHANGELOG.md](https://github.com/hjma29/proliant-mcp/blob/main/CHANGELOG.md) and the
164
+ [releases page](https://github.com/hjma29/proliant-mcp/releases).
165
+ - **Which version am I on:** `--check` prints it, plus the latest release and
166
+ `UPDATE AVAILABLE` if you are behind.
167
+ - **Pin a version** (no surprise changes; you upgrade by editing the version):
168
+ `proliant-mcp@0.6.1` in place of `proliant-mcp@latest`.
169
+ - **No access to PyPI** (some corporate networks): every release is also attached to GitHub.
170
+ Use `"args": ["--refresh-package", "proliant-mcp", "--from", "https://github.com/hjma29/proliant-mcp/releases/latest/download/proliant-mcp.tar.gz", "proliant-mcp"]`.
171
+ - **Unreleased changes** from `main`:
172
+ `"args": ["--from", "https://github.com/hjma29/proliant-mcp/archive/refs/heads/main.zip", "proliant-mcp"]`
173
+ (picks up every push on restart; may include unfinished work).
174
+
175
+ To hack on it: `git clone https://github.com/hjma29/proliant-mcp && cd proliant-mcp && uv sync && uv run pytest`.
176
+
177
+ ## Configure
178
+
179
+ Credentials are read from the machine running the server, never from this
180
+ repository, and never sent to the AI model. That machine must reach each iLO
181
+ and OneView appliance over HTTPS (443), and `*.api.greenlake.hpe.com` /
182
+ `sso.common.cloud.hpe.com` for COM. Configure any mix of the three.
183
+
184
+ ### Inventory file
185
+
186
+ **Add servers from the chat** (easiest): ask your assistant to *"add an iLO"* or *"add a OneView"*. It
187
+ calls the `add_server` tool, which shows a pop-up for the type, address, name and user name, then
188
+ opens a secure page on your own computer (`127.0.0.1`) for the password. The password goes straight
189
+ to proliant-mcp, never through the AI client or model. It is **checked against the server before
190
+ anything is saved**, so a wrong password or address is caught at once. The tools use the new server
191
+ immediately, no restart.
192
+
193
+ **Import a list** (many servers): ask your assistant to *"import my servers from a file"*. The
194
+ `import_inventory` tool pops up for the **path** of an `.ini` or `.csv` file (the AI cannot choose the
195
+ file; you type it), shows what it found, and optionally asks once for a password shared by entries
196
+ that have none, then checks each login. The file stays where it is. For a spreadsheet, use **File >
197
+ Save As > CSV** in Excel; the columns are `name, type, host, username, password`
198
+ ([example](https://github.com/hjma29/proliant-mcp/blob/main/examples/inventory.example.csv)), and common variants such as `IP Address` or `Server Name`
199
+ are recognised (`.xlsx` files are not read directly). Same thing in a terminal:
200
+ `proliant-mcp import servers.csv` (`--replace` overwrites entries that already exist, `--no-check` skips the login checks).
201
+
202
+ Both write `~/.config/proliant-mcp/inventory.ini` (or the file `PROLIANT_MCP_CONFIG` names), readable
203
+ only by you, and leave other content in the file as it is. If you only had a proliant-cli inventory,
204
+ its content is copied there first; the proliant-cli file is never changed. Passwords are stored in
205
+ that file in plain text, so delete a CSV you imported once you no longer need it.
206
+
207
+ **Or edit the file by hand.** Copy [examples/inventory.example.ini](https://github.com/hjma29/proliant-mcp/blob/main/examples/inventory.example.ini) to
208
+ `~/.config/proliant-mcp/inventory.ini` (Windows: `%USERPROFILE%\.config\proliant-mcp\inventory.ini`),
209
+ fill it in, and restrict it to your user. Or point `PROLIANT_MCP_CONFIG` at any path.
210
+ The file can be saved by Notepad or PowerShell (UTF-8 or UTF-16).
211
+
212
+ ```ini
213
+ [defaults]
214
+ username = Administrator
215
+ password = changeme
216
+
217
+ ; an iLO (type = ilo is the default)
218
+ [dl380-gen11]
219
+ host = 192.0.2.10
220
+
221
+ ; a OneView appliance / Synergy Composer
222
+ [synergy]
223
+ type = oneview
224
+ host = 192.0.2.100
225
+
226
+ ; a Compute Ops Management workspace
227
+ [greenlake]
228
+ type = com
229
+ client_id = ...
230
+ client_secret = ...
231
+ region = us-west
232
+ ```
233
+
234
+ Keep comments on their own lines; a `#` or `;` after a value becomes part of the value.
235
+
236
+ ```powershell
237
+ # Windows: create, edit, then lock to your user
238
+ New-Item -ItemType Directory -Force "$env:USERPROFILE\.config\proliant-mcp" | Out-Null
239
+ notepad "$env:USERPROFILE\.config\proliant-mcp\inventory.ini"
240
+ icacls "$env:USERPROFILE\.config\proliant-mcp\inventory.ini" /inheritance:r /grant:r "$($env:USERNAME):(R,W)"
241
+ ```
242
+
243
+ ```bash
244
+ # macOS / Linux
245
+ chmod 600 ~/.config/proliant-mcp/inventory.ini
246
+ ```
247
+
248
+ A [proliant-cli](https://github.com/hjma29/proliant-cli) inventory at `~/.config/proliant-cli/inventory.ini` is also read.
249
+
250
+ ### iLO
251
+
252
+ A read-only iLO account (Login privilege only) is enough for every tool. iLO uses a
253
+ self-signed certificate by default, so TLS verification is off unless you set
254
+ `verify_ssl = true`. One iLO can also come from environment variables:
255
+ `ILO_HOST`, `ILO_USERNAME`, `ILO_PASSWORD` (`ILO_NAME` sets its name, default `default`).
256
+
257
+ ```bash
258
+ export ILO_HOST=192.0.2.10 ILO_USERNAME=Administrator ILO_PASSWORD='...'
259
+ ```
260
+
261
+ ### HPE OneView
262
+
263
+ A OneView user with the read-only role is enough. One appliance can also come from
264
+ environment variables: `ONEVIEW_HOST`, `ONEVIEW_USERNAME`, `ONEVIEW_PASSWORD`
265
+ (`ONEVIEW_NAME`). The REST API version is negotiated automatically.
266
+
267
+ ### HPE Compute Ops Management
268
+
269
+ **Sign in from the chat** (easiest): ask your assistant to *"sign in to HPE GreenLake"*, or just
270
+ ask a COM question; it calls the `com_login` tool, which shows pop-ups in the chat:
271
+
272
+ 1. Your HPE GreenLake email.
273
+ 2. **`@hpe.com` accounts:** the number to tap in **Okta Verify** on your phone.
274
+ **Other accounts (e.g. gmail.com):** a sign-in page opens with a masked password field. The page
275
+ is served by proliant-mcp on your own computer (`127.0.0.1`), so the password goes straight to
276
+ it, never through the AI client or model. If Okta also wants a push, the number pop-up follows.
277
+ 3. Which workspace, if you have several. The COM region is detected.
278
+
279
+ It then creates a temporary GreenLake API client (`GLP-proliant-mcp-<host>-...`) in that workspace
280
+ and saves its ID and secret to `~/.config/proliant-mcp/com/login.json` (readable only by you). The
281
+ `com_*` tools use it straight away, no restart. Your email, password and session are never stored.
282
+ Signing in again replaces this computer's previous client.
283
+
284
+ This needs an AI client that supports MCP pop-ups (elicitation), such as VS Code with GitHub
285
+ Copilot. Otherwise run the same sign-in in a terminal:
286
+
287
+ ```bash
288
+ uvx proliant-mcp@latest login
289
+ ```
290
+
291
+ (`--email`, `--workspace NAME`, `--region us-west|eu-central|ap-northeast`; `proliant-mcp logout`
292
+ forgets the saved login, and you can delete the API client under **Manage Workspace > API**.)
293
+
294
+ The account needs permission to create API clients in the workspace. The sign-in is the same one
295
+ the GreenLake web page uses, which HPE does not publish as an API, so for unattended or shared
296
+ setups, or if HPE changes the sign-in, use an API client instead:
297
+
298
+ **Or use an API client.** In HPE GreenLake open **Manage Workspace > API**, create a personal API
299
+ client for the Compute Ops Management service in your region with a Compute Ops Management role (an
300
+ observer role is enough for these read-only tools), and copy the client ID and secret. Region is
301
+ `us-west`, `eu-central` or `ap-northeast`. Put it in the inventory (`type = com`) or set
302
+ `HPECOM_CLIENT_ID`, `HPECOM_CLIENT_SECRET` and `HPECOM_REGION`.
303
+
304
+ Order of use: inventory / environment variables, then the saved `proliant-mcp login`, then
305
+ proliant-cli's COM login (`proliant com login`), which is reused automatically if you have it.
306
+
307
+ ## Test it
308
+
309
+ ### 1. Unit tests (no hardware)
310
+
311
+ ```bash
312
+ uv run pytest
313
+ ```
314
+
315
+ Runs the tools against a fake iLO, OneView appliance and COM API (`httpx.MockTransport`)
316
+ through a real MCP client. No hardware or GreenLake account needed.
317
+
318
+ ### 2. From the terminal
319
+
320
+ ```bash
321
+ uv run fastmcp list src/proliant_mcp/server.py # tools and schemas
322
+ uv run fastmcp call src/proliant_mcp/server.py list_servers
323
+ uv run fastmcp call src/proliant_mcp/server.py get_ilo_info server=dl380-gen11
324
+ uv run fastmcp call src/proliant_mcp/server.py com_get_overview
325
+ uv run fastmcp call src/proliant_mcp/server.py oneview_list_alerts
326
+ ```
327
+
328
+ ### 3. MCP Inspector (web UI)
329
+
330
+ ```bash
331
+ npx @modelcontextprotocol/inspector uv run --directory "$PWD" proliant-mcp
332
+ ```
333
+
334
+ Open the printed URL, click **Connect**, then **Tools** to call each tool by hand.
335
+
336
+ ### 4. VS Code / GitHub Copilot
337
+
338
+ Open this folder in VS Code. [.vscode/mcp.json](https://github.com/hjma29/proliant-mcp/blob/main/.vscode/mcp.json) registers
339
+ the server as `proliant`; start it from the MCP view (or the code lens in that
340
+ file), switch Copilot Chat to **Agent** mode, and ask:
341
+
342
+ - "Give me a COM fleet health report. Which servers need attention and why?"
343
+ - "Which COM servers are not connected, and when do subscriptions expire?"
344
+ - "Any active OneView alerts? What's the corrective action?"
345
+ - "Show the Synergy frame: power, Composers, interconnect firmware"
346
+ - "Which OneView profiles are not on the newest Synergy Service Pack?"
347
+ - "Any critical IML events on dl380-gen11?"
348
+ - "Which switch port is each NIC on dl345-gen12 connected to?"
349
+
350
+ To use it from any workspace, add the same entry to your user MCP config
351
+ with an absolute path in `--directory`.
352
+
353
+ Claude Desktop / Claude Code / other clients use the same command:
354
+ `uv run --directory /path/to/proliant-mcp proliant-mcp`.
355
+
356
+ ### 5. Over HTTP
357
+
358
+ ```bash
359
+ uv run proliant-mcp --http --host 127.0.0.1 --port 8000 # endpoint: http://127.0.0.1:8000/mcp
360
+ ```
361
+
362
+ The HTTP endpoint has **no authentication**. Keep it on localhost or a
363
+ trusted management network.
364
+
365
+ ## Google ADK
366
+
367
+ [examples/adk_agent/agent.py](https://github.com/hjma29/proliant-mcp/blob/main/examples/adk_agent/agent.py) is a
368
+ [Google ADK](https://google.github.io/adk-docs/) agent that starts this server
369
+ over stdio with `McpToolset`:
370
+
371
+ ```bash
372
+ export GOOGLE_API_KEY=... # or Vertex AI env vars
373
+ uv run --with "google-adk[mcp]" adk web examples # pick "adk_agent"
374
+ ```
375
+
376
+ Set `ADK_MODEL` to choose a different Gemini model. To use the HTTP mode
377
+ instead, swap `StdioConnectionParams` for
378
+ `StreamableHTTPConnectionParams(url="http://127.0.0.1:8000/mcp")`.
379
+
380
+ ## Skills
381
+
382
+ Agent skills that tell an assistant which tool to use for which question, plus workflows:
383
+
384
+ - [skills/proliant-ilo/SKILL.md](https://github.com/hjma29/proliant-mcp/blob/main/skills/proliant-ilo/SKILL.md): one server through its iLO
385
+ (firmware audit, health triage, finding a server's switch port).
386
+ - [skills/hpe-compute-fleet/SKILL.md](https://github.com/hjma29/proliant-mcp/blob/main/skills/hpe-compute-fleet/SKILL.md): fleets through
387
+ Compute Ops Management and OneView (fleet health report, alert triage, firmware
388
+ baseline drift, finding one server across all three sources).
389
+
390
+ Copy them into your agent's skills folder (for example `~/.copilot/skills/` or
391
+ `.github/skills/`).
392
+
393
+ ## Roadmap
394
+
395
+ 1. **Read-only (now):** iLO, Compute Ops Management and OneView inventory, health,
396
+ alerts, jobs and firmware baselines.
397
+ 2. **Actions,** opt-in and annotated destructive: power and UID (iLO, COM, OneView),
398
+ one-time boot, COM firmware update jobs.
399
+ 3. **More reports:** COM server inventory (storage, NICs, PCI), OneView networks and
400
+ uplink sets, COM sustainability / energy reports.
401
+ 4. **Skills** for deploying and managing ProLiant servers (OS deployment,
402
+ firmware updates, BIOS baselines).
403
+
404
+ ## Security
405
+
406
+ - No credentials are stored in this repository; `.gitignore` blocks `*.ini`
407
+ (except the example) and `.env` files.
408
+ - Tools never return passwords or client secrets. `redfish_get` refuses session and
409
+ account resources; `oneview_rest_get` refuses sessions and users; the raw COM and
410
+ OneView GET tools redact keys such as `activationKey` and `password`.
411
+ - Each iLO and OneView tool call opens and closes its own session. COM access tokens
412
+ are cached in memory only, until they expire.
413
+
414
+ ## License
415
+
416
+ [MIT](https://github.com/hjma29/proliant-mcp/blob/main/LICENSE). Not an official HPE product.