vsp360-mcp
Related Servers
Alternatives to vsp360-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables Claude and other MCP clients to discover and call 425 Hitachi VSP One Block REST API operations for storage management, with read-only safety by default, session handling, asynchronous jobs, downloads/uploads, and configurable direct tools.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables testing and interacting with any REST API endpoints directly from MCP clients such as Claude and Cline, with support for multiple HTTP methods, authentication, custom headers, and response-size management.5 npmISC
- AlicenseAqualityDmaintenanceMCP server for the Wasabi WACM Connect API, enabling management of account hierarchy, storage, and billing data through Claude with 18 read-only and 12 opt-in write tools.181Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop and other MCP clients to interact with any OAuth2-authenticated OpenAPI-based API through automatic tool generation from OpenAPI specifications, with built-in token management and authentication handling.4 npm3MIT
- AlicenseAqualityBmaintenanceEnables Claude to work directly with VCF Operations Orchestrator 9.x — searching, describing, and invoking any REST API operation, plus running workflows, actions, and ad-hoc scripts, with automatic conversion between plain JSON and Orchestrator types. Works embedded in VCF Automation or standalone, across multiple authentication modes.1764 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables testing and interacting with any REST API endpoints from Claude, Cline, and other MCP clients, with support for multiple HTTP methods, authentication, custom headers, SSL verification, and response size limits.5 npmISC
TDQS
Scored across 3 tools
The three tools form a clean discover-describe-invoke pipeline with no functional overlap: list returns operationIds, describe returns schemas, call executes. Descriptions explicitly state the intended ordering, so an agent can never mistake one for another.
All names use the identical vsp360_ prefix followed by a consistent verb_noun pattern (list_operations, describe_operation, call_operation). The singular/plural distinction on 'operation(s)' is meaningful rather than sloppy.
Three tools is exactly right for a generic API gateway: the full VSP 360 surface is reached dynamically through operationId rather than one tool per endpoint. Every tool earns its place with no filler.
Discovery, introspection, pagination handling, binary download handling, and automatic auth cover the read lifecycle thoroughly. The deliberate read-only restriction blocks all write operations, which is a real capability gap for the domain even though it is an intentional safety design.