kratos

Why we included this project

Go teams that want a structured route from a single service into a set of cooperating services will find Kratos a solid place to start. The framework is API-first in a concrete way: you define the contract in Protobuf, generate the HTTP and gRPC servers, and spend your time on business logic instead of wiring transport and middleware by hand. Production concerns like service discovery and logging sit behind small, explicit interfaces rather than framework magic. The MCP transport support is what makes it interesting for AI work, because the same service skeleton can expose tools to AI agents without splitting into a separate stack. That suits Go backends that need to speak the Model Context Protocol while keeping the rest of the API conventional.