github-workflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPO_NAME | Yes | Target repository name (e.g., my-project) | |
| REPO_PATH | Yes | Absolute path to local repository (e.g., /Users/me/my-project) | |
| REPO_OWNER | Yes | Target repository owner (e.g., myorg) | |
| GITHUB_TOKEN | Yes | GitHub Personal Access Token (repo scope) | |
| ANTHROPIC_API_KEY | No | Claude API key (only needed for run_workflow tool) | |
| DEFAULT_BASE_BRANCH | No | Default base branch | main |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_labelsA | List all available labels in the repository. Call this before create_issue to see which label names are valid. |
| create_issueA | Create a GitHub issue. Use list_labels first to pick valid label names — non-existent labels are rejected. |
| create_branchA | Create a new GitHub branch from a base branch. |
| run_testsA | Run the test suite and return pass/fail status with full output. |
| commit_and_pushA | Stage files, create a commit, and push to the current branch. |
| create_prB | Open a GitHub Pull Request for the given branch. |
| get_pr_review_summaryA | Fetch and summarise all review comments for a Pull Request. |
| run_workflowA | Fully automated workflow: AI generates code, runs tests (retrying up to 3 times on failure), commits, pushes, and opens a PR. Requires ANTHROPIC_API_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| workflow | Standard prompt for implementing a feature end-to-end using the github-workflow MCP tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| repo-context | Repository file structure and key file contents. Attach before asking Claude to write or modify code. |
| repo-recent-prs | Recent pull requests (up to 10, sorted by last updated). Useful for context on active work. |
TDQS
Scored across 8 tools
Most tools are clearly distinct (create_branch, create_issue, create_pr, list_labels, get_pr_review_summary). However, run_workflow subsumes commit_and_push and run_tests, potentially causing selection ambiguity. Descriptions mitigate this by specifying that run_workflow is a high-level automated workflow.
All tool names follow a consistent snake_case verb_noun pattern (e.g., create_branch, list_labels, run_tests, get_pr_review_summary). Even compound verbs like commit_and_push adhere to the pattern without mixing styles.
8 tools is well within the typical 3-15 range for a focused MCP server. Each tool serves a distinct purpose in the development workflow, from branching and committing to testing and PR creation, without unnecessary bloat.
The tool set covers the core workflow (branching, committing, testing, PR creation, issue creation) and includes supporting tools (list_labels, get_pr_review_summary). Minor gaps exist: no direct file manipulation, no delete branch, and no tools for managing PRs after creation (e.g., merge). However, the stated purpose is workflow automation, and the set is largely complete for that.