skills.rest
IdanDavidAviv
IdanDavidAvivCOMMUNITY
Explore all skills by this author →
GitHub

mcp_publisher

Package and publish the Virgo MCP server to npm.

2|Updated Mar 26, 2026
Search Tags:#automation#ci/cd#npm#mcp#publish#nodejs
One-click install
npx skills add https://github.com/IdanDavidAviv/virgo --skill mcp-publisher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp_publisher
Source: https://github.com/IdanDavidAviv/virgo/tree/main/.agent/skills/mcp_publisher
Command: npx skills add https://github.com/IdanDavidAviv/virgo --skill mcp-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The MCP Publisher provides a safe, repeatable pathway to package and publish Virgo's standalone MCP server to the public NPM registry, enabling universal execution via npx and avoiding fragile local paths.

Core Features & Use Cases

  • Package extraction and isolation: assemble the stand-alone MCP server into a minimal npm package with a deterministic artifact.
  • Headless publishing support: read a NPM automation token from .env to allow CI/CD workflows to publish without interactive prompts.
  • Release gate alignment: enforce that MCP publishing occurs after the VSIX release and version parity to ensure artifact consistency.

Quick Start

Build the extension, then run the publish script to publish virgo-mcp to npm.

Frequently Asked Questions about mcp_publisher

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

FAQPage Schema
How do I publish an MCP server to npm using automated CI/CD workflows?▼

Headless npm publishing requires an automation token stored in your .env file. This skill reads the token to publish the MCP server package automatically in CI/CD workflows without interactive login prompts, ensuring safe and repeatable deployments.

What is the safest way to package a standalone Node.js server for global npm execution?▼

Safely packaging a Node.js server for npm requires isolating it into a minimal package with a deterministic artifact and a hashbang-safe entry point. This approach prevents fragile local paths and enables universal execution via npx.

Do I need to publish a VSIX release before publishing my MCP server to npm?▼

Yes, you must publish the VSIX release first. This skill enforces a release gate that requires the VSIX release and version parity before publishing the MCP server to npm, ensuring artifact consistency across environments.

Why should I isolate my MCP server into a lightweight npm package?▼

Isolating an MCP server into a lightweight npm package avoids fragile local paths and enables universal global execution via npx. This skill assembles the stand-alone server into a minimal package with a deterministic artifact for consistent deployment.

What safety gates are enforced during npm package publishing?▼

Safety gates enforced during npm publishing include release sequencing and version parity checks against the VSIX release. These gates prevent unauthorized or unsafe publishing actions, ensuring the MCP server package is deployed securely and consistently.

Related Skills

Explore More Software Engineering Skills→
AEtherlight-aiAEtherlight-ai

publish

Automate ÆtherLight release publishing to npm and GitHub.

Official
Intermediate
DavidLam-ossDavidLam-oss
283

project-release

Automate versioning, validation, and deployment for Obsidian plugins.

Community
Advanced
andymaiandymai
20

release-flow

Coordinate software package releases to the npm registry and web interfaces.

Community
Advanced
nerinanarinenerinanarine

build-mcpb

Package a local MCP server and its runtime into a standalone .mcpb file.

Community
Intermediate