nunu-layout

This MCP server is a Go-based example built with the Nunu framework and MCP-GO. It exposes three default transport protocols for testing and integration: STDIO for local CLI tooling, SSE for real-time browser-friendly communication, and StreamableHTTP for standard HTTP-based MCP interactions. You can build the server from source, run it locally, and connect the MCP Inspector to debug and explore capabilities such as resources, prompts, and tools exposed by the MCP server. After starting, you can open http://127.0.0.1:6274 to test available transports, and use the Inspector to send commands and inspect responses across the supported protocols.

Prerequisites:

• Go installed (1.20+ recommended)
• Git
• Optional: Node.js installed if you plan to use MCP Inspector locally (npx @modelcontextprotocol/inspector)
• Optional: Docker (for the provided container run)

Install and run from source (recommended for development):

1. Clone the repository and navigate into it

git clone https://github.com/go-nunu/nunu-layout-mcp.git
cd nunu-layout-mcp

2. Build the MCP server

cd mcp-demo
go build -ldflags="-s -w" -o ./bin/server ./cmd/server

3. Run the server locally (example using the built binary)

./bin/server

4. Start the MCP Inspector (optional, requires Node.js)

npx -y @modelcontextprotocol/inspector ./bin/server

Alternatively, run via Docker (example):

# Pull and run the provided image
docker pull go-nunu/nunu-layout-mcp:latest
docker run -i go-nunu/nunu-layout-mcp:latest

Notes and tips:

• The MCP server by default enables STDIO, SSE, and StreamableHTTP protocols. You can modify or disable protocols in internal/server/mcp.go if needed.
• If using STDIO for MCP STDIO interactions, avoid printing logs to the terminal to prevent breaking the STDIO channel; configure logs to write to a file instead.
• The server exposes a test surface at http://127.0.0.1:6274 for protocol testing via the browser.
• When using Inspector locally, ensure Node.js is installed because the Inspector is a Node-based tool.
• If you modify configuration, you can add a local YAML/JSON config as described in the sample to control log levels and endpoints.
• This example focuses on illustrating how to wire an MCP server; adjust the server path, image names, and ports according to your environment.