Bring Source Control
to Cursor
Learn how to connect GitHub to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the GitHub MCP Server?
Connect your GitHub account to any AI agent and take full control of your source control and development workflows through natural conversation.
What you can do
- Repository Orchestration — List and manage your repositories programmatically, including retrieving star counts, languages, and detailed metadata
- Issue Lifecycle — Monitor project status by listing open issues and creating new ones directly through your agent to maintain momentum
- Code Intelligence — Search through repositories and files programmatically to find specific logic and retrieve raw file contents (base64) for analysis
- Collaboration Visibility — Monitor pull requests and recent notifications to stay updated on team-wide development activity and code reviews
- Resource Management — Access user profiles, organization memberships, and Gists to manage your complete GitHub presence programmatically
How it works
1. Subscribe to this server
2. Retrieve your Personal Access Token (PAT) from GitHub (Settings > Developer Settings > PAT)
3. Ensure your token has the required scopes (repo, user, notifications)
4. Start managing your code and projects from Claude, Cursor, or any MCP client
No more manual toggling between browser tabs to check issue statuses. Your AI acts as your dedicated engineering coordinator.
Who is this for?
- Software Engineers — instantly find code snippets across repositories and retrieve file contents using natural language
- Team Leads — monitor repository activity and triage issues without leaving your communication tools
- DevOps Engineers — automate repository discovery and monitor project notifications through simple AI queries
Built-in capabilities (12)
Open GitHub issue
Read file from repo
Get account info
Get repo info
List code snippets
List user orgs
List your GitHub repos
List repo PRs
Check GitHub inbox
Check repo branches
List repo issues
Find GitHub projects
Why Cursor?
Cursor's Agent mode turns GitHub into an in-editor superpower. Ask Cursor to generate code using live data from GitHub and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
GitHub in Cursor
GitHub and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect GitHub to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for GitHub in Cursor
The GitHub MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
GitHub for Cursor
Every tool call from Cursor to the GitHub MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.