Git MCP Server vs MCP Github Project Manager

A side-by-side look at the Git MCP Server and MCP Github Project Manager MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Git MCP Server logoGit MCP ServerVersion Control · Local subprocess (stdio)Comprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.68GreatAuth: no auth requiredMCP Github Project Manager logoMCP Github Project ManagerVersion Control · Local subprocess (stdio)MCP server for AI-powered GitHub project management — 20 tools, 169 actions, agent swarm orchestration, GitHub Actions/Releases/Branches, MCP Resources & Prompts, PRD-to-issues pipeline68GreatAuth: api key required

Verdict: choose Git MCP Server for version control work as a local process; choose MCP Github Project Manager for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Git MCP Server logoChoose Git MCP Server when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: MCP_TRANSPORT_TYPE, MCP_LOG_LEVEL, MCP_HTTP_PORT, GIT_BASE_DIR, LOGS_DIR, GIT_USERNAME, GIT_EMAIL, GIT_SIGN_COMMITS.
  • You want tools like git_add, git_blame, git_branch.
Explore Git MCP Server

MCP Github Project Manager logoChoose MCP Github Project Manager when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: GITHUB_TOKEN, GITHUB_OWNER, GITHUB_REPO.
  • You want tools like manage_project, manage_issues, manage_prs.
Explore MCP Github Project Manager

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit MCP Server logoGit MCP ServerMCP Github Project Manager logoMCP Github Project Manager
CategoryVersion ControlVersion Control
Quality signal68/100 · Great68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredAPI key required
PricingFreeNot declared
Required env varsMCP_TRANSPORT_TYPEMCP_LOG_LEVELMCP_HTTP_PORTGIT_BASE_DIRLOGS_DIRGIT_USERNAMEGIT_EMAILGIT_SIGN_COMMITSGITHUB_TOKENGITHUB_OWNERGITHUB_REPO
Verified ownerCommunity listingCommunity listing
GitHub stars245105
Directory activity 9 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools2820

Tools & capabilities

Git MCP Server tools 28

  • git_addStage files for commit. Add file contents to the staging area (index) to prepare for the next commit.
  • git_blameShow line-by-line authorship information for a file, displaying who last modified each line and when. For large files, use startLine/endLine to limit output.
  • git_branchManage branches: list all branches, show current branch, create a new branch, delete a branch, or rename a branch.
  • git_changelog_analyzeGather git history context (commits, tags) and structured review instructions to support LLM-driven changelog analysis. Changelog file should be read separately; this tool provides the supporting git data and analysis framework. Pass one or more review types to control what kind of analysis to perform.
  • git_checkoutSwitch branches or restore working tree files. Can checkout an existing branch, create a new branch, or restore specific files.
  • git_cherry_pickCherry-pick commits from other branches. Apply specific commits to the current branch without merging entire branches.
  • git_cleanRemove untracked files from the working directory. Requires force flag for safety. Use dry-run to preview files that would be removed.
  • git_clear_working_dirClear the session working directory setting. This resets the context without restarting the server. Subsequent git operations will require an explicit path parameter unless git_set_working_dir is called again.
  • git_cloneClone a repository from a remote URL or local path. Accepts HTTP(S), SSH, git://, file://, and bare filesystem paths, with optional shallow cloning.
  • git_commitCreate a new commit with staged changes in the repository. Records a snapshot of the staging area with a commit message. **Commit Message Format:** Pass commit messages as JSON string parameters. Multi-line messages are supported using standard JSON string escaping. **Examples:** - Single line: { "message": "feat: add user authentication" } - Multi-line: { "message": "feat: add user authentication\n\nImplemented OAuth2 flow with JWT tokens.\nAdded tests for login and logout." } Note: Do not use bash heredoc syntax. Literal escape sequences (\n, \t) in the message string are automatically normalized to their actual characters.
  • git_diffView differences between commits, branches, or working tree. Shows changes in unified diff format.
  • git_fetchFetch updates from a remote repository. Downloads objects and refs without merging them.
  • +16 more on the listing page

MCP Github Project Manager tools 20

  • manage_projectManage GitHub Projects (v2): create, list, get, update, delete projects; manage readme, fields, views, items; handle templates and link to repos/teams. Use the `action` field to select the operation.
  • manage_issuesManage GitHub Issues: create, list, get, update issues; manage comments and drafts; search with advanced filters; manage sub-issues. Use the `action` field to select the operation.
  • manage_prsManage Pull Requests: create, get, list, update, merge PRs; list and create reviews. Use the `action` field to select the operation.
  • manage_milestonesManage Milestones: create, list, update, delete milestones; get metrics; find overdue and upcoming milestones. Use the `action` field to select the operation.
  • manage_sprintsManage Sprints: create, list, update sprints; get current sprint; add/remove issues; get metrics and plan. Use the `action` field to select the operation.
  • manage_labelsManage repository Labels: create and list labels. Use the `action` field to select the operation.
  • manage_automationManage Project Automations: list, get and delete the automation workflows of a GitHub project. Use the `action` field to select the operation.
  • manage_iterationsManage Project Iterations: get configuration, current iteration, items; find by date; assign items. Use the `action` field to select the operation.
  • manage_eventsManage Events: subscribe to project events, get recent events, replay events. Use the `action` field to select the operation.
  • manage_status_updatesManage project Status Updates: create, list, and get status updates. Use the `action` field to select the operation.
  • ai_generateAI-powered generation: generate/enhance/parse PRDs, add features, get next tasks, analyze complexity, expand tasks, create traceability matrices. Use the `action` field to select the operation.
  • ai_analyzeAI-powered analysis: enrich issues (single/bulk), triage issues, schedule triaging, suggest labels, detect duplicates, find related issues. Use the `action` field to select the operation.
  • +8 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Git MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git-mcp-server-2": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/git-mcp-server@latest"
      ],
      "env": {
        "MCP_TRANSPORT_TYPE": "YOUR_MCP_TRANSPORT_TYPE_HERE",
        "MCP_LOG_LEVEL": "YOUR_MCP_LOG_LEVEL_HERE",
        "MCP_HTTP_PORT": "YOUR_MCP_HTTP_PORT_HERE",
        "GIT_BASE_DIR": "YOUR_GIT_BASE_DIR_HERE",
        "LOGS_DIR": "YOUR_LOGS_DIR_HERE",
        "GIT_USERNAME": "YOUR_GIT_USERNAME_HERE",
        "GIT_EMAIL": "YOUR_GIT_EMAIL_HERE",
        "GIT_SIGN_COMMITS": "YOUR_GIT_SIGN_COMMITS_HERE"
      }
    }
  }
}

MCP Github Project Manager

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-github-project-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-github-project-manager"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
        "GITHUB_OWNER": "YOUR_GITHUB_OWNER_HERE",
        "GITHUB_REPO": "YOUR_GITHUB_REPO_HERE"
      }
    }
  }
}

Frequently asked questions

Git MCP Server is categorized under Version Control and uses a local stdio subprocess. MCP Github Project Manager belongs to Version Control and uses a local stdio subprocess. Pick Git MCP Server for version control work and MCP Github Project Manager for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Git MCP Server is listed as free. Auth: no auth required. MCP Github Project Manager has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add git-mcp-server-2 and mcp-github-project-manager as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Git MCP Server has a quality signal of 68/100 (Great) with 9 views, 0 installs and 245 GitHub stars. MCP Github Project Manager has 68/100 (Great) with 1 views, 0 installs and 105 GitHub stars.