migrate-v1-to-v2
CommunityMigrate MCP SDK from v1 to v2 with best practices
Authorgcapnias
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This migration guide helps teams upgrade MCP TypeScript SDK code from v1 to v2, aligning dependencies, imports, and API usage to the modern v2 contracts, reducing technical debt and future maintenance overhead.
Core Features & Use Cases
- Provides import mapping guidance to replace v1 imports with v2 packages and align with new symbol names and error models.
- Covers the tool migration required by v2 (registerTool, registerPrompt, registerResource) and the mandatory wrapping of raw Zod shapes into z.object().
- Addresses runtime changes such as header handling, JSON schema validation, and client/server boundary updates to ensure a smooth, end-to-end upgrade across projects.
Quick Start
Install the v2 packages and follow the mapping guidelines to begin migrating your codebase.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: migrate-v1-to-v2 Download link: https://github.com/gcapnias/server-features/archive/main.zip#migrate-v1-to-v2 Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.