Gitwand vs Github MCP Server

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

Gitwand logoGitwandVersion Control · Local subprocess (stdio)Auto-resolves Git merge conflicts so agents only touch the complex hunks.60GoodAuth: not declaredGithub MCP Server logoGithub MCP ServerVersion Control · Remote HTTP/SSEOfficial GitHub server for integration with repository management, PRs, issues, and more.81ExcellentAuth: oauth 2.0

Verdict: choose Gitwand for version control work as a local process; choose Github MCP Server for version control over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Gitwand logoChoose Gitwand when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like gitwand_status, gitwand_resolve_conflicts, gitwand_preview_merge.
Explore Gitwand

Github MCP Server logoChoose Github MCP Server when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like get_file_contents, getFileContents.
Explore Github MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGitwand logoGitwandGithub MCP Server logoGithub MCP Server
CategoryVersion ControlVersion Control
Quality signal60/100 · Good81/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars18633,863
Directory activity 1 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools72

Tools & capabilities

Gitwand tools 7

  • gitwand_statusList conflicted files with their complexity and auto-resolvability
  • gitwand_resolve_conflictsAuto-resolve trivial conflicts, return DecisionTrace + pendingHunks
  • gitwand_preview_mergeDry-run resolution — stats and risk assessment without writing files
  • gitwand_explain_hunkExplain why a specific hunk was classified its type (full trace + context)
  • gitwand_apply_resolutionApply a custom (LLM-provided) resolution to a specific complex hunk
  • gitwand_resolve_hunkAsk the connected agent to propose a resolution for one pending hunk (ours/theirs/base + trace returned)
  • gitwand_resolve_hunk_llmValidate an LLM-proposed resolution through the post-merge gate, then apply it to disk

Github MCP Server tools 2

  • get_file_contents
  • getFileContents

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.

Gitwand

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gitwand": {
      "command": "npx",
      "args": [
        "-y",
        "@gitwand/mcp"
      ]
    }
  }
}

Github MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "github-github-mcp-server": {
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}

Frequently asked questions

Gitwand is categorized under Version Control and uses a local stdio subprocess. Github MCP Server belongs to Version Control and uses a remote HTTP/SSE transport. Pick Gitwand for version control work and Github MCP Server 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.

Gitwand is listed as free. Github MCP Server is listed as free. Auth: oauth 2.0. 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 gitwand and github-github-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Gitwand has a quality signal of 60/100 (Good) with 1 views, 0 installs and 186 GitHub stars. Github MCP Server has 81/100 (Excellent) with 7 views, 0 installs and 33,863 GitHub stars.