AgentHubAgentHub

Hitachi VSP 360 (Community) MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.visubramaniam/vsp360-mcp · v0.1.26

Community MCP server for the Hitachi VSP 360 REST API: alerts, inventory, capacity and performance.

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Community MCP server for the Hitachi VSP 360 REST API: alerts, inventory, capacity and performance. Hitachi VSP 360 (Community) is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHubCursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-18
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Required
Required
Requiredsecret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Setup tutorial

  1. Open the Hitachi VSP 360 (Community) page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add vsp360-mcp --env VSP360_URL=<VSP360_URL> --env VSP360_CLIENT_ID=<VSP360_CLIENT_ID> --env VSP360_CLIENT_SECRET=<VSP360_CLIENT_SECRET> -- npx -y vsp360-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-mcp"
      ],
      "env": {
        "VSP360_URL": "<VSP360_URL>",
        "VSP360_CLIENT_ID": "<VSP360_CLIENT_ID>",
        "VSP360_CLIENT_SECRET": "<VSP360_CLIENT_SECRET>"
      }
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for Hitachi VSP 360 (Community)

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for Hitachi VSP 360 (Community)?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

Hitachi VSP 360 (Community) requires environment variables (VSP360_URL、VSP360_CLIENT_ID、VSP360_CLIENT_SECRET). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "VSP360_URL": "your_actual_key_here"
  }
}
Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

Hitachi VSP 360 (Community) Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: vsp360_mcpExecute the core tool interface of Hitachi VSP 360 (Community)
Request ArgumentsJSON Schema
{
  "target": "Hitachi VSP 360 (Community)",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

Hitachi VSP 360 (Community) + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

中文公文写作

v2.0.35

SkillClawHub9.7k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理，适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论，以及采购、整改、反馈和 AI 算力等场景。

source
View on ClawHub

ai-insurance-advisor

v2.0.163

SkillClawHub8.7k

io.clawhub.mnetfairy/ai-insurance-advisor

中国大陆保险顾问。本 skill 仅覆盖 6 项实际实现的能力：保险需求分析（needs_analyzer.py）、产品对比（premium_calculator.py + 本地 products.json）、保费计算（premium_calculator.py）、方案设计（plan_designer.py）、保险知识问答（insurance-knowledge.md）、合规要点提示（compliance.md）。不提供核保预审、理赔代办、朋友圈/营销文案生成、培训话术、代理人展业工具等能力——这些场景请转人工或调用专业服务。

source
View on ClawHub

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: Hitachi VSP 360 (Community)
HTML
<a href="https://myagenthub.cn/p/io.github.visubramaniam/vsp360-mcp" title="Listed on AgentHub: Hitachi VSP 360 (Community)" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.visubramaniam/vsp360-mcp?lang=en" alt="Listed on AgentHub: Hitachi VSP 360 (Community)" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: Hitachi VSP 360 (Community)](https://myagenthub.cn/badge/io.github.visubramaniam/vsp360-mcp?lang=en)](https://myagenthub.cn/p/io.github.visubramaniam/vsp360-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.visubramaniam/vsp360-mcp",
  "type": "mcp-server",
  "version": "0.1.26",
  "displayName": "Hitachi VSP 360 (Community)",
  "description": "Community MCP server for the Hitachi VSP 360 REST API: alerts, inventory, capacity and performance.",
  "repository": {
    "url": "https://github.com/visubramaniam/vsp360-mcp",
    "source": "github"
  },
  "homepage": "https://visubramaniam.github.io/vsp360-mcp/",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "vsp360-mcp",
        "version": "0.1.26",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "VSP360_URL",
            "description": "Base URL of your VSP 360, e.g. https://vsp360.example.com",
            "isRequired": true
          },
          {
            "name": "VSP360_CLIENT_ID",
            "description": "Client ID of the VSP 360 service account",
            "isRequired": true
          },
          {
            "name": "VSP360_CLIENT_SECRET",
            "description": "Client secret of the VSP 360 service account",
            "isRequired": true,
            "isSecret": true
          },
          {
            "name": "VSP360_TOOLSETS",
            "description": "Comma-separated API areas to expose as direct tools, e.g. Device Registry,Platform Alerts"
          },
          {
            "name": "VSP360_ALLOW_WRITES",
            "description": "Allow operations that change VSP 360. Leave false for read-only access."
          },
          {
            "name": "VSP360_CA_CERT",
            "description": "PEM file of the CA that signed the VSP 360 certificate"
          },
          {
            "name": "VSP360_INSECURE_TLS",
            "description": "Skip TLS certificate verification. For lab systems with self-signed certificates only."
          },
          {
            "name": "VSP360_DOWNLOAD_DIR",
            "description": "Folder for downloaded files; defaults to ~/Downloads/vsp360-mcp"
          },
          {
            "name": "VSP360_UPLOAD_DIR",
            "description": "The only folder files may be uploaded from; read-only mode refuses uploads unless set"
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.visubramaniam/vsp360-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.visubramaniam%2Fvsp360-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}