# modelcontextprotocol/servers · RepoSense Release & Migration Intelligence

> test(everything): check every registered tool carries all. Upgrade immediately to patch advisory. Migration: Low.

## Metadata
- **Repository URL**: https://github.com/modelcontextprotocol/servers
- **Primary Package**: `@modelcontextprotocol/server-filesystem` (NPM)
- **Categories**: `AI-AGENT`
- **Latest Version**: `v2.3.0`
- **Semantic Status**: `SECURITY_PATCH`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/modelcontextprotocol/servers/releases.atom

## The Human Context (Plain-English Pitch)
Model Context Protocol (MCP) Servers are standardized connectors that let AI assistants safely read local files, query databases, and call external APIs. Instead of writing custom integration code for every AI client, developers can build one MCP server that works across Claude, IDEs, and agent frameworks.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
test(everything): check every registered tool carries all. Upgrade immediately to patch advisory. Migration: Low.

## Breaking Changes & Required Actions
- test(everything): check every registered tool carries all four annotation hints by @cliffhall in #5347
- fix(everything): name resource-prompt's allowed argument values by @cliffhall in #5350
- everything: build the Docker image from the workspace lockfile, with a Streamable HTTP mode by @cliffhall in #5382
- feat(everything): add a resource collection example by @cliffhall in #5365

## Migration Snippet
```ts
npm install @modelcontextprotocol/server-filesystem@2.3.0
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v2.3.0** (2026-11-04) [SECURITY_PATCH]: test(everything): check every registered tool carries all. Upgrade immediately to patch advisory. Migration: Low.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is modelcontextprotocol/servers v2.3.0 safe to upgrade in production?
modelcontextprotocol/servers v2.3.0 is classified as SECURITY_PATCH (MINOR release). test(everything): check every registered tool carries all. Upgrade immediately to patch advisory. Migration: Low.

### What breaking changes or compatibility risks exist in modelcontextprotocol/servers v2.3.0?
No breaking API changes or peer dependency conflicts are recorded for modelcontextprotocol/servers v2.3.0 in the RepoSense compatibility graph.

### What is the bundle size impact of @modelcontextprotocol/server-filesystem v2.3.0?
Measured bundle size telemetry is currently unavailable for @modelcontextprotocol/server-filesystem v2.3.0; verify build output locally before deploying.

### How do I upgrade @modelcontextprotocol/server-filesystem to v2.3.0?
Upgrade @modelcontextprotocol/server-filesystem to v2.3.0 by running "npm install @modelcontextprotocol/server-filesystem@2.3.0" and applying the migration steps: npm install @modelcontextprotocol/server-filesystem@2.3.0