modelcontextprotocol / modelcontextprotocol/typescript-sdk
Type-first as opposed to Zod schema-first approach
Open
Nobody has claimed this yet.
breaking change
enhancement
needs decision
P3
v2
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
Consider a type-first approach rather than the current Zod schema-first approach.
Part of v2 SDK work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the current Zod schema-first implementation and the broader v2 SDK work, then clarify the intended type-first design and acceptance criteria before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100