A Model Context Protocol (MCP) server that provides tools for managing GitHub Projects V2 through Claude and other MCP clients. This server uses the
Github Projects MCP becomes available to MCP clients through the github projects mcp mcp server. A Model Context Protocol (MCP) server that provides tools for managing GitHub Projects V2 through Claude and other MCP clients. This server uses the GitHub GraphQL API for interacting with GitHub Projects V2.
A Model Context Protocol (MCP) server that provides tools for managing GitHub Projects V2 through Claude and other MCP clients. This server uses the GitHub GraphQL API for interacting with GitHub Projects V2.
Once connected, the assistant can call these 9 tools directly:
list_projects — List GitHub Projects V2 for a given organization or userget_project_fields — Get fields available in a GitHub Project V2get_project_items — Get items in a GitHub Project V2 (supports filtering bycreate_issue — Create a new GitHub issueadd_issue_to_project — Add an existing GitHub issue to a Project V2update_project_item_field — Update a field value for a project itemcreate_draft_issue — Create a draft issue directly in a GitHub Project V2delete_project_item — Delete an item from a GitHub Project V2Setup — Create a GitHub Personal Access Token and give it the necessary permissions. The required permissionsSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Before the server will start you need to supply one environment variable: GITHUB_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Github Projects MCP sits in that group, and the shape of its toolset — list_projects, get_project_fields, get_project_items among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| list_projects | List GitHub Projects V2 for a given organization or user |
| get_project_fields | Get fields available in a GitHub Project V2 |
| get_project_items | Get items in a GitHub Project V2 (supports filtering by |
| create_issue | Create a new GitHub issue |
| add_issue_to_project | Add an existing GitHub issue to a Project V2 |
| update_project_item_field | Update a field value for a project item |
| create_draft_issue | Create a draft issue directly in a GitHub Project V2 |
| delete_project_item | Delete an item from a GitHub Project V2 |
| Setup | [Create a GitHub Personal Access Token](https://github.com/settings/personal-access-tokens/new) and give it the necessary permissions. The required permissions are: repo, project, and read:org. |
{
"mcpServers": {
"github-projects": {
"command": "uvx",
"args": [
"mcp-github-projects"
],
"env": {
"GITHUB_TOKEN": "your_pat_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.