Discussion: I kept reinventing auth and boilerplate on every MCP project. Built NitroStack to stop doing that.

Saw an interesting discussion on r/MCP about this — wanted to bring it here. **Original topic:** I kept reinventing auth and boilerplate on every MCP project. Built NitroStack to stop doing that. > Been building with MCP for a while and kept hitting the same wall: no real framework. You wire up boilerplate manually, reinvent auth every project, have no proper IDE for debugging tool calls, and deployment is entirely your problem. I built NitroStack to fix that. It's an open source TypeScript f... What are your thoughts? Has anyone here dealt with MCP server? --- *Discuss more at [0n MCP](https://www.0nmcp.com) — the hub for [AI workflow automation](https://www.0nmcp.com).*