GitHub MCP for AI. Track issues, code, and PRs without leaving your agent.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
GitHub MCP lets your AI agent manage all development workflows directly from conversation. You can list repositories, check project issues, search file contents across repos, and monitor pull requests without opening a browser tab.
It gives you full control over source code management, user profiles, organization details, and CI/CD status.
What your AI can do
Create new issue
Opens a new issue directly into any specified GitHub repository.
Get file content
Reads the raw content of a specific file from a repository for analysis.
Get my profile
Retrieves detailed information about your personal GitHub account profile.
List your repositories and retrieve key details like star counts, languages, and overall structure.
View open issues for a given project or monitor recent notifications to see team-wide development activity.
Search through repo contents programmatically, find specific logic, and pull raw file contents for immediate analysis.
List all open pull requests to track code reviews and monitor team-wide merges.
Access details about your account, organization memberships, or list private code snippets (Gists).
Ask an AI about this
Waiting for input…
GitHub: 12 Development Tools Available
Use these tools to manage everything in your source control workflow—from listing user details to creating new project tickets.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using GitHub on VinkiusCreate New Issue
Opens a new issue directly into any specified GitHub repository.
Get File Content
Reads the raw content of a specific file from a repository for analysis.
Get My Profile
Retrieves detailed information about your personal GitHub account profile.
Get Repository Details
Gets general metadata and statistics for a specific repository.
List Repo Branches
Lists all existing branches within a repository.
List My Gists
Lists your private, public, or organization code snippets (Gists).
List Repository Issues
Retrieves a list of open and closed issues for a specific project.
List Recent Notifications
Checks the GitHub notification inbox for recent activity alerts.
List My Organizations
Retrieves a list of all user organizations you belong to.
List Pull Requests
Fetches a list of pull requests within a designated repository.
List My Repositories
Lists every repository associated with your account.
Search Repositories
Searches across GitHub to find projects based on criteria like name or description.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with GitHub, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GitHub. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Juggling browser tabs to track code status is exhausting.
Today, tracking development progress means opening GitHub in the browser. You jump from the repository main page to check the list of branches, then open a separate tab for the issue tracker to see if that branch's feature has been assigned a ticket number. Then you have to open another tab just to look at the pull requests to confirm who is reviewing it.
With this MCP, those manual steps vanish. You simply tell your agent: 'Check the status of the last three PRs for the auth service and list any related issues.' You get an immediate summary of all that data without leaving your chat window.
The GitHub MCP gives you conversational control over code intelligence.
You no longer have to manually download files or copy long diffs just to figure out which function needs fixing. You can ask the agent, 'What does the `user` model look like in the API?' and it uses `get_file_content` to pull the exact code block you need.
This changes everything. Instead of treating GitHub as a collection of siloed pages, you treat it like one single knowledge base, accessible via conversation.
What your AI can actually do with this
Your agent takes over your source control dashboard. Instead of toggling between tabs—checking the issue tracker here, then jumping to the repo list there, and finally opening a file just to see what changed—you talk to it. Your AI client handles the entire workflow. It tracks which repositories belong to whom, finds specific code snippets deep within multiple files, and monitors every open pull request for review status.
This means you maintain momentum on complex projects without ever leaving your chat environment. By connecting this MCP through Vinkius, you give any compatible agent access to GitHub's full operational depth. You can even programmatically create new issues when a bug pops up or list all the Gists used by a team member.
019dd0fa-eea3-73c1-83aa-240e5018a85b Here's how it actually works
The bottom line is, it turns complex GitHub dashboard navigation into simple conversational commands.
First, subscribe to this MCP and generate a Personal Access Token (PAT) from GitHub. Make sure the token has read/write scopes for repos and users.
Next, give that PAT to your AI client or agent within Vinkius's environment. This authorizes the connection.
Finally, tell your agent what you need—for example, 'List all my repositories with their star counts.' The MCP then executes the necessary API calls.
Who is this actually for?
This is for anyone who spends time in Git. If you're tired of switching between the issue tracker, the main repo page, and your local terminal just to get an overview, this MCP saves hours of context switching.
Retrieves file contents using natural language search or lists all open issues for a feature branch without leaving their chat window.
Monitors repository activity and pulls requests to triage team bottlenecks, keeping an eye on who needs to review code.
Automates the discovery of required repositories across multiple organizations and checks recent notifications for deployment status updates.
What Changes When You Connect
Find code snippets instantly. Instead of navigating folders to find a specific function, ask the agent to use get_file_content across repos. It pulls the raw text you need immediately.
Streamline issue tracking. Don't manually check dashboards; tell your agent to run list_repository_issues for project status updates or create_new_issue when a bug is found.
Monitor team progress effortlessly. Your agent can run list_pull_requests, giving you an instant overview of code reviews and merge readiness without leaving the chat.
Know your whole scope. Need to see all projects? Use list_my_repositories or search_repositories. It gives you a full map of your GitHub presence in one query.
Stay updated on team actions. Instead of reading dozens of emails, asking for list_recent_notifications provides an aggregated view of what matters right now.
See it in action
Debugging a forgotten dependency
A developer needs to find the exact usage of a function defined last quarter. They ask their agent, and it uses get_file_content across several repos, pulling the relevant code block immediately for review.
Triage after a release
A team lead wants to know the health of the main service. They instruct their agent to run list_repository_issues and then list_pull_requests on that repo, quickly identifying all open bugs and PRs needing review.
Onboarding a new contributor
A manager needs to give the new hire an overview of existing work. They ask their agent to list_my_repositories and then get_repository_details for the top three, providing immediate context.
Escalating a critical bug
An engineer spots a major flaw in testing. Rather than navigating the UI, they ask their agent to run create_new_issue, automatically logging all necessary details and assigning it to the right team.
The honest tradeoffs
Asking for 'all project data'
Telling your AI client, 'Give me everything about the project.' This is vague and forces the agent to guess which tools to use.
Be specific. Instead of general requests, ask the agent to list_repository_issues for the repo name OR tell it to run both list_my_repositories AND list_pull_requests for a single target.
Forgetting PAT scopes
Connecting your account but forgetting to grant 'write' scope. The agent will fail when trying to execute create_new_issue because of permission denial.
Before connecting, verify that your Personal Access Token (PAT) has the necessary write and read permissions for repos, users, and notifications.
Searching only by keyword
Manually searching GitHub's web UI is slow. You might miss context because you only searched a single repository.
Use the agent to run search_repositories or combine it with get_repository_details for an enterprise-wide view, making sure your search covers all relevant projects.
When It Fits, When It Doesn't
Use this MCP if your workflow requires constant cross-referencing between code, issues, and PRs. You need the ability to transition from 'I found a bug' (using list_repository_issues) directly to 'Here is the file content I suspect caused it' (using get_file_content), all without opening three separate tabs. Don't use this if you only need basic API access—a dedicated CLI tool might be faster for simple tasks like listing branches. However, if your pain point is context switching between multiple tools and dashboards, this MCP is the right call. If you are only doing single-task operations (like just managing user profiles), check if a specialized, smaller MCP exists first.
Questions you might have
How do I check all my repos using the list_my_repositories tool? +
You tell your agent to run list_my_repositories. This returns a full catalog of every repo you own, allowing you to select targets for deeper analysis.
Can I use get_file_content on old code? +
Yes. You specify the repository and file path, and get_file_content retrieves the raw contents regardless of how long ago it was committed.
Is list_pull_requests better than checking the UI? +
It's faster. The agent runs list_pull_requests and summarizes the status, providing a structured answer immediately without you having to click through multiple review threads.
What if I need to create an issue before connecting? +
You can't pre-connect. Once connected, just tell your agent to use create_new_issue and provide the title and body details for the ticket you need.
If I use list_recent_notifications, what happens if my Personal Access Token (PAT) is missing the 'user' scope? +
The tool will fail and return an authorization error. You must ensure your PAT has the necessary scopes, including 'user' and 'repo', for any action that requires accessing specific account or project data.
If I run list_my_repositories repeatedly in a short time, am I at risk of hitting rate limits? +
Yes. All external API calls are subject to GitHub's rate limits. If you make too many requests quickly, your AI client will receive an error until the limit resets. It’s best practice to batch related queries.
When should I use search_repositories compared to get_repository_details? +
Use search_repositories when you need a broad overview of projects across GitHub. Use get_repository_details only when you already know the exact repository name and need specific, deep metadata about it.
Does list_repo_branches show all active development branches or just the default ones? +
It lists all available branches within a given repository. You can use this to check out feature branches or verify if an experimental branch exists before running further commands.
Can I read private repositories? +
Yes, provided your Personal Access Token (PAT) has the 'repo' scope or appropriate fine-grained permissions for those repositories.
How do I find a repository owner and name? +
In a GitHub URL like github.com/vinkius/mcp-server, the owner is vinkius and the repository name is mcp-server.
Does it support creating pull requests? +
This version supports listing pull requests and issues. PR creation is currently handled through the web interface or other specialized tools.
We've already built the connector for GitHub. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.