← Back to directory
P

Pare Go

Community
Structured Go tool output for AI agents
GitHub source repository ↗
★ 138 Stars Category · Dev Tools Popular Source revision 57e1980e8375
38FMRS · D
Reliability
5/20
Security and permissions
8/20
Maintenance
11/20
Documentation
6/20
Setup experience
8/20

Pare Go significantly improves the accessibility of Go tools for AI agents by providing structured JSON output. It addresses the fragility of text parsing and reduces token usage. It is a reliable tool for Go developers, but non-Go users will not need it.

Read the FMRS scoring method →

Pare Go is an MCP server that wraps Go command-line tools (build, test, vet, fmt, mod) and returns typed JSON diagnostics instead of raw terminal text. It eliminates the need to parse fragile text output, providing reliable, schema-validated data for AI agents while significantly reducing token usage.

Tools

go_build
Runs `go build` and returns structured build results including errors and warnings.
go_test
Runs `go test` and returns structured test results including passed, failed, and skipped tests.
go_vet
Runs `go vet` and returns a structured static analysis report.
go_fmt
Runs `gofmt` and returns a list of formatted files or diffs.
go_mod
Runs `go mod` commands and returns module information such as dependency graph or updates.

Setup

  1. Install the package using npm: npm install @paretools/go.
  2. Add the server to your MCP client configuration with command npx -y @paretools/go and transport stdio.
  3. Restart your client to apply changes.

Fit and risk

Best for

  • Developers working with the Go programming language
  • Teams integrating MCP in CI/CD pipelines
  • AI agent users seeking to reduce token consumption

Not for

  • Developers not using Go
  • Users who prefer parsing raw terminal text
  • Scenarios requiring non-Go tooling support

Required permissions

  • Executing Go command-line tools (go build, go test, etc.)
  • Reading files in the project directory (e.g., go.mod)
  • Running commands that require file system access

Risks and side effects

  • Malicious or misconfigured Go commands could lead to unintended builds or test executions
  • Go version in the environment may affect output format
  • Improper tool selection may cause excessive command execution

Troubleshooting

  1. Ensure Node.js version is >= 20
  2. Check that `npx` is in PATH, or use a global install
  3. If connection times out, set `MCP_TIMEOUT=30000`
  4. Verify that the `go` command is available and the version is correct

Use cases

AI agents needing reliable build status checks for Go projects
Automated test workflows requiring structured test results
Quality checks with vet and fmt diagnostics
Dependency management with clean `go mod` output

Supported clients

Claude DesktopFull support