GitHub Projects MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_APP_ID | Yes | The GitHub App ID used to authenticate with GitHub Projects v2. | |
| GITHUB_APP_PRIVATE_KEY | Yes | The GitHub App private key used to mint an installation token at runtime. | |
| GITHUB_INSTALLATION_ID | Yes | The GitHub App installation ID used to mint an installation token at runtime. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsC | List visible GitHub Projects v2 for an organization. |
| get_projectC | Read one visible GitHub Project v2 and its fields. |
| list_project_itemsC | List visible Project v2 items, content and field values. |
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 3 tools
Each tool targets a distinct level: list_projects (org collection), get_project (single project with fields), and list_project_items (items within a project). The boundaries are clear from the descriptions, though list_projects vs get_project could momentarily blur since both concern projects.
All three tools follow a consistent list_/get_ verb_noun snake_case convention. The pattern is predictable and immediately readable.
Three tools is thin for a Projects domain, and the surface is entirely read-only. It is coherent for a minimal read scope, but feels under-scoped for a server named 'GitHub Projects MCP'.
List and read operations are covered at the organization, project, and item levels, giving a reasonable read surface. However, no create/update/delete operations exist for projects, items, or field values, leaving write workflows unserved.