github-mcp
Provides tools for safe GitHub developer workflows including pulling main, creating feature branches, pushing branches, and opening ready-for-review pull requests.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@github-mcp Create a new feature branch from main, push it, and open a PR"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitHub MCP Server
Local OpenCode MCP server for safe GitHub developer workflows: pull main, create a feature branch, push it, and open a ready-for-review pull request.
Environment
Set these variables in your shell. Do not commit real secrets.
export GH_TOKEN="your_github_token_here"
export GITHUB_MCP_ALLOWED_ROOTS="/Users/matiasbinagora/Projects"
export GITHUB_MCP_DEFAULT_BASE_BRANCH="main"
export GITHUB_MCP_DEFAULT_REMOTE="origin"
export GITHUB_MCP_REQUIRE_CLEAN_WORKTREE="true"GH_TOKEN is recommended. If it is not set, the server can still work when gh is already authenticated locally.
Related MCP server: local-git-mcp
Build
npm install
npm run buildSmoke Test
This creates a temporary local bare repo, pulls main, creates a test branch, commits a file, pushes the branch, and verifies the remote branch exists.
npm run smokeGitHub Integration Test
This creates a real branch and ready-for-review PR in the configured test repo.
export GITHUB_MCP_SMOKE_REPO_PATH="/Users/matiasbinagora/Projects/binagora"
npm run smoke:githubOpenCode Config
Add this to the global OpenCode config at ~/.config/opencode/opencode.json.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"github": {
"type": "local",
"command": ["node", "/Users/matiasbinagora/Projects/github-mcp/dist/index.js"],
"enabled": true,
"environment": {
"GH_TOKEN": "{env:GH_TOKEN}",
"GITHUB_MCP_ALLOWED_ROOTS": "/Users/matiasbinagora/Projects",
"GITHUB_MCP_DEFAULT_BASE_BRANCH": "main",
"GITHUB_MCP_DEFAULT_REMOTE": "origin",
"GITHUB_MCP_REQUIRE_CLEAN_WORKTREE": "true"
}
}
}
}If OpenCode is launched before your shell exports GH_TOKEN, use this command instead so the MCP server sources ~/.zshrc before starting:
"command": [
"zsh",
"-lc",
"source \"$HOME/.zshrc\" >/dev/null 2>&1; exec node \"/Users/matiasbinagora/Projects/github-mcp/dist/index.js\""
]Tools
github_repo_statusgithub_pull_maingithub_create_feature_branchgithub_push_feature_branchgithub_create_pull_requestgithub_prepare_feature_workflow
Safety Notes
Repositories must be inside
GITHUB_MCP_ALLOWED_ROOTS.No generic shell execution tool is exposed.
Direct pushes to
mainormasterare refused.Force pushes and branch deletion are not implemented.
A clean worktree is required before pulling, branch creation, and PR creation by default.
Branch names are validated with
git check-ref-format --branch.
Available Tools
6 toolsgithub_create_feature_branchCreate feature branchB
Create a new feature branch from the base branch after validating safety constraints.
Inputs: repoPath (required), branchName (required), remote, baseBranch.
github_create_pull_requestCreate GitHub pull requestB
Create a ready-for-review pull request from a pushed feature branch into the base branch.
Inputs: body (required), title (required), repoPath (required), baseBranch, +1 more.
github_prepare_feature_workflowPrepare feature workflowA
Check status, update main, and create a new feature branch. Does not push or create a PR.
Inputs: repoPath (required), branchName (required), remote, baseBranch.
github_pull_mainPull main branchA
Fetch, switch to the base branch, and fast-forward pull from the configured remote.
Inputs: repoPath (required), remote, baseBranch.
github_push_feature_branchPush feature branchA
Push a non-protected feature branch and set upstream. Refuses main/master.
Inputs: repoPath (required), remote, branchName.
github_repo_statusGet GitHub repo statusA
Inspect a local Git repository status, branch, remotes, upstream, and MCP allowed roots.
Inputs: repoPath (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose. Despite some conceptual overlap between create_feature_branch and prepare_feature_workflow, the latter includes additional steps (status check, update main) that differentiate them. All other tools are uniquely scoped.
All tool names follow a consistent verb_noun pattern with underscores, using descriptive verbs like create, prepare, pull, push, and inspect. No mixing of conventions or vague terms.
Six tools is an ideal number for a focused Git workflow server. Each tool covers a necessary step without redundancy or bloat.
The set covers the core feature workflow: status, pull, branch creation, push, and PR creation. Missing operations like branch deletion or listing PRs are minor gaps that don't break the primary workflow.
Maintenance
Related MCP Connectors
Create, deploy, and operate MCP servers directly from your GitHub repositories.
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search.
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceStandalone MCP server for GitHub that enables repository management, branch operations, pull request handling, and commit retrieval via tools listed in the README.1-
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that handles git operations on behalf of AI coding assistants, running as a local HTTP service without external network exposure by default.MIT
- AlicenseBqualityDmaintenanceA lightweight MCP server that acts as a secure proxy for AI assistants to run local Git operations and GitHub API macros simultaneously.1ISC
- AlicenseAqualityDmaintenanceA local MCP server that provides a safe, explicit set of Git operations for version control tasks like status, diff, branching, staging, committing, fetching, merging, and pushing.138 npmMIT