Best for
- Development teams that need AI assistants to operate GitHub
- Users who want to handle repository collaboration tasks through natural language
- Deployers able to manage GitHub access tokens securely
G
GitHub
Official
Connect AI assistants to GitHub through natural language.
GitHub source repository ↗
41FMRS · D
The source clearly identifies this server as a GitHub integration for repositories, issues, pull requests, and workflows, with stdio and streamable HTTP transports. It does not enumerate tool identifiers, client compatibility, or detailed token permissions, so those fields are not inferred.
The GitHub MCP Server lets AI assistants manage GitHub repositories, issues, pull requests, and workflows through natural language. The server is provided by the GitHub upstream project and supports local containerized stdio execution and remote streamable HTTP access.
Tools
The tool list has not been reviewed yet.
Setup
stdio: run the OCI image ghcr.io/github/github-mcp-server:${VERSION} and set the required GITHUB_PERSONAL_ACCESS_TOKEN environment variable. Remote: connect to https://api.githubcopilot.com/mcp/ and provide an Authorization header. The source does not provide a client-specific configuration example.
Fit and risk
Not for
- Users who do not need GitHub integration
- Deployment environments that cannot provide a GitHub PAT or App token
- Use cases requiring specific tools or permissions not documented in the source
Required permissions
- Requires a GitHub Personal Access Token or App token
- stdio deployments must set GITHUB_PERSONAL_ACCESS_TOKEN
- Remote connections require an authentication token in the Authorization header
- The actual token permissions depend on the PAT or App token used
Risks and side effects
- Access tokens are secrets and should not be exposed
- Repository, issue, pull request, and workflow operations may change GitHub data or project state
- Overly broad token permissions may expand the actions available to the AI assistant
- Misinterpreted natural-language requests may cause unintended GitHub operations
Troubleshooting
- Verify that GITHUB_PERSONAL_ACCESS_TOKEN is set and valid
- For remote access, check that the Authorization header is present and uses the correct token
- Confirm that the token has the permissions required for the intended GitHub operation
- Check that the OCI image version variable has been replaced correctly
- Confirm that the client supports the selected stdio or streamable HTTP connection
Use cases
Manage GitHub repositories through natural language
Handle GitHub issues and pull requests
Manage GitHub workflows
Connect GitHub operations to an AI assistant
Supported clients
Supported clients have not been confirmed yet.