Mmcp.market

Pare Go MCP server

by Dave-London·io.github.Dave-London/pare-go·v0.8.1·138 stars
No reviews yet

Pare Go ג€” Structured Go tool output (build, test, vet, fmt, mod) as typed JSON diagnostics.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

138 stars

Reviews

Write one

Nobody has reviewed Pare Go yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pare Go tools (9, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • buildwrite action

    Runs go build and returns structured error list (file, line, column, message). Use instead of running `go build` in the terminal.

  • env

    Returns Go environment variables as structured JSON. Optionally request specific variables. Use instead of running `go env` in the terminal.

  • fmt

    Checks or fixes Go source formatting using gofmt. In check mode (-l), lists unformatted files. In fix mode (-w), rewrites files. Use instead of running `gofmt` in the terminal.

  • generatewrite action

    Runs go generate directives in Go source files. Use instead of running `go generate` in the terminal. WARNING: `go generate` executes arbitrary commands embedded in //go:generate directives in source files. Only use this tool on trusted code that you have reviewed.

  • get

    Downloads and installs Go packages and their dependencies. Use instead of running `go get` in the terminal.

  • list

    Lists Go packages and returns structured package information (dir, importPath, name, goFiles). Use instead of running `go list` in the terminal.

  • mod-tidywrite action

    Runs go mod tidy to add missing and remove unused module dependencies. Use instead of running `go mod tidy` in the terminal.

  • runwrite action

    Runs a Go program and returns structured output (stdout, stderr, exit code). Use instead of running `go run` in the terminal.

  • vetwrite action

    Runs go vet and returns structured static analysis diagnostics. Use instead of running `go vet` in the terminal.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan33 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Pare Go in Claude Code, Cursor or VS Code

Runs npx -y @paretools/go on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pare-go -- npx -y @paretools/go
Add to Cursor

What the publisher says

From the Pare Go repository's README, as published. We do not edit it. Read it on GitHub

  Pare

Reliable, structured CLI output for AI agents — no more parsing fragile terminal text.

Pare provides MCP servers that wrap common developer tools (git, npm, docker, test runners, etc.) and return clean, schema-validated JSON instead of raw terminal text. Agents get typed data they can act on directly, without brittle string parsing.

The Problem

Parsing CLI output is fragile. Raw terminal text includes ANSI escape codes, decorative headers, progress bars, locale-specific formatting, and platform differences that break agent workflows in subtle ways. An agent that works fine with git status on macOS may fail on Windows because the output format changed. A test runner's summary line might shift between versions, silently breaking a regex.

Pare eliminates this entire class of errors by returning schema-validated JSON with consistent field names, regardless of platform, tool version, or locale. As a bonus, structured output is significantly smaller — agents use fewer tokens per tool call:

Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like eslint or tsc, the main advantage is reliable structured data — agents can use typed JSON directly rather than parsing strings.

How It Works

Each Pare tool returns two outputs:

  • content — human-readable text, for MCP clients that display it
  • structuredContent — typed, schema-validated JSON, ready for agents to process

This uses MCP's structuredContent and outputSchema features to provide type-safe, validated data that agents can rely on without custom parsing.

Example: git status

Raw git output (~118 tokens):

On branch main
Your branch is ahead of 'origin/main' by 2 commits.
  (use "git push" to publish your local commits)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pare Go: common questions

Is Pare Go MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Pare Go safety report
How do I install Pare Go?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pare Go need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pare Go maintained?
The last commit was 21 days ago (2026-09-22). The latest release is v0.8.1.

More from Dave-London →