mcp-release-prep

Update MCP release version numbers across core files and generate a changelog entry.

3.7k|104|Updated Dec 11, 2020
One-click install
npx skills add https://github.com/dathere/qsv --skill mcp-release-prep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-release-prep
Source: https://github.com/dathere/qsv/tree/main/.claude/skills/mcp-release-prep
Command: npx skills add https://github.com/dathere/qsv --skill mcp-release-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare MCP server releases and plugin releases by bumping version numbers across all required files and generating a changelog entry, ensuring version consistency.

Core Features & Use Cases

  • Bump versions across core MCP files: package.json, manifest.json, and .claude-plugin/plugin.json to sync server and plugin releases.
  • Update release metadata across repository metadata (marketplace.json) and agent frontmatters to reflect new versions.
  • Generate a changelog entry documenting MCP releases for release notes.

Quick Start

Use the mcp-release-prep skill with the new MCP server version (and optional minimum_qsv_version) to update all versions and create a changelog entry.

Frequently Asked Questions about mcp-release-prep

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

FAQPage Schema
How do I automate version bumps across multiple MCP configuration files?

Automate MCP version bumps by supplying a new server version string to update package.json, manifest.json, .claude-plugin/plugin.json, and marketplace.json simultaneously, ensuring version consistency across the repository.

How do I generate a changelog entry for an MCP server release?

Generate a changelog entry for MCP releases by applying the new version number to core files and documentation, which automatically produces a changelog entry documenting the release notes for the update.

What files need version updates when releasing an MCP plugin?

MCP plugin releases require version updates in package.json, manifest.json, .claude-plugin/plugin.json, marketplace.json, and YAML frontmatters in agents/data-analyst.md, agents/data-wrangler.md, and agents/policy-analyst.md.

How do I handle conditional version updates when minimum_qsv_version changes?

Conditional version updates trigger when the optional minimum_qsv_version parameter changes, applying core and conditional version bumps across the required MCP files and generating the corresponding changelog entry.

What is the best way to keep MCP server and plugin release versions in sync?

Keep MCP server and plugin versions in sync by automating the release preparation process, which applies the new version string across all core files and metadata to ensure consistency before generating a changelog entry.

Can I update agent frontmatter YAML files during an MCP version bump?

Update agent frontmatter YAML files during an MCP version bump by including the new version string, which automatically modifies agents/data-analyst.md, agents/data-wrangler.md, and agents/policy-analyst.md along with core configuration files.