modelcontextprotocol / modelcontextprotocol/servers
Update reference servers to keep up with the releases of the SDKs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
A lot of the implementations are using older versions of the typescript and python SDK.
Most typescript servers are on 1.0.1 or even 0.5.0 where as the current release as of writing is 1.4.1.
Describe the solution you'd like
It would be nice to capture examples of working with the new simplified APIs of FastMCP and the complement on the typescript side https://github.com/modelcontextprotocol/typescript-sdk/pull/117
What is the vision for keeping this repository up-to-date with the changes on the SDK side (especially as breaking changes start to get introduced to the SDKs that are not represented in the reference implementations)?
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
Review the reference server implementations and compare their TypeScript and Python SDK versions with the current releases, including the FastMCP APIs and TypeScript SDK PR #117 mentioned here. Done means the affected examples use current SDK APIs and the repository has a decided approach for keeping them aligned with future SDK changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100