Cubic vs Github Enterprise MCP
A side-by-side look at the Cubic and Github Enterprise MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cubic for version control work over a hosted endpoint; choose Github Enterprise MCP 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?
Choose Cubic when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 40/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | GITHUB_TOKENGITHUB_ENTERPRISE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 29 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 20 |
| Full listing | View Cubic | View Github Enterprise MCP |
Tools & capabilities
Cubic tools
No tool names declared yet. Check the project README from the listing page.
Github Enterprise MCP tools 20
list-repositoriesRetrieve repository list for a user or organizationget-repositoryGet detailed repository informationlist-branchesList branches of a repositoryget-contentRetrieve file or directory contentslist-pull-requestsList pull requests in a repositoryget-pull-requestGet pull request detailscreate-pull-requestCreate a new pull requestmerge-pull-requestMerge a pull requestlist-issuesList issues in a repositoryget-issueGet issue detailslist-issue-commentsList comments on an issue or pull requestcreate-issueCreate a new issue- +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.
Cubic
{
"mcpServers": {
"cubic": {
"url": "https://www.cubic.dev/api/mcp"
}
}
}
Github Enterprise MCP
{
"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"
}
}
}
}
Frequently asked questions
Cubic is categorized under Version Control and uses a remote HTTP/SSE transport. Github Enterprise MCP belongs to Version Control and uses a local stdio subprocess. Pick Cubic for version control work and Github Enterprise MCP 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.
Cubic has no declared pricing — check the project's own site. Github Enterprise MCP is listed as free. 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 cubic and ddukbg-github-enterprise-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cubic has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Github Enterprise MCP has 55/100 (Good) with 6 views, 0 installs and 29 GitHub stars.