Greenlake Workspaces Mcp
Give your agent live HPE GreenLake workspace metadata so you can govern environments and scope changes accurately.
Overview
io.github.HewlettPackard/greenlake-workspaces-mcp is an Operate-phase MCP server that lets your agent call HPE GreenLake workspace APIs via stdio.
What is this MCP server?
- Official GreenLake workspaces MCP from Hewlett Packard on PyPI
- Stdio transport, greenlake-workspaces-mcp version 1.1.2
- Part of the three-server gl-mcp suite alongside users and subscriptions
- Enables agent-guided workspace discovery before infra changes
- Targets hybrid cloud operators, not local IDE workspace folders
- Published version 1.1.2, PyPI identifier greenlake-workspaces-mcp
- MCP schema 2025-12-11, transport type stdio
- Hosted in github.com/HewlettPackard/gl-mcp with two sibling GreenLake MCP packages
Community signal: 8 GitHub stars.
What problem does it solve?
Without MCP, mapping GreenLake workspaces means repetitive console navigation while your agent could be drafting infra changes blind.
Who is it for?
GreenLake operators who coordinate deployments or incidents across multiple cloud workspaces from an MCP client.
Skip if: Developers who only need local project folders, or stacks that do not run on HPE GreenLake.
What do I get? / Deliverables
Workspace structure is visible in the agent thread so infra edits and runbooks reference the correct GreenLake boundaries.
- In-session GreenLake workspace queries through MCP tools
- Version-pinned stdio server config for 1.1.2
- Cross-reference capability with users and subscriptions gl-mcp servers
Recommended MCP Servers
Journey fit
Workspaces partition production and shared services on GreenLake; managing them belongs to the operate phase once systems are live. Infra shelf fits because workspaces are the structural unit for resources, policies, and deployment boundaries on the platform.
How it compares
Enterprise workspace API connector, not a dev-environment or Terraform plan skill.
Common Questions / FAQ
Who is greenlake-workspaces-mcp for?
It is for people administering HPE GreenLake who want workspace API access from Claude Code, Cursor, Codex, or other stdio MCP hosts.
When should I use greenlake-workspaces-mcp?
Use it when operating infra—before migrations, during incident scoping, or when correlating subscriptions and users to specific GreenLake workspaces.
How do I add greenlake-workspaces-mcp to my agent?
Install greenlake-workspaces-mcp 1.1.2 from PyPI, register it as a stdio MCP server, and configure GreenLake API auth per the gl-mcp GitHub project.