Why is the maintenance frequency so low when this project helps you cross-user between users and FastAPI users?

[sunny-zhang-98]

I think this MCP is very useful. We don't even need a front-end page anymore; we only need a server-side component wrapped in MCP. This way, in the early stages of some projects, we can let AI manage the data for us without developing a front-end page. You can add some new annotations to help the AI ​​understand the MCP service more easily. We are very happy to support such a useful and creative project. Seeing so many friends asking questions proves that this is definitely a project with potential.
Thank you to the author for writing such beautiful code. I hope this project can develop rapidly and gain popularity.

[aniruddhaadak80]

The praise makes sense, but I also think the maintenance concern is fair. Projects like this become important infrastructure surprisingly quickly, and once people build internal workflows around them, long quiet periods start to feel risky even if the code still works.nnA small roadmap note or maintenance-status statement would probably go a long way here. It does not need to promise rapid feature work, just enough clarity for users to know whether the project is stable, paused, or actively evolving.

[nbraem]

It looks like this project is abandoned. FastMCP looks like a good alternative with a lot of momentum: https://github.com/PrefectHQ/fastmcp

[allmonday]

https://github.com/KLR-Pattern/fastapi-gql-mcp
I built this one to enhance the process of turning fastapi into mcp, it saves context and more friendly for agent