migrate-mcp-ts-template

To migrate an mcp-ts-template fork, install the @cyanheads/mcp-ts-core package and rewrite internal @/ framework imports to package subpaths. The workflow updates src/index.ts to use createApp(), modifies configs, and removes bundled framework files from src/.

Refactoring imports to use @cyanheads/mcp-ts-core preserves your server-specific artifacts such as tools, resources, prompts, and services. The migration only targets embedded framework code and internal @/ path imports, leaving your custom implementation files intact while simplifying future upgrades.

Yes, refactoring local framework imports to package subpaths requires a Bun or Node runtime environment. The migration workflow uses these environments to install @cyanheads/mcp-ts-core, scan src/ directories for internal imports, and run dev checks verifying no local framework code remains.

If your mcp-ts-template fork still has local framework code after updating dependencies, the embedded framework files in src/ were not removed. The migration workflow requires explicitly deleting bundled framework sources after rewriting @/ imports to @cyanheads/mcp-ts-core subpaths and updating entry points.

The best way to update entry points when moving to an MCP core package is modifying src/index.ts to call createApp() imported from @cyanheads/mcp-ts-core. This replaces local framework initialization, aligns configuration with the package, and ensures clean upgrades to MCP infrastructure.

The migration workflow automates scanning src/ for @/ imports and rewriting them to package subpaths, but requires manual verification to ensure no local framework code remains. It updates entry points and configs, then runs dev checks to confirm bundled framework files are successfully removed.