GitHub Projects MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub Personal Access Token (classic or fine-grained) for authentication | |
| GITHUB_APP_ID | No | GitHub App ID for GitHub App authentication | |
| GITHUB_APP_PRIVATE_KEY | No | Private key for GitHub App authentication | |
| GITHUB_APP_INSTALLATION_ID | No | Installation ID for GitHub App authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List GitHub Projects V2 for a user or organization |
| get_projectB | Get detailed information about a specific GitHub Project V2 |
| create_projectC | Create a new GitHub Project V2 |
| update_projectB | Update a GitHub Project V2 (title, description, readme, visibility, or closed status) |
| delete_projectB | Delete a GitHub Project V2 |
| list_project_itemsB | List all items (issues, pull requests, draft issues) in a GitHub Project V2 |
| get_project_itemB | Get detailed information about a specific item in a GitHub Project V2 |
| add_draft_issueB | Add a new draft issue to a GitHub Project V2 |
| add_existing_issueB | Add an existing issue or pull request to a GitHub Project V2 |
| update_item_fieldB | Update a field value on an item in a GitHub Project V2 |
| remove_project_itemB | Remove an item from a GitHub Project V2 |
| list_project_fieldsB | List all fields in a GitHub Project V2 |
| create_fieldB | Create a new custom field in a GitHub Project V2 |
| update_fieldC | Update a field in a GitHub Project V2 |
| delete_fieldB | Delete a custom field from a GitHub Project V2 |
| list_project_viewsB | List all views in a GitHub Project V2 |
| get_project_viewB | Get detailed information about a specific view in a GitHub Project V2 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct resource or action within GitHub Projects V2, with clear boundaries. For example, adding draft issues and adding existing issues are clearly differentiated by description, and all other tools have unique purposes.
All tools follow a consistent verb_noun pattern in snake_case, such as create_project, list_project_items, and update_item_field. The use of 'add' for issues vs 'create' for fields and projects is a minor convention shift but still logically consistent.
17 tools is appropriate for a comprehensive GitHub Projects V2 management server. The tool count covers all major CRUD operations for projects, fields, items, and views without being excessive.
The tool set covers most important workflows: creating, reading, updating, and deleting projects, fields, and items. However, it lacks tools for creating, updating, or deleting views, and there is no dedicated tool to get a specific field by ID (only list). These are minor gaps but do not severely hinder core functionality.