Github
Pull GitHub pull requests, issues, repository metadata, and code search into agent workflows from one MCP server.
Overview
io.github.davidweb3-ctrl/github is a MCP server for the Build phase that connects your agent to GitHub to list PRs and issues, read repo info, and search code.
What is this MCP server?
- Lists pull requests and issues from GitHub via MCP tools
- Repository information and code search for agent-driven navigation
- stdio npm package @davidweb3-ctrl/mcp-github-server (v1.0.0)
- Requires GITHUB_TOKEN personal access token for authenticated API calls
- Server schema version 1.0.0
- npm identifier @davidweb3-ctrl/mcp-github-server
- Required env: GITHUB_TOKEN
What problem does it solve?
Jumping between GitHub tabs to list PRs, issues, and search code wastes time when your agent could fetch the same facts in one turn.
Who is it for?
Indie developers who live in GitHub for issues and PRs and want Cursor or Claude Code to summarize or search the repo without custom scripts.
Skip if: Pure local-only workflows with no GitHub remote, or teams needing enterprise audit features beyond a PAT-based MCP wrapper.
What do I get? / Deliverables
Once connected with a PAT, your agent can query live GitHub repository data so planning, review, and fix loops stay aligned with the remote source of truth.
- Live PR and issue lists inside agent conversations
- Repo metadata and code search results without leaving the IDE
- Faster integration and release prep against GitHub truth
Recommended MCP Servers
Journey fit
Builders wire GitHub early while integrating repos, automating issue triage, and keeping shipping cadence—integrations is the primary journey shelf for hosted SCM. Integrations covers third-party API bridges; GitHub PR/issue/search access is the classic connect-your-repo step during Build and ongoing Ship prep.
How it compares
GitHub REST MCP for PRs, issues, and search—not a local git-enhanced commit review server.
Common Questions / FAQ
Who is io.github.davidweb3-ctrl/github for?
Solo builders and small teams on GitHub who want MCP-backed access to PRs, issues, repo metadata, and code search from their AI coding agent.
When should I use io.github.davidweb3-ctrl/github?
Use it while building integrations, triaging issues, or preparing releases whenever the agent needs current GitHub state instead of manual copy-paste.
How do I add io.github.davidweb3-ctrl/github to my agent?
Install @davidweb3-ctrl/mcp-github-server as stdio MCP, set GITHUB_TOKEN to a fine-grained or classic PAT with appropriate repo scopes, and restart the client.