uvx fails on a Python MCP server whose command name differs from its PyPI name The maintainer of aisync, a local CLI for multi-agent context management that ships an MCP server, found that `uvx aisync-cli` fails because uvx looks for an executable matching the PyPI package name while the package installs a command called `aisync`. In version 0.2.11 the maintainer added a console script named after the package and documented a registry `server.json` that uses `--with "mcp>=2.3,<3"` and a positional `mcp` argument so uvx can start the server, with `mcp-publisher validate` confirming the file is valid. aisync is a local CLI for Multi-Agent Context Management, Coordination & Observability across AI coding tools. I maintain it, and it ships an MCP server aisync mcp . While preparing it for the official MCP registry I found that uvx