[kirkwat]

• mcp/ holds the mcp-jobspy package (README, LICENSE) and server.json: the package pins python-jobspy[mcp] to the same version and provides the mcp-jobspy command, so uvx mcp-jobspy@latest runs the newest server
• The release workflow checks the tag against every version string, builds both packages and checks their metadata before uploading either, then publishes python-jobspy, mcp-jobspy (Trusted Publishing) and the registry entry; uploads skip files already on PyPI, so a failed job can be re-run
• CI builds mcp-jobspy on every PR, installs it with the python-jobspy wheel (a wrong pin fails the install) and starts it
• The registry entry lists mcp-jobspy as its package, so clients run uvx mcp-jobspy@<version> with no extra arguments
• README: the MCP section links to mcp/README.md for setup, which uses uvx mcp-jobspy@latest; the mcp-name line moves to mcp-jobspy's README