Mcp Github
Give your agent read-first access to GitHub repos, files, issues, PRs, and code search while you stay in the editor.
Overview
io.github.infoinlet-marketplace/mcp-github is a MCP server for the Build phase that exposes GitHub repos, files, code search, issues, PRs, and commits to agents with read-only as the default mode.
What is this MCP server?
- GitHub surface: repos, file contents, code search, issues, pull requests, and commits
- Read-only default reduces accidental repo mutation by agents
- Stdio MCP via @infoinlet/mcp-github npm package v0.1.1
- Supports tracing PR and issue context without tab-switching
- Pairs with local git MCP when you need remote vs working-tree views
- Documented areas: repos, files, code search, issues, PRs, commits
- npm package @infoinlet/mcp-github version 0.1.1
- Read-only default stated in server description
What problem does it solve?
Copy-pasting GitHub links and screenshots into chat burns time and agents hallucinate issue state when they cannot query the API.
Who is it for?
Solo builders shipping from GitHub who want agent-grounded code search and issue context with conservative default permissions.
Skip if: Workflows that require heavy GitHub Actions orchestration or org-wide admin automation without explicit write scopes.
What do I get? / Deliverables
After registration with a GitHub token, your agent can ground answers in live repo, issue, and PR data from GitHub.
- Agent-queryable GitHub repo, file, search, issue, PR, and commit data
- Reduced context switching between IDE chat and github.com
Recommended MCP Servers
Journey fit
GitHub MCP is shelved under Build integrations because most solo builders wire it while connecting repos, APIs, and agent workflows. Integrations captures remote VCS and platform APIs that extend the agent beyond the local filesystem.
How it compares
Hosted GitHub API MCP bridge, not local-only git inspection or a code-review methodology skill.
Common Questions / FAQ
Who is io.github.infoinlet-marketplace/mcp-github for?
Developers using AI agents on GitHub-hosted SaaS, APIs, or open-source repos who need API-backed context during build and triage.
When should I use io.github.infoinlet-marketplace/mcp-github?
Use it when implementing against remote repos, researching existing issues and PRs, or searching code across GitHub without leaving the agent session.
How do I add io.github.infoinlet-marketplace/mcp-github to my agent?
Install @infoinlet/mcp-github, configure stdio MCP in your client, and supply a GitHub personal access token or compatible credential per your security model.