GitLab MCP Server vs Repowise
A side-by-side look at the GitLab MCP Server and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GitLab MCP Server for version control work as a local process; choose Repowise 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 GitLab MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITLAB_TOKEN, GITLAB_API_URL. - You want tools like
browse_pipelines, manage_pipeline, browse_environments.
Choose Repowise 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 57/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | GITLAB_TOKENGITLAB_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 7,875 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View GitLab MCP Server | View Repowise |
Tools & capabilities
GitLab MCP Server tools 4
browse_pipelineslist, get, jobs, job, logs, triggersmanage_pipelinecreate, retry, cancelbrowse_environmentslist, get, list_deploymentsmanage_environmentcreate, update, stop, delete, update_deployment_status
Repowise 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.
GitLab MCP Server
{
"mcpServers": {
"gitlab-mcp-server-2": {
"command": "npx",
"args": [
"-y",
"@structured-world/gitlab-mcp"
],
"env": {
"GITLAB_TOKEN": "YOUR_GITLAB_TOKEN_HERE",
"GITLAB_API_URL": "YOUR_GITLAB_API_URL_HERE"
}
}
}
}
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
GitLab MCP Server is categorized under Version Control and uses a local stdio subprocess. Repowise belongs to Version Control and uses a local stdio subprocess. Pick GitLab MCP Server for version control work and Repowise 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.
GitLab MCP Server has no declared pricing — check the project's own site. Repowise is listed as free. Auth: no auth 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 gitlab-mcp-server-2 and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitLab MCP Server has a quality signal of 57/100 (Good) with 1 views, 0 installs and 8 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,875 GitHub stars.