What is mcp-releasing?

A procedure for releasing Model Context Protocol servers, which let AI applications connect to external tools, as NPM packages.

Use it to prepare and verify an MCP server release, including TypeScript output and native-code checks when the project has them.

It checks package metadata, versions, dependencies, tests, builds, security, and release notes before publishing.

mcp-releasing — Cursor rule for Cursor by roy2392

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/roy2392/vibe-agents-rules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/mcp-releasing/github.svg)](https://agentmods.dev/rules/roy2392/vibe-agents-rules/mcp-releasing)

Your own site

<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/mcp-releasing"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/mcp-releasing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/mcp-releasing"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/mcp-releasing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,231 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01231
Opus 5	$0.00000	$0.00616
Sonnet 5	$0.00000	$0.00246
Haiku 4.5	$0.00000	$0.00123

Measured 9d ago against content hash ecd1ba4be2ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

mcp-releasing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to mcp-releasing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

docs/mcp-releasing.mdc · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releasing MCP Servers

This document outlines the steps to release a new version of an MCP (Model Context Protocol) server as an NPM package.

Automated Release Preparation

Many MCP projects include an automated release preparation script that performs comprehensive checks before release. Run it with:

npm run prepare-release

This script typically performs the following checks:

Git Status: Ensures you're on the main branch with no uncommitted changes
Required Fields: Validates all required fields in package.json
Dependencies: Checks for missing or outdated dependencies
Security Audit: Runs npm audit to check for vulnerabilities
Version Availability: Confirms the version isn't already published
Version Consistency: Ensures package.json and package-lock.json versions match
Changelog Entry: Verifies CHANGELOG.md has an entry for the current version
TypeScript: Compiles and runs tests
TypeScript Declarations: Verifies .d.ts files are generated
Native Code (if applicable): Runs format, lint, and tests for Swift/other languages
Build Verification: Builds everything and verifies the package
Package Size: Warns if package exceeds reasonable size limits
MCP Server Smoke Test: Tests the server with a simple JSON-RPC request

If all checks pass, follow the manual steps below.

Manual Pre-Release Steps

Update Version Number:
- Decide on the new semantic version number (e.g., 1.0.0-beta.3, 1.0.0, 1.1.0).
- Update the version field in package.json.
Update Documentation:
- README.md: Ensure it accurately reflects the latest features, installation instructions, and any breaking changes.
- API Documentation: If there are changes to tool schemas or server behavior, update the detailed specification.
- Any other relevant documentation.
Update CHANGELOG.md:
- Add a new section for the upcoming release version (e.g., ## [1.0.0-beta.3] - YYYY-MM-DD).
- List all notable changes (Added, Changed, Fixed, Removed, Deprecated, Security) under this version.
- Replace YYYY-MM-DD with the current date.

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 103 lines · 0 tokens per session scan A ecd1ba4be2ae

Subscribe to this mod's changes

mcp-releasing is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (11 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,231 tokens. A static security scan graded it A with 0 findings. It is 100% identical to mcp-releasing, differing in 0 lines, and is treated as a copy.

Git and workflow Releases

monorepo-versioning

Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.

solvapay/solvapay-sdk · 0 tokens

release-notes

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

thatrebeccarae/claude-marketing · 50 tokens

mcp-releasing