github-issues-mcp

A zero-dependency MCP server that gives Claude full control over GitHub Issues and Project boards. OAuth 2.0 auth, Streamable HTTP transport, runs anywhere Node.js 18+ runs.

Built for developers who want Claude (Web App, Desktop, or CLI) to manage their GitHub issue boards without installing heavyweight tools or granting broad permissions.

You have a private GitHub repo with issues organized as a project board (kanban). You want Claude — across Web App, Desktop, and CLI — to:

• Read your board: list issues, check statuses, filter by label
• Write to it: create issues, update them, add comments, close them
• Manage the kanban: move items between columns (Todo, In Progress, Done)

The official GitHub MCP connector (via api.githubcopilot.com) requires GitHub App installation with org-level permissions and doesn't reliably access private repos under personal accounts. This server sidesteps all of that — it uses a GitHub Personal Access Token directly. If the token can see the repo, Claude can manage it.

Real-world example: I use this to manage a multi-project roadmap across Claude Web App (for planning conversations) and Claude Code CLI (for implementation sessions). Both Claudes read and write to the same kanban board. Issues are created during planning, moved to "In Progress" during coding, and closed when done — all without leaving the conversation.

• 10 tools: issues (list, get, create, update, comment, labels) + projects (get board, list items, add item, move between columns)
• OAuth 2.0 + PKCE: proper authorization flow with consent screen and admin secret
• GitHub Projects V2: full kanban board management via GraphQL API
• Streamable HTTP: MCP transport that works with Claude Web App custom connectors
• Zero npm dependencies: just Node.js built-ins (http, crypto)
• Self-hosted: runs on your own server, you control the data flow
• ~500 lines: read the whole thing in 1