MCP Servers

GitHub
GADevelopment platform for version control, collaboration, and CI/CD workflows.
MCP ServersDeveloper ToolsVersion ControlCI/CD
How it works
Every agent request passes through Ferentin policy before it reaches GitHub.- AI agentAsks for something
- Ferentin policies
- Audit logging
- Fine grained permissions
- Secret scanning
- GitHub MCP serverAuthorized connection
- Governed resultMasked, logged, returned
What you can do with GitHub
Discover
Search and browse what exists, without opening the content itself.
33 tools
Access
Read content and metadata, subject to masking policy.
25 tools
Manage
Create, update, organise and remove items.
21 tools
Collaborate
Comment, share and coordinate with people.
6 tools
Technical capabilities92 tools
Discover
- List GitHub Actions workflows in a repository
- GitHub Support Docs Search
- List branches
- List code scanning alerts
- List commits
- List Copilot Spaces
- List dependabot alerts
- List discussion categories
- List discussions
- List Gists
- List global security advisories
- List issue fields
- List available issue types
- List issues
- List labels from a repository
- List notifications
- List org repository security advisories
- List pull requests
- List releases
- List repository security advisories
- List secret scanning alerts
- List starred repositories
- List tags
- List GitHub Projects resources
- Search code
- Search commits
- Search issues
- Search organizations
- Search pull requests
- Search repositories
- Search users
- Semantic Issue Similarity Search
- Semantic Issues Search
Access
- Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts)
- Check Dependency Vulnerabilities
- Get code scanning alert
- Get commit details
- Get Copilot Space
- Get dependabot alert
- Get discussion
- Get file or directory contents
- Get Gist Content
- Get a global security advisory
- Get GitHub Actions workflow job logs
- Get a specific label from a repository
- Get latest release
- Get my user profile
- Get notification details
- Get a release by tag name
- Get repository tree
- Get secret scanning alert
- Get tag details
- Get team members
- Get teams
- Get issue details
- Mark all notifications as read
- Get details of GitHub Projects resources
- Get details for a single pull request
Manage
- Trigger GitHub Actions workflow actions
- assign_copilot_to_issue
- Create branch
- Create Gist
- Create or update file
- Open new pull request
- create_pull_request_with_copilot
- Create repository
- Delete file
- Create or update issue/pull request
- Write operations on repository labels
- Manage notification subscription
- Manage repository notification subscription
- Merge pull request
- Manage GitHub Projects
- Write operations (create, submit, delete) on pull request reviews
- Run Secret Scanning
- Change sub-issue
- Update Gist
- Edit pull request
- Update pull request branch
Collaborate
- Add review comment to the requester's latest pending pull request review
- Add comment to issue or pull request
- Add reply to pull request comment
- Manage discussion comments
- Get discussion comments
- List repository collaborators
Other
- Dismiss notification
- Fork repository
- Push files to repository
- Request Copilot review
- Star repository
- Triage Issue
- Unstar repository
Overview
GitHub is the world's leading software development platform, offering Git-based version control, code review, project management, and CI/CD through GitHub Actions.
Ferentin integration
GitHub MCP Server enables AI agents to interact with repositories, issues, pull requests, and code through secure OAuth authentication with fine-grained permission controls.
Frequently asked about GitHub
- What can AI agents do with GitHub through Ferentin?
- Ferentin exposes 92 GitHub MCP tools to your AI agents, grouped as Discover (33 tools), Access (25 tools), Manage (21 tools) and Collaborate (6 tools). Every call is checked against your Ferentin policies before it reaches GitHub.
- How does Ferentin secure GitHub access?
- Requests through the GitHub integration are covered by audit logging, fine grained permissions and secret scanning. These controls are applied by Ferentin, not by GitHub, so they hold across every connected agent.
- What permissions does the GitHub integration require?
- The GitHub integration requests 6 OAuth 2.0 scopes: repo; read:org (read access); read:user (read access); user:email; read:project (read access); workflow
- How do I connect GitHub to Ferentin?
- Open the Ferentin admin console, add GitHub as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
- Is the GitHub integration generally available?
- Yes. The GitHub integration is generally available on Ferentin, including the free tier.
