modelcontextprotocol/servers

Prefer upstream unless you specifically need an older frozen snapshot; this fork adds no visible capabilities and is far behind current maintenance.

Choose this fork if you want the MCP reference servers plus extra distribution and AI-tooling metadata. Choose upstream if you want the latest server fixes and the cleanest reference baseline.

Prefer upstream unless you specifically need this frozen fork or its README-level customization. For adopters, the main signal is staleness: it adds little and misses substantial upstream progress.

Prefer upstream unless you specifically need this older snapshot; the fork adds no visible features and is far too stale for most adopters.

Prefer upstream unless you specifically want a frozen snapshot; this fork adds no visible capabilities and is materially behind on maintenance and recent improvements.

Prefer upstream unless you specifically need this exact historical snapshot; the fork adds no visible value and is far behind current fixes and capabilities.

Prefer upstream unless you explicitly need this older snapshot; the fork adds no visible functionality and is materially behind current upstream maintenance.

Choose upstream unless you specifically need the added contributor-improvement script. This fork looks like a narrow maintenance helper, not a better reference-server distribution, and its lag behind upstream is the main adoption concern.