npm deprecations force unplanned migrations

2 posts from 2 people2d activeFading, +0 this weekunverified

Posts per day2 posts, Aug 28 to Nov 9

The posts behind it

GitHub issuesmodelcontextprotocol/servers · BerkantACUNSep 9

Four archived reference servers still pull ~214k installs/week, and their npm deprecation message points at npm support rather than a replacement

Measured today (2026-09-09), live from `api.npmjs.org`: | Package | Downloads/week | Version | Published | |---|---:|---|---| | `@modelcontextprotocol/server-postgres` | 95,430 | 0.6.2 | 2026-07-03 | | `@modelcontextprotocol/server-github` | 84,416 | 2025.4.8 | 2026-07-03 | |...

GitHub issuesmodelcontextprotocol/servers · olaservoAug 28

npm deprecate @modelcontextprotocol/server-filesystem@<=2025.8.21 (empty tool schemas under zod v4)

Follow-up to #4661, which is fixed in the package but not communicated to anyone still pinned to an old version. ## What's wrong Every published `server-filesystem` up to and including `2025.8.21` calls `zodToJsonSchema` directly to build its tool schemas. `zod-to-json-schema`...

3 replies

Companies and products named

npm

2 posts

Model Context Protocol

2 posts

PostgreSQL

1 post

GitHub

1 post

About this problem

Evidence

2 posts from 2 people in 1 place, about 1 a week over 13 days. Mostly on modelcontextprotocol/servers. Tools named alongside: Model Context Protocol, PostgreSQL, GitHub.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "deprecation" rule about npm. First post Aug 28, 2026, latest Sep 9, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere