Skip to content

Updating

b123d-print --version (or the version field of the MCP list_parts tool) shows what you run. Releases: PyPI and GitHub releases (what changed).

Installed with Update
uvx --from b123d-print ... (MCP clients) uvx caches the package: run uvx --refresh --from b123d-print b123d-print-mcp --help once, then restart the client
a pinned version --from b123d-print==0.2.0 change the version in your client config, restart the client
uvx --from git+https://github.com/KD5RYN/b123d-print ... (unreleased) uvx --refresh --from git+https://github.com/KD5RYN/b123d-print b123d-print-mcp --help, then restart the client
uv tool install b123d-print (CLI) uv tool upgrade b123d-print
Docker image ghcr.io/kd5ryn/b123d-print-mcp docker pull ghcr.io/kd5ryn/b123d-print-mcp, restart the client
Docker image built from a clone git pull && docker build -t b123d-print-mcp . in your clone, restart the client
HTTP server with Compose see below
Claude Code plugin /plugin marketplace update b123d-print, then restart Claude Code

A Compose install

For the HTTP server with Compose. The parts, the tokens and your .env stay as they are; clients reconnect on their own (the server is stateless).

With the GHCR image, in the folder that holds compose.yaml:

docker compose pull && docker compose up -d

Built from a clone, in the clone:

git pull && docker build -t b123d-print-mcp . && cd deploy && docker compose up -d

After updating

  • Workspaces keep your parts and settings. The workflow text in a workspace's AGENTS.md is a copy; refresh it with b123d-print init --update-agents (MCP clients always get the current text from the server).
  • Printer profiles ship with the package and update with it; your own files in ~/.config/b123d-print/ are never touched.
  • Part scripts: while b123d-print is 0.x the script conventions may change; the release notes say when, and b123d-print check tells you what breaks.