mcp-server-shippinglisted

# Shipping a personal MCP server Workflow for repos whose entire purpose is producing an MCP server for personal, cross-project use, rather than a library other code imports. Covers going from a working repo to "loadable in any project," and how that differs between the dev machine and everywhere else. The worked examples name the author's own servers — a family of `*-polite-mcp` repos — because a concrete name reads better than a placeholder; substitute your own everywhere. Shipping an **Agent Skill** is a different job with a different mechanism — see the `skill-authoring` skill, which also covers getting an edit to an existing skill deployed. ## What this skill reads, runs and writes This skill ships no scripts; what it touches, it touches through the commands it tells you to run. - **Runs**: `uv tool install`, `claude mcp add`, `claude mcp list`. - **Writes**: `uv tool install` puts a tool environment under uv's tool directory and a shim on `PATH` (`~/.local/bin/` by default); `claude mcp add --scope user` writes the server registration into Claude Code's user-level config, `--scope project` into the repo's `.mcp.json`. Both are reversible with the same tools' `uninstall`/`remove`. Nothing else, and nothing in the repo the server lives in beyond the `[project.scripts]` entry you add by hand. - **Network**: `uv tool install git+…` clones the repo you name. ## Per-repo dev loop **Two things here are general and one is the author's own stack.** The general one