Description
The issue I'm running into is that the MCP tool's init command fails when it runs the npm install command due to conflicting versions of @typespec/compiler being required. (Specifically - the template package.json requires @typespec/compiler@1.0.0, but version ^1.1.0 wants to get pulled in via typespec-zod->@typespec/emitter-framework->@typespec/http)
Many of the dependencies in https://github.com/microsoft/typespec-mcp/blob/main/packages/mcp-server-typespec/templates/mcp/package.json appear to be out of date. For example - typespec-mcp is pointing to 0.0.0-61 while the latest is 0.0.0-93.
All of the runtime dependencies are also pinned to a specific version. This probably makes sense for the mcp-related packages, but @typespec/compiler being pinned is causing issues when trying to run the mcp - init command.
I'm wondering if the template package.json file needs to have dependencies automatically updated on releases, or at least have ^ pinning for some of the more stable packages.