README: the client config example installs archived servers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Start with the “Using an MCP Client” example and the Windows note in the root README.md, then check which servers are active in the README’s Archived section. Update the example to use only active reference servers and keep the Windows note accurate; review the result against SECURITY.md on v2/main. Done when the example no longer installs archived servers.
Written by the indexing model from the issue text.
Description
Problem
The "Using an MCP Client" example in the root README.md configures @modelcontextprotocol/server-github and @modelcontextprotocol/server-postgres. Both are archived (the README lists them under its own Archived heading) and get no fixes, so new users who copy the example install unmaintained packages.
Expected
The example uses only active reference servers, and the Windows note after it stays accurate. (SECURITY.md already covers archived servers on v2/main.)
Prior work
- #4381 by @go165
- #4788 by @FOWEPJF255
The PR(s) above targeted the pre-refactor code and are closed as part of the backlog triage in #4875; this issue is where the work continues, with the PR(s) as a prototype. Thank you to their authors.
- Dominant language
- TypeScript
- Stars
- 91.4k
- Forks
- 11.8k
- Avg merge
- 7h 36m
- Merged PRs (30d)
- 126
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from modelcontextprotocol/servers
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelcontextprotocol/servers#5217 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5216 ·
Maintainers usually reply within 1 day
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
modelcontextprotocol/servers#5215 ·
Maintainers usually reply within 1 day
-
documentation server-git server-time v2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5213 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation v2
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5212 · 1 comment ·
Maintainers usually reply within 1 day
All issues in modelcontextprotocol/servers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chaitin/MonkeyCode#1437 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
carbon-design-system/carbon-ai-chat#2615 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
redhat-developer/rhdh-plugin-export-overlays#4486 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: fileUploadMatrix.test.ts URL case does a real DNS lookup and fails offlinePossibly taken @r2jaff claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ComposioHQ/composio#5054 ·
Maintainers usually reply within 1 day