What problem does it solve?
Releasing the @dain-os/mcp-server package requires two separate, easy-to-forget steps: publishing the new version to npm and deploying the updated code to the Vercel cloud endpoint. Forgetting either step leaves users with stale tools or an unavailable cloud MCP surface, causing disruption for teams relying on the service.
Core Features & Use Cases
- End-to-end release workflow: Automates the full 7-step process for publishing the MCP server, from version verification to post-deployment checks.
- Secure credential handling: Pulls the npm publish token from Azure Key Vault without exposing it in logs, shell history, or temporary files left in the repository.
- Dual deployment validation: Ensures both the npm package and the Vercel cloud endpoint (mcp.dainos.app) are updated and verified after every release.
- Use Case: When a release PR for the MCP server is merged to main, use this skill to push the new version to npm and update the cloud endpoint without missing steps or exposing sensitive credentials.
Quick Start
Use the publish-mcp-server skill to release the new version of the @dain-os/mcp-server package after the corresponding release PR has been merged to the main branch.