mcp-github-pm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with repo scope |
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 |
|---|---|
| create_issueC | Create a GitHub issue with optional labels, assignees, and milestone. |
| list_issuesB | List issues with filters for state, labels, assignee, and sorting. |
| update_issueA | Update an existing issue's title, body, state, labels, or assignees. |
| create_milestoneC | Create a milestone for tracking issue groups. |
| list_milestonesC | List milestones for a repository. |
| get_repo_statsA | Get repository overview: stars, forks, open issues, language, description, last push. |
| generate_changelogA | Generate a markdown changelog from merged PRs between two dates. |
| add_labelsC | Add labels to an existing issue. |
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 8 tools
Each tool targets a distinct aspect of GitHub project management: issues, milestones, labels, stats, and changelog. Even where functionality overlaps (e.g., add_labels vs update_issue), the descriptions clarify the specific purpose, leaving no ambiguity.
Tools follow a verb_noun pattern with snake_case, but there is a minor inconsistency: create_milestone uses singular noun while list_milestones uses plural. Additionally, get_repo_stats uses 'get' where others use 'list', but the pattern is still recognizable and predictable.
With 8 tools, the server is well-scoped for GitHub project management. Each tool earns its place by covering essential operations on issues, milestones, labels, repository stats, and changelog generation.
The tool set covers core operations: create, update, list for issues; create and list milestones; add labels. Minor gaps exist, such as no dedicated update or delete for milestones, but most workflows are supported and agents can work around these gaps.