FastMCP
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
2recommend
2warn against
Nov 3, 2025first mention
Oct 2, 2026latest mention
Why people recommend it
“The official website modelcontextprotocol refers to FastMCP in their examples”
“retreat towards python's FastMCP”
Caveats and dissent
“This resulted in a lot of confusion by users, which persists to this day.”
“calling itself "the standard framework" doesn't feel right to me”
Often compared with
Who recommends it in their own words
Threads where it came up
- Welcome to FastMCP 4 mentions
- Why we migrated from Python to Node.js 2 mentions
- Ask HN: Who wants to be hired? (October 2026) 1 mention
- I built a game where AI agents compete to ship code; live WASM every 5 minutes 1 mention
- I open-sourced Claude's best feature 1 mention
- Personal MCP server on every Claude platform without Auth0 1 mention
Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 12
“Elasticsearch, FastMCP, Kafka”
“Stack: FastAPI + FastMCP”
“so we could spin something up with FastMCP”
“This resulted in a lot of confusion by users, which persists to this day.”
“this has some nice twists on the theme”
“The official website modelcontextprotocol refers to FastMCP in their examples”
“calling itself "the standard framework" doesn't feel right to me”
“FastMCP gives you an in-memory test provider (useless in prod) or a proxy that requires Google/GitHub/Auth0”
“retreat towards python's FastMCP”
I agree with your analysis of building your own Agent framework to have some level of control and fewer abstractions. Agents at their core are about programmatically talking to an LLM and performing these basic operations: 1. Structured Input and String Interpolation in prompts 2. Structured Output and Unmarshalling String response to Structured output (This is getting easier now with LLMs supporting Structured outpu
async python has problems, but "anyio exists" is not one of them that can be blamed on python, simply dont use weird third party libraries trying to second guess the asyncio architecture edit: ironically I'm the author of a weird third party library trying to second guess the asyncio architecture but mine is good https://awaitlet.sqlalchemy.org/en/latest/ (but I'll likely be retiring it in the coming year due to lack
“landed on FastMCP, FastAPI, PydanticAI”