agentmods.dev

mcp-releasing

mcp-releasing is a cursor rule for coding agents from steipete/agent-rules. It costs 0 tokens per session (1,231 once invoked), scanned A, original, MIT.

A release checklist for publishing Model Context Protocol (MCP) servers as npm packages. MCP servers provide tools that AI applications can call.

In plain words
What is it for?
Use it when preparing an MCP server release, checking package metadata, running audits and tests, verifying generated TypeScript declarations, and confirming the build.
Why use it?
It catches version, dependency, security, build, test, documentation, and package problems before a release is published.

Cursor rule

not rated 5.7k +1 4mo ago A scan 0 tokens original MIT archived
View the source file steipete/agent-rules
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.

agentmods
npx agentmods add rules/steipete/agent-rules/mcp-releasing
Clone the repo
git clone --depth 1 https://github.com/steipete/agent-rules

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.

agentmods badge for mcp-releasing

README.md
[![agentmods](https://agentmods.dev/badge/rules/steipete/agent-rules/mcp-releasing.svg)](https://agentmods.dev/rules/steipete/agent-rules/mcp-releasing)
Your own site
<a href="https://agentmods.dev/rules/steipete/agent-rules/mcp-releasing"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/mcp-releasing.svg" alt="Measured on agentmods" 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. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01231
Opus 5 $0.00000 $0.00616
Sonnet 5 $0.00000 $0.00246
Haiku 4.5 $0.00000 $0.00123

Measured 4d ago against content hash ecd1ba4be2ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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

Copies of this mod

1 near-identical copy found in the catalogue:

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

  1. 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.

  2. 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.

  3. 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.

  1. 4d 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 steipete/agent-rules (5,694 stars, last pushed 4mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agentsGit and workflowReleasesagentclaudecodecursorllmsrules
Related

Other cursor rules, from other repositories

zip-contents-protection.crux

⟦CRUX:zip-contents-protection.md P.⊛{¬auto-Δ scripts/create-crux-zip.py w/o user req!}.

zotoio/CRUX-Compress · 495 tokens

version-bump.crux

⟦CRUX:version-bump.md Κ{M=X.0.0;m=0.X.0;p=0.0.X} R{fix|docs|style|refactor|perf|test|chore→p;feat→m;BREAKING|!→M} Λ{⊲commit→Δ.crux/crux.json»stage} P{1bump;↑→↓0;¬conv→?} ⟧.

zotoio/CRUX-Compress · 190 tokens

changelog-generator-manual

This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.

usrrname/cursorrules · 0 tokens

release-commit-analysis-auto

This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…

usrrname/cursorrules · 0 tokens

release-git-tags-auto

This rule checks for existing tags before creating new ones. It also offers to push the tag to the remote repository. It runs when users request release creation, version bumping, or package publishing.

usrrname/cursorrules · 0 tokens

release-validation-auto

This rule validates release prerequisites including branch naming conventions and package.json structure. It runs when users request release creation, version bumping, or package publishing. The rule ensures releases only occur from appropriate branches (release/, hotfix/, fix/) and validates package.json exists with…

usrrname/cursorrules · 0 tokens