Best for
- Developers working with the Go programming language
- Teams integrating MCP in CI/CD pipelines
- AI agent users seeking to reduce token consumption
P
Pare Go
Community
Structured Go tool output for AI agents
- Category
- Dev Tools #370 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js >=20
- Credentials
- No credential needed
- License
- MIT
- Last commit
- Tools
- 5
38FMRS · D
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.
Strongest · Maintenance 11/20 Weakest · Reliability 5/20
Why each score
- Reliability 5/20
- Only the server manifest and repository-level README were available; no source, tests, or CI evidence for packages/server-go were supplied. The manifest declares @paretools/go 0.22.0 over stdio with structured build/test/vet/fmt/mod output, and the README lists the Go server, so a happy path is plausible. However, the MCP init handshake, tool-list accuracy, real tool behavior, error handling, and dependency controllability cannot be verified. Missing execution evidence lowers the score under the static calibration, so reliability is 5.
- Security and permissions 8/20
- No red-line issues such as malware, credential theft, covert exfiltration, or destructive defaults are visible in the supplied materials; the local stdio transport also limits network exposure. However, without source access it is impossible to audit command execution paths, credential/environment handling, working-directory boundaries, or confirmation mechanisms for dangerous operations. go fmt/build/mod/test can modify files or execute code, and no explicit scoping or confirmation is documented. These gaps warrant a score of 8.
- Maintenance 11/20
- The repository is not archived, uses an MIT license, and the manifest shows version 0.22.0, indicating continued evolution; badges in the README are untrusted as evidence. No commit history, release cadence, issue-response track record, dependency update process, or security-response channel was provided. Governance and versioning evidence is incomplete, so maintenance is scored 11.
- Documentation 6/20
- The repository README covers the general architecture, structuredContent concept, configuration examples, and generic troubleshooting reasonably well. However, server-go-specific documentation, tool parameter tables, output schemas, limitations, and reviewable linked pages were not supplied. The README only points to tool-schema and response-example locations without providing their content. Because package-level documentation and verifiable evidence are missing, documentation is scored 6.
- Setup experience 8/20
- The manifest provides the npm identifier @paretools/go, version 0.22.0, and stdio transport, while the README states Node.js >= 20 and shows the general npx-based pattern, so the install path is broadly clear. There is no pare-go-specific client configuration example and no verifiable startup evidence. The static calibration caps setup at 15 without execution evidence, and the evidence supports only a manual-but-workable level, yielding a score of 8.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessRuns commands or code
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
Setup
Before you start
Runtime：Node.js >=20
Other optional settings (1)
PARE_TOOLS
Universal tool filter in server:tool,... format (e.g. go:build,go:test) applying across all Pare servers; set to empty to register no tools.
- Install the package using npm:
npm install @paretools/go. - Add the server to your MCP client configuration with command
npx -y @paretools/goand transport stdio. - Restart your client to apply changes.
Check that it works
Check that go_build, go_test, go_vet, go_fmt and go_mod appear in the client's tool list, or ask the agent to run go_build and confirm it returns structured JSON instead of raw terminal text.
Troubleshooting
- Ensure Node.js version is >= 20
- Check that `npx` is in PATH, or use a global install
- If connection times out, set `MCP_TIMEOUT=30000`
- Verify that the `go` command is available and the version is correct
Things to try
Once connected, you can ask your AI assistant things like:
- Build the current Go project and tell me if there are compile errors
- Run the Go tests for this project and summarize which tests failed
- Run go vet across the codebase and list any issues
- Format all Go files in the src directory
Tools 5
go_build writes
Runs `go build` and returns structured build results including errors and warnings.
go_test writes
Runs `go test` and returns structured test results including passed, failed, and skipped tests.
go_vet read-only
Runs `go vet` and returns a structured static analysis report.
go_fmt writes
Runs `gofmt` and returns a list of formatted files or diffs.
go_mod writes
Runs `go mod` commands and returns module information such as dependency graph or updates.
No matching tools
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 Desktop
Listed from the project's documentation, not tested by this site.
Overview
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.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method