Connecting Claude - visubramaniam/vsp360-mcp GitHub Wiki

The server talks MCP over standard input and output. The client starts it as a command and passes the settings as environment variables.

In the examples, vsp360-mcp is the command from the npm install. For other installs, use:

Install	Command
npm	`vsp360-mcp`, or its full path from `which vsp360-mcp`
`npx`	`npx` with arguments `-y [email protected]`
Claude Code plugin	nothing to configure: the plugin starts the server itself
Standalone, macOS/Linux	`/opt/vsp360-mcp-<version>-<platform>/bin/vsp360-mcp`
Standalone, Windows	`...\runtime\node.exe` with argument `...\dist\index.js`
Container	`docker` with `run -i --rm ...`; see README.docker.md

Claude Code

The simplest way is the Claude Code plugin: /plugin install vsp360-community --marketplace visubramaniam/vsp360-mcp, which also adds the capacity-report and health-check skills. To add the server on its own instead:

claude mcp add vsp360 -e VSP360_URL=https://vsp360.example.com -e VSP360_CLIENT_ID=my-service-account -e VSP360_CLIENT_SECRET=REPLACE_ME -e "VSP360_TOOLSETS=Device Registry,Platform Alerts" -- vsp360-mcp

Run claude mcp list to check that vsp360 shows as connected.

Claude Desktop

The easiest way is the .mcpb extension. To configure it by hand, edit:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "vsp360": {
      "command": "/usr/local/bin/vsp360-mcp",
      "env": {
        "VSP360_URL": "https://vsp360.example.com",
        "VSP360_CLIENT_ID": "my-service-account",
        "VSP360_CLIENT_SECRET": "REPLACE_ME",
        "VSP360_TOOLSETS": "Device Registry,Platform Alerts"
      }
    }
  }
}

Claude Desktop doesn't read your shell's PATH, so use full paths. Quit Claude Desktop fully and reopen it after editing.

Other MCP clients

Configure the client to start the server command with the environment variables. Any client that supports stdio MCP servers works.

In a CI/CD pipeline

Install a pinned version, pass the credentials from the CI secret store, and point the agent at an MCP config that names only the variables:

- run: npm install -g "[email protected]"
- run: |
    cat > vsp360.mcp.json <<'EOF'
    { "mcpServers": { "vsp360": { "command": "vsp360-mcp" } } }
    EOF
- env:
    VSP360_URL: ${{ vars.VSP360_URL }}
    VSP360_CLIENT_ID: ${{ secrets.VSP360_CLIENT_ID }}
    VSP360_CLIENT_SECRET: ${{ secrets.VSP360_CLIENT_SECRET }}
  run: ...  # e.g. claude -p "..." --mcp-config vsp360.mcp.json

Keep automated jobs read-only, which is the default, and give their service account only the access the job needs.

Check that it works

Ask "List the VSP 360 API areas". This needs no VSP 360 access, so it confirms the server started.
Ask "Show current VSP 360 platform alerts". This confirms sign-in, TLS and network access.

If either fails, see Troubleshooting.