All integrationsGet an API key
GitHub
Issues, pull requests, repositories, actions and code search across your GitHub teams.
Developer
How an agent reaches it
MCPREST APICLI
How you authenticate
OAuth
API key
- Open GitHub, then Settings, then Developer settings, then Personal access tokens, then Fine-grained tokens.
- Generate a token granting the repository and organisation access you want the agent to have (Contents, Issues, Pull requests).
- Paste it below. It is encrypted at rest and never shown to the model.
Connection details
- Base URL
- https://api.github.com
- Pagination
- link_header
- Rate limit
- 5000 requests/hour authenticated. Check X-RateLimit-Remaining.
- MCP server
- https://api.githubcopilot.com/mcp/
Common endpoints
| who am I | GET /user |
| list my repos | GET /user/repos?per_page=100 |
| list issues | GET /repos/{owner}/{repo}/issues |
| create issue | POST /repos/{owner}/{repo}/issues |
| list pull requests | GET /repos/{owner}/{repo}/pulls |
| create pull request | POST /repos/{owner}/{repo}/pulls |
| read a file | GET /repos/{owner}/{repo}/contents/{path} |
| list workflow runs | GET /repos/{owner}/{repo}/actions/runs |
| search code | GET /search/code?q={query} |
Worth knowing
- Search endpoints have their own much lower limit (30/min) and a separate response envelope with `items`.
- A 404 on a repository you believe exists usually means the token lacks access, not that the repo is missing. GitHub hides private resources behind 404.
- Fine-grained tokens are per-repository. A token that works for one repo will 403 on another in the same org.