GitHub Flow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub token | |
| GITHUB_INITIALS | No | Your initials | |
| BASECAMP_CLIENT_ID | No | Your Basecamp client ID | |
| BASECAMP_ACCOUNT_ID | No | Your Basecamp account ID | |
| BASECAMP_PROJECT_ID | No | Your Basecamp project ID | |
| GITHUB_DEFAULT_OWNER | Yes | The default GitHub owner or organization | |
| GITHUB_WRITE_ENABLED | No | Whether write tools are enabled | false |
| BASECAMP_ACCESS_TOKEN | No | Your Basecamp access token | |
| BASECAMP_CLIENT_SECRET | No | Your Basecamp client secret | |
| GITHUB_LOCAL_REPOS_ROOT | No | The root directory for local repositories | |
| GITHUB_DEFAULT_BASE_BRANCH | No | The default base branch | |
| GITHUB_REPOSITORY_POLICY_FILE | No | A path to a file defining repository-specific policies | |
| BASECAMP_BACKFILL_LINKED_ISSUES | No | Whether to backfill linked Basecamp issues | false |
| GITHUB_CONFIRMATION_TTL_SECONDS | No | The confirmation token TTL in seconds | 300 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthcheckD | – |
| get_authenticated_userD | – |
| get_repositoryB | Gets repository metadata and permissions. |
| list_branchesC | Lists repository branches. |
| get_collaborator_permissionC | Checks whether a user/bot is a collaborator and returns repository permission. |
| inspect_local_repositoryB | Inspects a local Git repository without changing files, branches, commits, or remotes. |
| preview_branch_nameB | Builds and validates the branch name without creating the branch. |
| preview_local_commitB | Previews a local commit plan. This tool never creates commits. |
| preview_remote_branchC | Preview a branch and issue a token bound to the exact source commit. |
| list_pull_requestsC | List pull requests ordered by most recently updated. |
| get_pull_requestC | Get a pull request by number. |
| list_pull_request_filesC | List changed files in a pull request. |
| list_pull_request_reviewsC | List reviews for a pull request. |
| preview_pull_requestB | Preview a pull request and issue a token bound to the exact final payload. |
| preview_pull_request_commentC | Preview a PR timeline comment and issue a token for the exact body. |
| build_basecamp_pr_updateC | Build Markdown for a separate Basecamp MCP without writing to Basecamp. |
| list_workflowsC | Lists GitHub Actions workflows in a repository. |
| list_workflow_runsC | Lists recent GitHub Actions workflow runs with optional filters. |
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 18 tools
There is heavy overlap among the many 'preview_' tools: preview_branch_name, preview_local_commit, preview_remote_branch, preview_pull_request, and preview_pull_request_comment all follow a 'preview' pattern but differ in what they preview. More seriously, inspect_local_repository and preview_local_commit both involve inspecting local state, and several tools have empty descriptions (healthcheck, get_authenticated_user, get_repository, list_branches) that provide no cues for disambiguation, making misselection likely.
Most tools follow a consistent verb_noun pattern (list_pull_requests, get_pull_request, list_branches, list_workflows). However, there is a notable deviation with build_basecamp_pr_update and healthcheck, and the 'preview_' family uses a verb style distinct from the rest of the set, creating a mixed but still readable convention.
At 18 tools, the count is on the heavier side but reasonable for a GitHub workflow orchestration server that spans local inspection, PR operations, Basecamp integration, and CI workflows. Several tools feel edge-case specific (healthcheck, get_authenticated_user, list_collaborator_permission), but each has a defensible purpose.
The server covers core GitHub operations like listing/getting PRs, branches, workflows, and repository information. However, there are notable gaps: no create/update/merge pull request tools, no create/delete branch tools, and no workflow dispatch or run detail tools. The surface is read-inspection heavy but lacks the mutation actions expected of a 'workflow' server.