Skip to main content

proliant-mcp

Ask your AI assistant about your HPE servers. proliant-mcp is an MCP server that gives AI assistants (GitHub Copilot, Claude, Codex, opencode, ...) read-only access to HPE iLO, HPE Compute Ops Management (GreenLake) and HPE OneView.

Ask things like "which servers in Compute Ops Management are critical and why", "show a table of each server's storage controller and GPU" or "any active OneView alerts on the Synergy frame".

Install

Option 1: ask your AI agent

Paste this into your AI agent (GitHub Copilot, Claude, Codex, opencode, ...):

Install the proliant-mcp MCP server for me. Follow the instructions at https://raw.githubusercontent.com/hjma29/proliant-mcp/main/AGENTS.md (install uv first if it is missing), then tell me when to restart you.

Option 2: manual

Step 1. Install uv (no admin rights, no git needed).

Windows (PowerShell):

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

macOS:

curl -LsSf https://astral.sh/uv/install.sh | sh

Step 2. Add this to your AI client's MCP configuration and restart the client (VS Code Copilot: MCP: Open User Configuration; Claude Desktop: Settings > Developer > Edit Config, with mcpServers in place of servers):

{"servers": {"proliant": {"type": "stdio", "command": "uvx", "args": ["proliant-mcp@latest"]}}}

If the client cannot find uvx, put its full path in command: C:\Users\<you>\.local\bin\uvx.exe on Windows, /Users/<you>/.local/bin/uvx on macOS.

Connect your servers

Just ask your assistant, and it guides you in the chat:

  • "Sign in to HPE GreenLake" for Compute Ops Management. If your chat cannot show pop-ups, it gives you a link to a page on your own computer to type your email.
  • "Add my iLO" or "add my OneView", or "import my servers from a file" (.ini or .csv).

Passwords are typed on a page on your own computer, never in the chat.

Update

proliant-mcp@latest picks up new releases whenever your AI client restarts the server. To stay on one version, use proliant-mcp@X.Y.Z. To check what you run: uvx proliant-mcp@latest --check --connect.

More

Tools | Configuration (inventory file, environment variables, API client) | Advanced (pinning, testing, skills, security) | Changelog

Read-only. Credentials stay on your computer and are never sent to the AI model. MIT licensed; not an official HPE product.

Metadata

Release files for proliant-mcp 0.15.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for proliant-mcp 0.15.2
File Size Uploaded Provenance Actions
proliant_mcp-0.15.2.tar.gz 73.9 kB With provenance Details for proliant_mcp-0.15.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for proliant-mcp 0.15.2
File Interpreter ABI Platform Actions
proliant_mcp-0.15.2-py3-none-any.whl Python 3 none any Details for proliant_mcp-0.15.2-py3-none-any.whl

Total release size: 157.3 kB

Release files / proliant_mcp-0.15.2.tar.gz

Download URL proliant_mcp-0.15.2.tar.gz
Size 73.9 kB
Tags Source
SHA-256 checksum
How to use checksums
dc6ce2c8cb09b6df1847a3165467c7a789e852ba0016ef3f78f3b71c18763ca1
BLAKE2b-256 checksum
How to use checksums
306ff604a3fc4fceb9457e1c0875320077764912839b2b52a33b6b3441b0fa75
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Release files / proliant_mcp-0.15.2-py3-none-any.whl

Download URL proliant_mcp-0.15.2-py3-none-any.whl
Size 83.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e7699bc66dd4bd2193c8a4e5a7658e51d1cbc61c82e4f4c447c1b8755520753b
BLAKE2b-256 checksum
How to use checksums
1fe07dc2f5c6883273ffd0166d3ead81d085f2497d3f14e588462d5c420a4998
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for proliant-mcp 0.15.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for proliant_mcp-0.15.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page