Community MCP server that lets an assistant browse and call the Hitachi VSP 360 REST API for alerts, inventory, capacity and performance.
What you can do
Browse the VSP 360 REST API by area and search operations by tag or query
Inspect one operation's method, path, permissions, parameters and request/response schemas
Call any operation by operationId with path, query and header parameters and a JSON body
Follow paginated collections across pages, up to 100 records per page
When to use it
Useful when you administer Hitachi VSP 360 storage and want an assistant to look up alerts, inventory, capacity or performance data, or to run API operations without hand-writing REST calls.
Requirements
Runs locally over stdio from the npm package vsp360-mcp. Needs the base URL of your VSP 360 instance and a service account client ID and client secret, plus network access to that instance. Optional settings cover CA certificate, toolset selection, download and upload folders, and write access.
Before you install
Requires a service account client secret, which grants API access to your storage system. Write operations are gated by VSP360_ALLOW_WRITES; keep it false for read-only use. VSP360_INSECURE_TLS disables TLS verification and is meant only for lab systems with self-signed certificates. Uploads are restricted to VSP360_UPLOAD_DIR, and downloads go to VSP360_DOWNLOAD_DIR.
Browse the VSP 360 REST API. With no arguments, lists the API areas (tags) and how many operations each has. With `tag` and/or `query`, lists matching operations (operationId, method, path, summary). Use this first to find the operationId you need, then vsp360_describe_operation and vsp360_call_operation. Operations marked [write] are blocked because the server runs read-only.
Parameterstaglimitquery
vsp360_describe_operation
Show everything needed to call one VSP 360 operation: method and path, required permissions and prerequisites, parameters, request body schema and response schema.
ParametersoperationIdrequiredresourceType
vsp360_call_operation
Call any VSP 360 REST API operation by operationId. Authentication is handled automatically. Pass path, query and header parameters by name in `params`, and the JSON request body in `body`. Collections are paginated with limit/offset (max 100 per page); set all_pages to follow the `next` link. Binary responses (ZIP, gzip, CSV downloads) are saved to the download folder and the file path is returned. Only read operations are allowed; the server runs read-only.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 days25 pts
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.