nunu

Nunu is a Go-based CLI tool that scaffolds and manages Go applications. It provides a streamlined workflow for creating new projects, generating common components (handlers, services, repositories, models), and running the application with live reloading. When used as an MCP server, this repository exposes the Nunu CLI as the service endpoint that can be interacted with through the MCP protocol, enabling automated tooling and orchestration in larger systems. The CLI integrates popular Go libraries (Gin, Gorm, Wire, Viper, Zap, and more) to deliver a fast, opinionated starting point for Go projects, with DI via Wire and a modular architecture that supports extension through modules and templates. Tools available include: go install to upgrade the nunu binary, nunu new to scaffold a project, nunu create to generate components, and nunu run to start the server with hot-reload capabilities.

Prerequisites:

• Go 1.19 or higher
• Git
• Optional: Docker (for containerized deployments)

Install the Nunu CLI (Go tool):

go install github.com/go-nunu/nunu@latest

Verify installation:

nu nu --version

Create a new Go project with Nunu:

nunu new myProject

Navigate to your project directory and run the project locally:

nunu run

If you prefer containerized runs, you can build a Docker image for your project (where applicable) and run it with Docker:

docker build -t my-nunu-project .
docker run -it --rm my-nunu-project

Notes:

• Ensure your Go environment GOPATH and GOBIN are configured if you rely on the go install path.
• The MCP server integration is exposed through the Nunu CLI; consult repository docs for MCP-specific endpoints and protocol details.

Tips and common issues:

• If the nunu command is not found after installation, ensure that your GOBIN (or Go binaries directory) is in your PATH.
• For Windows users, ensure GO111MODULE=on and that your shell environment is configured to locate the Go binaries.
• When creating new projects, you can use -r with mirrors such as the Gitee templates for a faster setup in restricted environments.
• Docker is optional but recommended for consistent runtime environments and easier deployment.
• The MCP integration relies on the CLI's ability to start the server; use nunu run to enable hot-reloading during development.
• Review the generated project structure (cmd, config, internal, pkg, etc.) to understand where to hook MCP-specific endpoints or adapters.