github -review-tools

This MCP server exposes a set of tools for interacting with GitHub pull requests and their reviews. The tools include getting a specific pull request review or comment, replying to a comment, resolving a review thread, checking if all threads are resolved, and retrieving threads for a pull request in both granular and aggregated forms. Each tool accepts a schema-driven input tailored to the GitHub pull request review data model, ensuring you pass the required identifiers (such as PR number, review ID, thread ID, etc.) to perform the operation. You can call these tools in sequence to automate workflows like validating review statuses before merging, replying to comments with guidance, or collecting all threads for reporting and analytics.

To use a tool, first ensure your MCP server is running and accessible to your MCP client. Then invoke the desired operation by providing the corresponding input payload that matches the tool’s input schema. The server will respond with data fetched from GitHub or the result of the mutation (e.g., a newly created reply). You can chain tools to perform complex checks—e.g., fetch a review, check if all threads are resolved, and then mark the review as resolved if needed.

Prerequisites:\n- Node.js (and npm/yarn) installed on your machine or a server\n- Access to the repository containing the MCP server code (github-server-only)\n\n1) Install dependencies:\nbash\nyarn install\n\n\n2) Build the server (if using a build step):\nbash\nyarn build\n\n\n3) Run the server locally (example):\nbash\nyarn start\n\n\n4) Install as an MCP server in your configuration (example provided in the repository):\njson\n{\n "mcpServers": {\n "github-pr-review-tools": {\n "command": "node",\n "args": ["~/Code/github-server-only/dist/index.js"],\n "env": {\n "GITHUB_PERSONAL_ACCESS_TOKEN": "<your token here>"\n }\n }\n }\n}\n\n\nNotes:\n- Adjust the path to dist/index.js to point to your built server entry.\n- Ensure you provide a valid GitHub Personal Access Token with appropriate scopes for PR reviews.\n- If you prefer running via Docker, you can containerize the server using the Dockerfile in src/github/Dockerfile (as noted in the Docker build section).

Tips and common issues:\n- Ensure the GITHUB_PERSONAL_ACCESS_TOKEN has the necessary scopes (e.g., repo, read:org) for PR and review actions.\n- If you modify input schemas, keep them in sync with the server’s internal validation to avoid payload rejections.\n- When running in CI, store the token securely as an environment variable referenced by your MCP client.\n- The server provides a quota-limited GitHub API; for high-frequency automation, respect rate limits and implement backoff handling in your client.\n- If you switch from Yarn to npm, ensure build/start scripts are compatible with your package manager.\n- Docker users can build the image with the provided docker build command, then run it and expose the necessary port for MCP communication.