Repository navigation
FAQ
It's built from the VSP 360 1.4 Platform OpenAPI spec. For a newer release, point VSP360_SPEC at that release's OpenAPI file; nothing needs rebuilding. See How It Works.
No. Any MCP client that supports stdio servers works. The search advice and tool descriptions are written for AI assistants in general.
Not by default. It's read-only until you set VSP360_ALLOW_WRITES=true. See Safety and Security.
264 tools would add about 400 KB of schemas to every conversation, crowding out the actual work. Three discovery tools reach everything; add direct tools only for the areas you use most, with VSP360_TOOLSETS.
Only to the MCP client you connect: tool results become part of the conversation, which your AI provider processes as usual. The server itself talks only to your VSP 360. The optional decision log stays on your machine, and holds search text but no response data or credentials.
To VSP360_DOWNLOAD_DIR, by default ~/Downloads/vsp360-mcp. With Docker, to whatever folder you mount at /downloads.
Set VSP360_CA_CERT to the CA certificate's PEM file. Avoid VSP360_INSECURE_TLS=true outside labs.
Claude Desktop users: the extension. Machines with Node.js, and CI: npm. No Node.js: standalone. Containers or isolation: Docker. See Installation.
npm versions from the Release workflow carry a provenance attestation (npm audit signatures), and every GitHub release has a SHA256SUMS file. Container images on ghcr.io and Docker Hub come from the same build and have the same digest.
npm: npm install -g vsp360-mcp@latest. Extension: open the new .mcpb. Standalone: unpack the new version and repoint your config. Docker: pull the new tag. Then restart your MCP client. Check the changelog for anything that needs action.
vsp360-mcp, a community MCP server for Hitachi VSP 360 (not an official Hitachi Vantara product) · MIT License · The repository's README, INSTALL.md and SECURITY.md are the definitive reference.
Using it
Understanding it
Maintaining it
Links