v0.2.1

AnnealBridge is now on the MCP Registry
as io.github.TheTsungYing/annealbridge. No optimization behaviour changed.

Added

• annealbridge mcp runs the MCP server, exactly as the annealbridge-mcp
  console script does. Every argument reaches the same parser, --help and
  --version included, and a missing [mcp] extra ends both the same way.
• server.json describes the server for the MCP Registry. A registry
  client resolves it to uvx --from=annealbridge[mcp] annealbridge mcp.

The subcommand exists because the registry composes a package command as
<runtimeHint> <runtimeArguments> <identifier> <packageArguments>, and
identifier has to be the PyPI project name for the registry's ownership
check — so a console script named differently from the project is unreachable.
Both entry points remain supported; a hand-written host configuration is
shorter with annealbridge-mcp.

Installing from the registry

A registry-aware client picks this up on its own. By hand, nothing changes:

uvx --from "annealbridge[mcp]" annealbridge-mcp

Upgrading an existing uvx install still needs uv cache clean annealbridge
and a host restart — it reuses the environment it first resolved.

---

Full changelog: https://github.com/TheTsungYing/AnnealBridge/blob/main/CHANGELOG.md#021---2026-09-16 · Compare: v0.2.0...v0.2.1