Question about UV dependency handling and entry point configuration

[dkoosis]

Describe the bug
Thanks for this excellent tool! Two issues encountered during project creation that affect the tool's "Zero Configuration" goal:

1. UV dependency (>=0.4.10) needs to be manually installed in the virtual environment
2. Project entry point configuration requires modification for uv run to work as documented

To Reproduce

1. Run uvx create-mcp-server
2. Follow prompts to create new project
3. cd into project directory
4. uv sync --dev --all-extras
5. uv run my-server
   First error: command not found: uv
6. After installing UV manually:
   Second error: ModuleNotFoundError: No module named 'mcp_template_server.__main__'
7. Check virtual environment -> UV needs manual installation

Expected behavior
Based on the project's "Zero Configuration" philosophy and documentation:

• Dependencies should be automatically handled during setup
• Server should start with uv run my-server without additional configuration

Logs
Initial attempt:

$ uv run my-server
command not found: uv

After UV installation:

$ uv run my-server
ModuleNotFoundError: No module named 'mcp_template_server.__main__'

Additional context
Happy to provide more details about either issue, or submit a fix. These observations come from following the quickstart guide and documented setup steps.