0.1.1

Added

• More release packages. Every release now also has a Claude Desktop extension (.mcpb), standalone packages for macOS, Linux and Windows (x64 and arm64) with a Node.js runtime bundled, and a zip of the raidcom-command-builder skill, besides the npm package and the Docker image. SHA256SUMS covers them all. The Windows packages are tested on Windows x64 and arm64 machines. CI builds the Desktop extension, the skill zip and the Linux x64 standalone package on every pull request and smoke-tests them. INSTALL.md has a section for each.
• Claude Code plugin raidcom-community (plugin/, listed by .claude-plugin/marketplace.json; see README.plugin.md). It installs the server from a pinned npm version and adds the raidcom-command-builder skill. It needs no settings. The Plugin release workflow opens a pull request that moves the plugin to each new server release (including the lockfile), and tags plugin-v<version> and creates a GitHub release with the plugin zip when that pull request is merged.
• Security scanning in CI. CodeQL (security-extended queries) runs on every pull request, push to main and weekly. Dependency review fails a pull request that adds a vulnerable dependency. A Security audit workflow runs npm audit on the runtime dependencies and a Trivy scan of the Docker image on pull requests that touch dependencies or the Dockerfile, and weekly.
• Recipe create-mainframe-pool: creates a mainframe parity group (always -emulation 3390-V, not a parameter), assigns an SSID, creates and quick-formats 3390 LDEVs and makes them a DP pool, with HORCC_DRIVEOPERATION=1 exported at the top of the script. Recipes can now export environment variables (env).
• CU:LDEV notation (dd:0f) is accepted for LDEV IDs and range-checked, and ranges such as dd:00-dd:0f expand in recipes and scripts.
• add parity_grp accepts -emulation, which the manual's syntax line leaves out but mainframe-capable systems use. The generator records it as an addition.
• The Release workflow also pushes the image to Docker Hub (subramaniamv/raidcom-mcp) when the DOCKERHUB_USERNAME and DOCKERHUB_TOKEN repository secrets are set; otherwise it pushes to ghcr.io only.
• Build, CI and release pipeline. CI now also builds the npm package and installs it into an empty folder to check it starts over stdio and HTTP (npm run package, npm run smoke). Merging a pull request that bumps version in package.json tags the commit (the Tag release workflow, which requires a matching CHANGELOG.md section) and starts the Release workflow: it re-runs the tests, attaches the package and SHA256SUMS to a GitHub release, publishes to npm with provenance, lists the version in the MCP Registry and pushes a multi-arch image to ghcr.io.

0.1.0

First version.

• Eight read-only MCP tools: raidcom_list_commands, raidcom_describe_command, raidcom_build_command, raidcom_check_command, raidcom_build_script, raidcom_list_recipes, raidcom_build_recipe, raidcom_model_limits.
• A catalogue of 178 commands (218 syntax forms, 562 examples) generated from the Command Reference, with per-model limits for VSP One Block 24/26/28, VSP 5000 series and VSP E series.
• Thirteen recipes: FC, iSCSI and NVMe/TCP provisioning, DP pools, extending and deleting volumes, command devices, zero-page reclaim, inventory, copy groups.
• Stdio and stateless Streamable HTTP transports (bearer token, TLS or proxy, host and origin checks, rate limit).
• Build-only by design: no tool connects to a storage system or runs a command.

raidcom-community plugin 0.1.0

Claude Code plugin for raidcom-mcp 0.1.0. Install: /plugin install raidcom-community --marketplace visubramaniam/raidcom-mcp. See README.plugin.md.