Lets AI clients run structured GitHub operations like pull requests, issues, and actions as typed JSON.
Also known as Dave-London/Pare, @paretools/github
- Stars
- 141
- Tools
- 15
- Downloads, 30 days
- —
- Latest version
- 0.8.1
- Last commit
- Nov 10, 2026
- License
- MIT
What is Pare GitHub MCP?
Pare GitHub lets AI clients run structured GitHub operations like pull requests, issues, and actions as typed JSON. It exposes 15 tools, such as pr-view, pr-list, pr-create.
Summary generated from the project's README
About Pare GitHub MCP server
Automating GitHub operations like managing pull requests, issues, and actions is what developers achieve using this MCP server. It provides AI agents with structured, schema-validated JSON instead of raw, fragile terminal text. This approach prevents errors caused by parsing ANSI escape codes, progress bars, or platform-specific formatting that often breaks traditional CLI workflows.
By using this server, agents receive typed data they can act on directly through the structuredContent feature. This method significantly reduces token usage; for example, a git log command can see a 92% reduction in tokens compared to raw text. The server is designed for local integration with clients like Claude Desktop, Cursor, and Windsurf, requiring Node.js 20 or higher for setup.
Users can fine-tune agent capabilities by using environment variables to filter specific tools. You can restrict a server to only certain commands, such as allowing only status and log via PARE_GIT_TOOLS, or use a universal PARE_TOOLS variable to limit access across your entire stack.
What you can do with it
- 1Reduce agent token costsDevelopers can lower the number of tokens consumed by long command outputs like git logs or npm installs.
Written from the project's README. Every use case is checked against a quote from it.
How to install Pare GitHub MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Pare GitHub MCP in Claude Code
$ claude mcp add pare-github -- npx -y @paretools/githubInstall Pare GitHub MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pare-github": {
"command": "npx",
"args": [
"-y",
"@paretools/github"
]
}
}
}Install Pare GitHub MCP in VS Code
.vscode/mcp.json
{
"servers": {
"pare-github": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@paretools/github"
]
}
}
}Install Pare GitHub MCP in VS Code CLI
$ code --add-mcp '{"name":"pare-github","type":"stdio","command":"npx","args":["-y","@paretools/github"]}'Install Pare GitHub MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pare-github": {
"command": "npx",
"args": [
"-y",
"@paretools/github"
]
}
}
}Install Pare GitHub MCP in Codex
$ codex mcp add pare-github -- npx -y @paretools/githubInstall Pare GitHub MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.pare-github] command = "npx" args = ["-y", "@paretools/github"]
Install Pare GitHub MCP in Gemini CLI
$ gemini mcp add -s user pare-github npx -- -y @paretools/githubInstall Pare GitHub MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pare-github": {
"command": "npx",
"args": [
"-y",
"@paretools/github"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @paretools/github 0.7.1 in an isolated container with no network and no keys. It answered and listed 8 tools.
Pare GitHub MCP tools 15
Read from the server with tools/listpr-viewViews a pull request by number. Returns structured data with state, checks, review decision, and diff stats. Use instead of running `gh pr view` in the terminal.
pr-listLists pull requests with optional filters. Returns structured list with PR number, state, title, author, and branch. Use instead of running `gh pr list` in the terminal.
pr-createCreates a new pull request. Returns structured data with PR number and URL. Use instead of running `gh pr create` in the terminal.
pr-mergeMerges a pull request by number. Returns structured data with merge status, method, and URL. Use instead of running `gh pr merge` in the terminal.
pr-commentAdds a comment to a pull request. Returns structured data with the comment URL. Use instead of running `gh pr comment` in the terminal.
pr-reviewSubmits a review on a pull request (approve, request-changes, or comment). Returns structured data with the review event and URL. Use instead of running `gh pr review` in the terminal.
pr-updateUpdates pull request metadata (title, body, labels, assignees). Returns structured data with PR number and URL. Use instead of running `gh pr edit` in the terminal.
issue-viewViews an issue by number. Returns structured data with state, labels, assignees, and body. Use instead of running `gh issue view` in the terminal.
issue-listLists issues with optional filters. Returns structured list with issue number, state, title, labels, and assignees. Use instead of running `gh issue list` in the terminal.
issue-createCreates a new issue. Returns structured data with issue number and URL. Use instead of running `gh issue create` in the terminal.
issue-closeCloses an issue with an optional comment and reason. Returns structured data with issue number, state, and URL. Use instead of running `gh issue close` in the terminal.
issue-commentAdds a comment to an issue. Returns structured data with the comment URL. Use instead of running `gh issue comment` in the terminal.
Show all 15 toolsShow fewer tools
issue-updateUpdates issue metadata (title, body, labels, assignees). Returns structured data with issue number and URL. Use instead of running `gh issue edit` in the terminal.
run-viewViews a workflow run by ID. Returns structured data with status, conclusion, jobs, and workflow details. Use instead of running `gh run view` in the terminal.
run-listLists workflow runs with optional filters. Returns structured list with run ID, status, conclusion, and workflow details. Use instead of running `gh run list` in the terminal.
Configuration
PARE_GIT_TOOLSPARE_NPM_TOOLSPARE_TOOLS
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachabledave-london/pare is public and reachablegithub.com/dave-london/pare ↗Pass
- Package names this repository as its source@paretools/github names dave-london/pare as sourcenpmjs.com/package/@paretools/github ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @paretools/githubnpmjs.com/package/@paretools/github/v/0.8.1#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-10github.com/dave-london/pare ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @paretools/githubPass
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model15 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubReliable, 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:
| Tool Command | Raw Tokens | Pare Tokens | Reduction |
|---|---|---|---|
docker build (multi-stage, 11 steps) |
373 | 20 | 95% |
git log --stat (5 commits, verbose) |
4,992 | 382 | 92% |
npm install (487 packages, warnings) |
241 | 41 | 83% |
vitest run (28 tests, all pass) |
196 | 39 | 80% |
cargo build (2 errors, help text) |
436 | 138 | 68% |
pip install (9 packages, progress bars) |
288 | 101 | 65% |
cargo test (12 tests, 2 failures) |
351 | 190 | 46% |
npm audit (4 vulnerabilities) |
287 | 185 | 36% |
Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like
eslintortsc, 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 itstructuredContent— 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)
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: src/index.ts
new file: src/utils.ts
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: README.md
Untracked files:
(use "git add <file>..." to include in what will be committed)
temp.log
Pare structured output (~59 tokens):
{
"branch": "main",
"upstream": "origin/main",
"ahead": 2,
"staged": [
{ "file": "src/index.ts", "status": "modified" },
{ "file": "src/utils.ts", "status": "added" }
],
"modified": ["README.md"],
"deleted": [],
"untracked": ["temp.log"],
"conflicts": [],
"clean": false
}
50% fewer tokens. Zero information lost. Fully typed. Savings scale with output verbosity — test runners and build logs see 80–92% reduction.
Available Servers (28 packages, 240 tools)
Install only the servers relevant to your stack — most projects need just 2–4. The full catalog covers a wide range of ecosystems so Pare works wherever you do.
| Category | Servers | Tools | Wraps |
|---|---|---|---|
| Version Control | git, github | 55 | git, gh |
| Languages & Packages | npm, python, cargo, go, deno, bun, nix, dotnet, ruby, swift, jvm | 101 | npm, pip, cargo, go, deno, bun, nix, dotnet, gem, swift, gradle, maven |
| Build, Lint & Test | build, lint, test, cmake, bazel | 23 | tsc, esbuild, vite, webpack, eslint, prettier, biome, vitest, pytest, jest |
| Infrastructure | docker, k8s, infra, security, remote | 40 | docker, kubectl, helm, terraform, ansible, trivy, ssh |
| Utilities | search, http, make, process, db | 21 | ripgrep, fd, curl, make, just, psql, mysql, redis, mongosh |
Tool Schemas — detailed response examples and field descriptions for every tool. See also Tool Response Examples for quick JSON samples.
Quick Setup
# 1. Configure MCP servers (non-interactive)
npx @paretools/init --client claude-code --preset web
# 2. Add agent rules to your project
# (append to existing CLAUDE.md, or copy if new)
cat node_modules/@paretools/init/rules/CLAUDE.md >> CLAUDE.md
# 3. Restart your client session
# 4. Validate
npx @paretools/init doctor
Available presets: web, python, rust, go, jvm, dotnet, ruby, swift, mobile, devops, full
Setup Guides by Client
| Claude Code | Claude Desktop | Cursor |
| VS Code / Copilot | Windsurf | Cline / Roo Code |
| OpenAI Codex | Gemini CLI | Zed |
| Continue.dev |
Full Quickstart Guide — presets, ecosystem mapping, validation
Manual Configuration — config paths and formats for all clients
Agent Integration Guide — rule files, hooks, CLI-to-MCP mapping
Configuration
Tool Selection
By default, every Pare server registers all of its tools. If a server exposes tools you don't need — or you want to limit which tools are available to an agent — you can filter them with environment variables.
Per-server filter — restrict a single server's tools:
# Only register status and log in the git server
PARE_GIT_TOOLS=status,log npx @paretools/git
Universal filter — restrict tools across all servers:
# Only register these specific tools across any server
PARE_TOOLS=git:status,git:log,npm:install npx @paretools/git
Disable all tools — set the env var to an empty string:
PARE_GIT_TOOLS= npx @paretools/git # no tools registered
| Env Var | Scope | Format | Example |
|---|---|---|---|
PARE_TOOLS |
All servers | server:tool,... |
git:status,npm:install |
PARE_{SERVER}_TOOLS |
One server | tool,... |
status,log,diff |
Rules:
- No env var = all tools enabled (default)
PARE_TOOLS(universal) takes precedence over per-server vars- Server names use uppercase with hyphens replaced by underscores (e.g.,
PARE_MY_SERVER_TOOLS) - Whitespace around commas is ignored
Common patterns:
# Read-only git (no push, commit, add, checkout)
PARE_GIT_TOOLS=status,log,diff,branch,show
# Minimal npm
PARE_NPM_TOOLS=install,test,run
# Only specific tools across all servers
PARE_TOOLS=git:status,git:diff,npm:install,test:run
In JSON MCP config, set via the env key:
{
"mcpServers": {
"pare-git": {
"command": "npx",
"args": ["-y", "@paretools/git"],
"env": {
"PARE_GIT_TOOLS": "status,log,diff,show"
}
}
}
}
Troubleshooting
| Issue | Solution |
|---|---|
npx not found / ENOENT on Windows |
Use cmd /c npx wrapper (see your client's setup guide) |
| Slow first start | Run npx -y @paretools/git once to cache, or install globally: npm i -g @paretools/git |
| Node.js version error | Pare requires Node.js >= 20 |
| NVM/fnm PATH issues | Use absolute path to npx: e.g., ~/.nvm/versions/node/v22/bin/npx |
| MCP connection timeout | Set MCP_TIMEOUT=30000 for Claude Code, or increase initTimeout in client config |
| Too many tools filling context | Use tool selection env vars to limit tools, or only install the servers you need |
Contributing
Each server is a self-contained package. See CONTRIBUTING.md for the full guide.
License
Pare GitHub MCP questions
How do I add Pare GitHub MCP to Claude Code?
Run claude mcp add pare-github -- npx -y @paretools/github in your terminal. Add --scope user to make it available in every project.
How do I add Pare GitHub MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Pare GitHub MCP provide?
It exposes 15 tools, including pr-view, pr-list, pr-create, pr-merge, pr-comment.
What tools does the GitHub server wrap?
The version control category includes git and github servers that wrap git and gh.
Can I limit which GitHub tools are registered?
Yes, you can filter tools per server with an environment variable such as PARE_GITHUB_TOOLS, or across all servers with PARE_TOOLS.
How does the server return output to agents?
Each tool returns human-readable content plus typed, schema-validated structuredContent using MCP outputSchema.
How do I install and configure the servers?
Use the init CLI with a client and preset, add the agent rules, then restart your client session and validate with doctor.