publish-mcp-server

Automate npm publishing and Vercel deployment for @dain-os/mcp-server.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/dain-agency/mood-tracker --skill publish-mcp-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-mcp-server
Source: https://github.com/dain-agency/mood-tracker/tree/main/.claude/skills/publish-mcp-server
Command: npx skills add https://github.com/dain-agency/mood-tracker --skill publish-mcp-server

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about publish-mcp-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate npm package publishing and Vercel deployment for an MCP server release?

Automating an MCP server release requires coordinating npm package publishing and Vercel deployment simultaneously. This workflow executes the end-to-end 7-step process, from version verification to post-deployment checks, ensuring both surfaces update without missing steps.

Why does my MCP server cloud endpoint show a stale version after publishing to npm?

A stale MCP server cloud endpoint happens when npm publishing and Vercel deployment are done separately. This workflow solves version drift by automating dual deployment validation, verifying both the npm package and Vercel endpoint versions match.

How do I securely use an npm publish token from Azure Key Vault in a release workflow?

Securely using an npm publish token from Azure Key Vault requires pulling the credential without exposing it in logs, shell history, or temporary files. This workflow manages secure token retrieval internally to protect sensitive credentials.

When should I trigger an automated MCP server release workflow after merging to main?

You should trigger an automated MCP server release workflow immediately after a release PR is merged to the main branch. This ensures the new version is pushed to npm and the Vercel cloud endpoint is updated without delay.

Does this release workflow support targeting specific Vercel team projects for MCP endpoint deployment?

Yes, this release workflow supports correct Vercel team project targeting for MCP endpoint deployment. It ensures the deployment routes to the proper Vercel team project and verifies the post-deployment endpoint version.