Best for
- Developers, DevOps engineers
- Users of AI coding tools like Claude, Cursor
- Scenarios needing reliable structured GitHub data
P
Pare Github
Community
Pare GitHub - Structured GitHub operations (PRs, issues, actions) as typed JSON.
- Category
- Dev Tools #408 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js 20+
- Credentials
- No credential needed
- License
- MIT
- Last commit
31FMRS · D
This server provides structured JSON output for GitHub operations, reducing token usage and suitable for AI agents. However, attention to auth security and write operation risks is required.
Strongest · Setup experience 8/20 Weakest · Reliability 5/20
Why each score
- Reliability 5/20
- Only the manifest at packages/server-github/server.json and the repo-level README were reviewed; sibling server tools/tests were not attributed. The manifest is well-formed and internally consistent (name, version, stdio transport), and the README describes structured GitHub PR/issues/actions output, making the happy path plausible. However, no source, tests, or CI workflow for this server were supplied, so initialization handshake, tool-list accuracy, error handling, and dependency controllability cannot be verified. Heavily deducted under static calibration.
- Security and permissions 5/20
- No red-line issues such as malware, credential theft, covert exfiltration, or destructive defaults without confirmation are evident. The generic PARE_TOOLS / PARE_GITHUB_TOOLS filtering can support least-privilege tool exposure, which is positive. But there is no GitHub token authentication guide, token scope guidance, data-boundary/network disclosure, or documented confirmation for dangerous operations like merge/delete. Risk visibility is incomplete, so the score is low.
- Maintenance 8/20
- MIT license is explicit, the repository is not archived, and the manifest is versioned at 0.22.0, indicating versioned releases; 17 open issues suggest community feedback. However, commit history, release dates, dependency-update cadence, and a security-response channel are absent from the supplied material, and the README's CI/Codecov/OpenSSF badges cannot be independently verified. The score reflects moderate rather than strong governance.
- Documentation 5/20
- The README provides project-level quickstart, multi-client setup links, tool-filtering explanations, and troubleshooting, but these are generic to the whole repository. For the GitHub server specifically, tool parameters, authentication method, token scopes, rate-limit/cost information, and response examples are missing. Users must assume pre-configured gh/token, which is a significant documentation gap.
- Setup experience 8/20
- The manifest provides the npm package @paretools/github and stdio transport, so an npx launch path is inferable; the README states Node.js >=20 and links client-specific setup guides. But there is no GitHub-server-specific MCP JSON configuration example and no authentication preparation step (e.g., GH_TOKEN environment variable). Platform compatibility and troubleshooting are generic, and no reviewable CI/test execution evidence was supplied, making setup manual and fragile.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessUses the network
Not for
- Users needing full GitHub functionality (e.g., code search, advanced admin)
- Those preferring simpler tools in low-token environments
Required permissions
- Requires GitHub API authentication (e.g., token)
- Involves reading repository, PR, issue data
- May include write operations (e.g., creating PRs, commenting) depending on configuration
Risks and side effects
- Potential unauthorized access if credentials are leaked
- Accidental modifications to repositories due to misuse of write operations
- Dependency on GitHub API rate limits
Setup
Before you start
Runtime：Node.js 20+
Other optional settings (1)
PARE_TOOLS
Optional universal filter across all Pare servers in server:tool,... format (e.g. github:prs); takes precedence over per-server variables.
Install the @paretools/github package via npm. Configure your MCP client to use stdio transport with npx -y @paretools/github. Requires Node.js >= 20.
Check that it works
The pare-github server's tools should appear in your client's tool list after startup; you can also run npx @paretools/init doctor to validate the connection.
Troubleshooting
- Check Node.js version is >= 20
- Verify GitHub authentication token is correctly configured
- Test connectivity by running `npx -y @paretools/github`
- Inspect client logs or increase timeout with `MCP_TIMEOUT`
Things to try
Once connected, you can ask your AI assistant things like:
- List all open pull requests in this repo with their status
- Show the open issues in this repository, sorted by creation date
- Trigger the GitHub Actions workflow and report the result
- Close issue #42 and add a comment explaining why
Use cases
Interacting with GitHub repositories: viewing PRs, issues, workflow runs
Automating code review or CI/CD processes
Fetching repository metadata, branch information from agents
Overview
Pare GitHub is part of the Pare project, optimized for AI agents. It wraps the GitHub CLI (gh) and returns schema-validated JSON instead of raw terminal text, ensuring consistent output across platforms and versions while 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