modelcontextprotocol / modelcontextprotocol/typescript-sdk
TS SDK Add first-class SEP-2640 Skills extension APIs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
Problem
SEP-2640 is accepted and conformance coverage landed in modelcontextprotocol/conformance#330. The official TypeScript SDK can express the extension through custom handlers, but it does not provide Skills-specific APIs.
Olaservo's reusable @olaservo/ext-skills prototype already provides server and client APIs and was previously proposed in modelcontextprotocol/ext-skills#71. That PR was closed with the note that the implementation would move to the TypeScript SDK.
PR #2797 adds a conformant TypeScript server fixture, but no public SDK API.
Proposed direction
Adapt Olaservo's Apache-2.0 implementation with attribution, in small phases:
- Shared schemas, types, and
skills/list/skills/getoperations. - Server registration and filesystem discovery.
- Verified client resource reads.
- Optional
resources/directory/read, documentation, and examples.
Use modelcontextprotocol/conformance#330 as the acceptance test.
Questions
- Should this be a new workspace package or live in the existing client/server packages?
- Should
resources/directory/readbe included initially or added separately?
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
Start by reviewing the @olaservo/ext-skills implementation, PR #2797's conformant TypeScript server fixture, and modelcontextprotocol/conformance#330. Work through the proposed phases for schemas, skills/list and skills/get, server and client APIs, and resource reads. Done means the TypeScript SDK exposes the agreed Skills APIs and passes the SEP-2640 conformance coverage.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100