A release checklist publishes an MCP server—a program that gives an AI assistant access to tools—to PyPI, Python's package registry. It checks the version, updates release notes, builds the package, uploads it, verifies the release, and updates the server metadata.

Use it to release the indiestack MCP server, choose a patch, minor, or major version change, update its changelog, upload the package to PyPI, and commit the related changes.

It reduces the chance of forgetting a release step or publishing the wrong version. It also asks for confirmation before changing the version number.

How Pattyboi101/indiestack configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Pattyboi101/indiestack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Pattyboi101/indiestack/master/.claude/commands/publish-mcp.md

Clone the repo

git clone --depth 1 https://github.com/Pattyboi101/indiestack

Made for: Claude Code.

Or install indiestack, the plugin that ships this one along with the rest of its 4 skills, 6 commands, 1 hook, 1 MCP server.

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/commands/pattyboi101/indiestack/publish-mcp/github.svg)](https://agentmods.dev/commands/pattyboi101/indiestack/publish-mcp)

Your own site

<a href="https://agentmods.dev/commands/pattyboi101/indiestack/publish-mcp"><img src="https://agentmods.dev/badge/commands/pattyboi101/indiestack/publish-mcp/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/commands/pattyboi101/indiestack/publish-mcp"><img src="https://agentmods.dev/badge/commands/pattyboi101/indiestack/publish-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

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

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00522
Opus 5	$0.00000	$0.00261
Sonnet 5	$0.00000	$0.00104
Haiku 4.5	$0.00000	$0.00052

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

Security

Grade A, and why

publish-mcp scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -X POST -H "X-Hub-Secret: $HUB_SECRET" -H "Content-Type: application/json" \

.claude/commands/publish-mcp.md · 78 lines

What it actually says

Publish MCP Server to PyPI

Working directory: ~/indiestack

1. Check current version

cd ~/indiestack && grep 'version = ' pyproject.toml

pip3 index versions indiestack 2>/dev/null || echo "Could not check PyPI"

2. Determine version bump

Review recent changes to src/indiestack/mcp_server.py and related files since last publish. Suggest:

Patch (X.Y.Z+1) for bug fixes
Minor (X.Y+1.0) for new features/tools
Major (X+1.0.0) for breaking changes

Ask the user to confirm the new version.

3. Update version

Edit pyproject.toml to set the new version number.

4. Update changelog

Check if README_PYPI.md needs a changelog entry for the new version. Add one if there are notable changes.

5. Build

cd ~/indiestack && python3 -m build

6. Upload to PyPI

cd ~/indiestack && python3 -m twine upload dist/indiestack-NEW_VERSION*

Replace NEW_VERSION with the version just set. PyPI token is in ~/.pypirc.

7. Verify

pip3 index versions indiestack 2>/dev/null

Confirm the new version appears.

8. Update server.json

Update the version field in server.json to match the new version.

9. Commit and push

cd ~/indiestack && git add pyproject.toml README_PYPI.md server.json && git commit -m "chore: publish MCP server vNEW_VERSION to PyPI" && git push

10. Notify

bash ~/.claude/telegram.sh "IndieStack MCP server vNEW_VERSION published to PyPI"

11. Log to hub (best effort)

Skip if HUB_URL is not set.

curl -s -X POST -H "X-Hub-Secret: $HUB_SECRET" -H "Content-Type: application/json" \
  "$HUB_URL/activity" -d '{"actor":"patrick","action":"published MCP vNEW_VERSION","detail":"uploaded to PyPI"}'

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 · 78 lines · 0 tokens per session scan A 27f3d8b38e3d

Subscribe to this mod's changes

publish-mcp is a command published in the GitHub repository Pattyboi101/indiestack (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Releases

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.

dsswift/ion · 25 tokens

indiestack: Command for Claude Code