Building a Production-Ready MCP Server: Async PostgreSQL, OpenTelemetry, and Kubernetes in One Template

Building a Production-Ready MCP Server: Async PostgreSQL, OpenTelemetry, and Kubernetes in One Template Most MCP server examples stop at "hello world." A few tools, an in-memory data store, and a uvicorn main:app command. That is fine for a demo, but the moment you try to ship one in production you immediately run into the same four problems: How do I manage a database connection pool safely across concurrent async tool calls? How do I prevent a malicious prompt from invoking tools it should never reach? How do I get distributed traces into my existing observability stack? How do I deploy this to Kubernetes without hardcoding secrets? I spent time solving all of these and packaged the result as a template anyone can fork: fastmcp-production-template . This post explains the decisions behind each piece. What Is MCP and Why Does It Need a Production Template? The Model Context Protocol (MCP) is an open standard that lets AI clients like Claude discover and call typed tools exposed by a s