Github Enterprise MCP vs GitResume

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

Github Enterprise MCP logoGithub Enterprise MCPVersion Control · Local subprocess (stdio)MCP server for GitHub Enterprise API integration55GoodAuth: api key required
G
GitResumeVersion Control · Remote HTTP/SSE
Validate, build, and publish the resume you keep as YAML in your own GitHub repository.39FairAuth: oauth 2.0

Verdict: choose Github Enterprise MCP for version control work as a local process; choose GitResume 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?

Github Enterprise MCP logoChoose Github Enterprise MCP 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_ENTERPRISE_URL.
  • You want tools like list-repositories, get-repository, list-branches.
Explore Github Enterprise MCP

G
Choose GitResume 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.
Explore GitResume

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGithub Enterprise MCP logoGithub Enterprise MCP
G
GitResume
CategoryVersion ControlVersion Control
Quality signal55/100 · Good39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredOAuth 2.0
PricingFreeNot declared
Required env varsGITHUB_TOKENGITHUB_ENTERPRISE_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars29—
Directory activity 6 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools20Not listed

Tools & capabilities

Github Enterprise MCP tools 20

  • list-repositoriesRetrieve repository list for a user or organization
  • get-repositoryGet detailed repository information
  • list-branchesList branches of a repository
  • get-contentRetrieve file or directory contents
  • list-pull-requestsList pull requests in a repository
  • get-pull-requestGet pull request details
  • create-pull-requestCreate a new pull request
  • merge-pull-requestMerge a pull request
  • list-issuesList issues in a repository
  • get-issueGet issue details
  • list-issue-commentsList comments on an issue or pull request
  • create-issueCreate a new issue
  • +8 more on the listing page

GitResume tools

No tool names declared yet. Check the project README from 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.

Github Enterprise MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ddukbg-github-enterprise-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ddukbg/github-enterprise-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
        "GITHUB_ENTERPRISE_URL": "YOUR_GITHUB_ENTERPRISE_URL_HERE"
      }
    }
  }
}

GitResume

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

Frequently asked questions

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

Github Enterprise MCP is listed as free. Auth: api key required. GitResume has no declared pricing — check the project's own site. 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 ddukbg-github-enterprise-mcp and gitresume as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Github Enterprise MCP has a quality signal of 55/100 (Good) with 6 views, 0 installs and 29 GitHub stars. GitResume has 39/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.