## Summary Rename `FastMCP` to `MCPServer` (or similar) and restructure so that transport-specific options are passed to `run()` rather than the constructor. ## Motivation - The name "FastMCP" was inherited from the original external project but doesn't clearly convey what it is - The constructor currently accepts many HTTP-specific options (`host`, `port`, `stateless_http`, etc.) that only apply when running with a specific transport - This couples server definition with transport configuration - Users are confused about the relationship between FastMCP v2 (external library) and FastMCP in the official SDK (see #1068) ## Goal - Clear, descriptive name for the high-level server class - Constructor focused on server identity and capabilities - Transport-specific options moved to `run()` or transport configuration - Document the relationship between FastMCP v2 (external library) and the official MCP Python SDK ## Consolidates - #1068 (FastMCP 2.0 vs MCP Python SDK Server - user confusion about naming) --- <sub>[AI Disclaimer](https://gist.github.com/maxisbey/6123d132484e4c533eab519a2800693d)</sub>
Summary
Rename
FastMCPtoMCPServer(or similar) and restructure so that transport-specific options are passed torun()rather than the constructor.Motivation
host,port,stateless_http, etc.) that only apply when running with a specific transportGoal
run()or transport configurationConsolidates
AI Disclaimer