Go
Run `go build`, `go test`, and `go vet` through MCP and feed the agent typed JSON diagnostics instead of unstructured compiler noise.
Overview
io.github.Dave-London/go is an MCP server for the Ship phase that returns Go build, test, and vet results as typed JSON diagnostics for coding agents.
What is this MCP server?
- Wraps Go toolchain commands with typed JSON diagnostic objects
- Targets build, test, and vet output for agent-friendly parsing
- Stdio npm package `@paretools/go` (v0.7.1) aligned with other Pare MCP servers
- Reduces token waste versus pasting full `go test -v` logs into chat
- npm package `@paretools/go` at version 0.7.1
- stdio MCP transport
- Repository: github.com/Dave-London/Pare
Community signal: 128 GitHub stars.
What problem does it solve?
Go command output is verbose and hard for agents to parse reliably when fixing compile errors and test failures.
Who is it for?
Indie builders maintaining Go backends or CLIs who want agent-driven fix loops after `go test` or `go vet`.
Skip if: Pure frontend workflows, languages other than Go, or teams that only run tests in remote CI without local MCP execution.
What do I get? / Deliverables
After registration, your agent receives compact JSON diagnostics from Go tooling and can target fixes file-by-file.
- MCP tools that execute Go build, test, or vet and return JSON diagnostics
- Shorter agent turns when fixing compile and test failures
Recommended MCP Servers
Journey fit
How it compares
MCP wrapper around local Go toolchain output, not a hosted test runner or a golangci-lint marketplace skill.
Common Questions / FAQ
Who is io.github.Dave-London/go for?
Go developers using MCP agents who want structured build, test, and vet feedback without copying terminal walls into the chat.
When should I use io.github.Dave-London/go?
Use it during ship and test cycles when you are iterating on Go packages and need the agent to read failures as typed diagnostics.
How do I add io.github.Dave-London/go to my agent?
Install `@paretools/go` from npm, configure stdio MCP in your client, and run it with access to your module directory and a working Go installation.