Github MCP Server vs Gitlab MCP Server
A side-by-side look at the Github MCP Server and Gitlab MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Github MCP Server for version control work over a hosted endpoint; choose Gitlab MCP Server 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 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.
Choose Gitlab MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GITLAB_TOKEN, GITLAB_MCP_READ_ONLY. - You want tools like
gitlab_execute_action, gitlab_find_action.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | GITLAB_TOKENGITLAB_MCP_READ_ONLY |
| Verified owner | Verified | Community listing |
| GitHub stars | 34,320 | 47 |
| Directory activity | 12 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 2 | 2 |
| Full listing | View Github MCP Server | View Gitlab MCP Server |
Tools & capabilities
Github MCP Server tools 2
get_file_contentsgetFileContents
Gitlab MCP Server tools 2
gitlab_execute_actionExecute one GitLab catalog action by canonical ID or alias. Always pass params as an object. Destructive actions require top-level confirm=true. Use find first only when action or params are unclear. Example: {"action":"issue.list","params":{"project_id":"group/project"}}gitlab_find_actionSearch the local GitLab action catalog. Read-only and no GitLab API call. Use when the action ID or params are unclear. Returns schemas, hints, destructive flags, and execute examples. Example: {"query":"issue list"}
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 MCP Server
{
"mcpServers": {
"github-github-mcp-server": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
Gitlab MCP Server
{
"mcpServers": {
"jmrplens-gitlab-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jmrp.io/gitlab-mcp-server"
],
"env": {
"GITLAB_TOKEN": "YOUR_GITLAB_TOKEN_HERE",
"GITLAB_MCP_READ_ONLY": "YOUR_GITLAB_MCP_READ_ONLY_HERE"
}
}
}
}
Frequently asked questions
Github MCP Server is categorized under Version Control and uses a remote HTTP/SSE transport. Gitlab MCP Server belongs to Version Control and uses a local stdio subprocess. Pick Github MCP Server for version control work and Gitlab 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.
Github MCP Server is listed as free. Auth: oauth 2.0. Gitlab 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 github-github-mcp-server and jmrplens-gitlab-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Github MCP Server has a quality signal of 81/100 (Excellent) with 12 views, 0 installs and 34,320 GitHub stars. Gitlab MCP Server has 67/100 (Great) with 3 views, 0 installs and 47 GitHub stars.