qlinter
publish-pilot-mcp

publish-pilot-mcp

MCP server

From an empty folder to a published package, with you clicking approve.

An MCP server that lets Claude take a project to a GitHub repo and an npm, PyPI or crates.io release. It checks your tools, handles logins, scaffolds the project, runs checks, publishes and releases. You only do the sign-in, 2FA and approval clicks.

  • Node.js 22+
  • npm · PyPI · crates.io
  • MIT
  • macOS

01

What the setup does

Run the downloaded file and follow the wizard.

  1. Checks that Node.js 22 or newer is on your PATH.
  2. Adds publish-pilot to Claude Code for your user (claude mcp add --scope user), if Claude Code is installed.
  3. If you tick it, adds publish-pilot to Claude Desktop’s config, keeping your other servers and saving a .bak copy first.
  4. Uninstalling removes those entries again.

Other ways to install

Claude Code · Windows 
claude mcp add publish-pilot -- cmd /c npx -y publish-pilot-mcp
Claude Code · macOS, Linux, WSL 
claude mcp add publish-pilot -- npx -y publish-pilot-mcp
Check your machine 
npx -y publish-pilot-mcp doctor both npm

On a Mac

  1. Adds publish-pilot to Claude Code for your user if claude is found, and to Claude Desktop if it’s installed, keeping your other servers.
  2. Needs Node.js 22 or newer (Homebrew or nvm both work). What it did is logged in /Library/Application Support/publish-pilot/install.log.
  3. To remove it: sudo bash "/Library/Application Support/publish-pilot/uninstall.sh"

02

What it does

From the project’s README.

Preflight

Checks git, gh, the registry CLI, your logins and git identity. install_tool adds what’s missing with winget, brew or apt.

Free names

check_names checks the package and repo names and picks the best free alternative.

Scaffold + workflows

Source, tests, README, LICENSE, CHANGELOG and CI/release workflows. Never overwrites files.

Checks and secret scan

Lint, typecheck, build and test, plus a secret scan. Commits and publishes are blocked when tokens or .env files would ship.

Trusted publishing

After the first version, every release is a pushed v* tag. GitHub Actions publishes with OIDC, so no tokens are stored.

Install test

verify_install installs from the real registry into a fresh folder and runs your README steps one by one.

03

Requirements

  • Node.js 22 or newer.
  • To publish: git, the GitHub CLI (gh) and your registry’s CLI. doctor shows what’s missing.
  • Claude Code, Claude Desktop, or any MCP client.