We chose FastMCP because it treats MCP servers like FastAPI applications.
Decorator-based DX: Instead of writing verbose class-based boilerplate, we just use
@mcp.tool(). It feels exactly like writing a FastAPI route.
Pydantic Native: Since we heavily use Pydantic for data validation (SERP results, GSC data), FastMCP's native integration saved us hours of conversion work.
Built-in Image Support: FastMCP makes it incredibly easy to return multimodal responses (images + text), which is crucial for our "Site Health Check" features that visualize data.
SSE out-of-the-box: Connecting to Claude Desktop requires a robust Server-Sent Events implementation. FastMCP handles the handshake, keep-alive, and transport details automatically.
It's the "FastAPI moment" for the MCP ecosystem.
Raycast
From @jlowin :
FastMCP 3.0 is the platform MCP deserves in 2026, built to be as durable as it is future-proof: