github-mcp

The core problem repogate tackles is giving coding agents direct, in-conversation access to GitHub. Before, agents could only output suggestions or generate curl commands, and closing an Issue, merging a PR, or posting a line-level review comment still required the developer to switch back to a terminal. repogate wraps the GitHub REST API into 23 standard MCP tools spanning repo queries, full Issue lifecycle management, PR creation and merging, code review, multi-type search, and account authentication, so a single natural-language request can drive a complete operation chain through the agent.\n\nA few engineering details deserve attention. The project has zero runtime dependencies, relying solely on Node.js built-ins such as fetch and node:test, so no npm packages are needed to start. Authentication supports both personal access tokens and the OAuth device authorization flow with local token caching, and OAuth completion takes effect immediately without a process restart. List and search tools return concise summaries instead of raw JSON, preserving context tokens for the model. Every error response includes a fix guide covering common scenarios such as 401, rate limits, parameter validation, and permission issues. A one-switch read-only mode intercepts all eight write operations and returns a clear message explaining how to disable it, making it ideal for research-only sessions.\n\nIt is well suited for developers who use coding agents in MCP-capable clients like dsh, Claude Code, Codex, or opencode, especially contributors who want agents to manage Issues and PRs on their behalf without hand-writing API calls, and researchers who prefer agents to browse repositories in read-only mode to assist with code review.