Describe the bug
QuickstartWeatherServer project uses a reference to ModelContextProtocol project within the solution which differs from what is available via Nuget as ModelContextProtocol package. The solution project offers extensions which are not there in the Nuget package. So, the project will not build if I don't use the custom implementation of ModelContextProtocol project within a solution.

This is confusing and inconvenient when I try to create my own project using the Nuget packages that don't have what this custom ModelContextProtocol project has.

To Reproduce
Steps to reproduce the behavior:

1. Open the main ModelContextProtocol solution in VS2022.
2. Find QuickStartWeatherServer project. Check Dependencies / Projects. There should be no projects there.
3. Try to remove the project dependency and install the Nuget packages ModelContextProtocol and ModelContextProtocol.AspNetCore and the solution will not build.

Expected behavior
I want to be able to see examples from your projects with Nuget packages just the way you want me to do it in my project.

Logs
N/A

Additional context
These dependencies in Samples force us, developers, to do the same and to bypass your Nuget packages. That is not good. You should not be referencing a custom implementation in the Samples which doesn't align with your package in Nuget. This applies to all Samples.