Pare Go
Surface Go build, test, vet, fmt, and mod output as typed JSON diagnostics for agent-led backend work.
Overview
Pare Go is an MCP server for the Build phase that turns Go build, test, vet, fmt, and mod output into structured JSON diagnostics.
What is this MCP server?
- Structured JSON for go build, test, vet, fmt, and mod tooling
- Stdio MCP via @paretools/go npm package (v0.8.1)
- Diagnostic-shaped output suited to fix-and-rerun agent loops
- Avoids parsing noisy compiler and test failure text by hand
- Fits solo Go microservices, CLIs, and worker binaries
- Server version 0.8.1
- npm package identifier @paretools/go
- stdio MCP transport
Community signal: 128 GitHub stars.
What problem does it solve?
Go compile and test output floods agent context, so fixes drift and reruns miss the exact failing package or line.
Who is it for?
Indie Go developers who want MCP-driven build and test loops on a local module without custom scripts.
Skip if: Polyglot shops with no Go code or teams that rely solely on remote CI logs instead of local go commands.
What do I get? / Deliverables
With Pare Go connected, agents consume typed diagnostics from Go tooling and close build-test cycles with less back-and-forth.
- JSON diagnostics from go build and test runs
- Structured vet, fmt, and mod command results
- Repeatable agent reruns after code changes
Recommended MCP Servers
Journey fit
How it compares
Go toolchain MCP with JSON diagnostics, not a Go tutorial skill or a generic shell runner.
Common Questions / FAQ
Who is Pare Go for?
Solo builders writing Go backends or CLIs who want agents to run standard Go commands and read structured error output.
When should I use Pare Go?
Use it while implementing Go packages when you need build, test, vet, fmt, or mod results inside an MCP agent session.
How do I add Pare Go to my agent?
Install @paretools/go from npm, configure stdio MCP, and ensure the Go toolchain is installed where the server executes commands.