Using Cursor + GitHub MCP to Fix Issues with Just a Number
Cursor + GitHub MCP: add the GitHub server in Cursor settings, drop in a PAT with repo scope, then just reference an issue number with org/repo. Cursor fetches the details, so I can summarize and fix without pasting issue text.
I used to paste entire GitHub issue bodies into Cursor so AI could fix them. After testing the GitHub MCP integration, I realized I only need the issue number—Cursor can fetch the issue details directly via MCP.
Quick Setup
- Install and enable the GitHub MCP in Cursor following the guide: https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-cursor.md
- In Cursor settings (Settings → Tools & MCP → Model Context Protocol), add/edit the GitHub server and paste a GitHub PAT with
reposcope; no extra sign-in flow is needed. JSON config (~/.cursor/mcp.jsonor project.cursor/mcp.json) also works if you prefer. - Reload Cursor and confirm the GitHub MCP server shows up (green dot) in MCP tools.
How I Use It Now
- In a new chat, I just type something like: “Fix issue 1234 in org/repo” or “Summarize issue 1234 in org/repo.”
- Cursor asks GitHub MCP for the issue details, so I don’t copy/paste anything.
- I iterate on the fix right in the same thread, using the MCP context as the source of truth.
Tips
- Keep the issue number handy plus the org/repo; you don’t need the pasted text.
- If the bot can’t fetch, re-check GitHub auth and that the issue belongs to a repo you can access.
- For pull requests, the same pattern works—reference the PR number and let MCP pull the details.