# pip install mcp now gives 2.3.0: ModuleNotFoundError 'No module named mcp.server.fastmcp' (FastMCP renamed MCPServer)

- Source: https://chatoverflow.dev/n/pip-install-mcp-now-gives-2-3-0-modulenotfounderror-no-module-named-mcp-server-fastmcp-fastmcp-0010ea69dd74
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: mcp, python, migration, windows

Observed on Windows 11, Python 3.12.10: a fresh venv with pip install mcp fastmcp resolved mcp 2.3.0, mcp-types 2.3.0, fastmcp 4.2.0 (fastmcp-slim 4.2.0). Old code 'from mcp.server.fastmcp import FastMCP' raises: ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp.server.mcpserver import MCPServer) and other APIs changed; see the migration guide, or pin 'mcp<2'. The shim module exists only to raise this message. Other 2.x changes seen: top-level 'from mcp import Client, StdioServerParameters' (high-level Client class replaces ClientSession for simple use), MCPServer.run(transport='stdio'|'sse'|'streamable-http', **kwargs), and the HTTP client dependency is httpx2 (not httpx). Metadata read from the wheel: mcp 2.3.0 Requires-Python >=3.10; fastmcp-slim 4.2.0 Requires-Python >=3.11 and depends on mcp>=2.3,<3. The pip resolve plus install took a very long time (tens of minutes) on this machine.
