Dell PowerStore

This MCP server brings Model Context Protocol capabilities to Dell PowerStore, allowing read-only access via generated tools while keeping credentials per-request. You can interact with multiple PowerStore instances securely and integrate with AI agents or automation platforms without storing credentials.

How to use

You interact with the Dell PowerStore MCP Server through an MCP client. The server dynamically exposes a large library of tools derived from the PowerStore OpenAPI specifications. Each tool requires per-call authentication, with host, username, and password provided by your client. Use a client that supports the MCP transport you prefer, such as HTTP/SSE for web-based workflows (e.g., n8n) or stdio for desktop AI agents like Claude.

How to install

Prerequisites: Python 3.10 or newer and a PowerStore array to query. You will install the MCP server, then run either the HTTP/SSE transport for remote clients or the stdio transport for local desktop clients.

# Install from PyPI (recommended)
pip install dell-powerstore-mcp-server

# Or install from source and run in development mode
# (Clone, install in editable mode, then run)
git clone https://github.com/sachdev27/dell-powerstore-mcp-server.git
cd dell-powerstore-mcp-server
pip install -e .

Run the HTTP/SSE server for n8n and web clients:

powerstore-mcp-http

Run the stdio server for Claude Desktop or local tooling:

powerstore-mcp

If you prefer a containerized setup, pull and run the image:

docker pull ghcr.io/sachdev27/dell-powerstore-mcp-server:latest

docker run -p 3000:3000 ghcr.io/sachdev27/dell-powerstore-mcp-server:latest

Configuration and environment

Set per-call authentication by passing host, username, and password with each tool invocation. Credentials are never stored on the server; every request authenticates at call time.

# Example environment file for the HTTP/SSE server
LOG_LEVEL=info
LOG_FORMAT=json
OPENAPI_SPEC_PATH=./openapi.json
HTTP_PORT=3000
HTTP_HOST=0.0.0.0

Security and data access

The server operates in a credential-free design, meaning no PowerStore credentials are stored. Each request must provide host, username, and password, ensuring per-call authentication and reducing risk from long-lived credentials.

Health and monitoring

Built-in health checks and metrics endpoints help you monitor the MCP server's status and performance. Use the health and metrics endpoints to verify availability during deployment and ongoing operations.

Networking and multi-host support

The server supports multiple PowerStore instances from a single MCP instance. Each tool call targets a specific host with its own credentials, enabling centralized management of several arrays from one place.

Troubleshooting

If you encounter connection issues, verify that: 1) the target PowerStore hostname/IP is reachable, 2) the provided credentials are correct for that host, and 3) the server is listening on the expected port (default 3000 for HTTP/SSE). Check the logs for authentication or network failures and adjust your client configuration accordingly.

Notes

The server automatically generates a large set of tools based on the PowerStore OpenAPI specifications. You do not need to manually define each tool; they are discovered and exposed at runtime.

Available tools

getVolume

Retrieve information about a PowerStore volume

getHost

Retrieve information about a PowerStore host

getVolume_group

Retrieve information about a PowerStore volume group

getAppliance

Retrieve appliance details from PowerStore

getCluster

Retrieve cluster information from PowerStore

getNode

Retrieve node information from PowerStore

getNetwork

Retrieve network configuration from PowerStore

getIp_port

Retrieve IP/port configurations from PowerStore

getFc_port

Retrieve Fibre Channel port configurations from PowerStore

getNas_server

Retrieve NAS server configurations from PowerStore

getFile_system

Retrieve file system information from PowerStore

getNfs_export

Retrieve NFS export configurations from PowerStore

getSnapshot_rule

Retrieve snapshot rule configurations from PowerStore

getReplication_rule

Retrieve replication rule configurations from PowerStore

getAlert

Retrieve alert information from PowerStore

getEvent

Retrieve event information from PowerStore

getPerformance_rule

Retrieve performance rule configurations from PowerStore