| FMRS | 60 / 100 · C | 76 / 100 · B |
|---|
| Reliability | 9 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 14 / 20 |
|---|
| Maintenance | 11 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Teams that want AI clients to operate GitLab project-management and collaboration workflows.
- Users working with GitLab.com and self-managed GitLab instances.
- Deployments needing read-only mode, toolsets, individual tool filters, or deny patterns.
- Developers needing local stdio or remote HTTP MCP access.
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Projects that do not use GitLab or need GitLab API operations.
- Static code-reading scenarios where GitLab credentials should not be granted.
- Deployments that require REMOTE_AUTHORIZATION together with SSE.
- Environments unable to securely manage personal, OAuth, cookie, or remote authorization credentials.
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - GITLAB_PERSONAL_ACCESS_TOKEN is required unless another supported authentication method is used.
- The token should have scopes required by the selected tools, such as api or read_api.
- Write, delete, pipeline, and project-management tools require corresponding GitLab permissions.
- GITLAB_READ_ONLY_MODE can expose only read-only tools.
- Access can be constrained with GITLAB_ALLOWED_PROJECT_IDS, GITLAB_TOOLSETS, GITLAB_TOOLS, and GITLAB_DENIED_TOOLS_REGEX.
- Wiki tools require USE_GITLAB_WIKI or the relevant toolset to be enabled.
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - Tokens with the api scope or write tools may permit creating, changing, merging, or deleting GitLab resources.
- Personal access tokens, job tokens, cookies, and OAuth tokens are sensitive credentials and should not be exposed in logs or shared configuration.
- NODE_TLS_REJECT_UNAUTHORIZED=0 weakens TLS certificate validation and should only be used intentionally for invalid or self-signed certificates.
- Remote HTTP deployments require correctly configured authentication, sessions, origins, hosts, and proxy trust settings.
- download_job_artifacts and other download tools may save content to local paths.
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Code, VS Code, GitHub Copilot, Codex, Cursor, Cline, Roo Code, Kilo Code, Amp Code, Claude.ai, OpenCode, Factory AI Droid, OpenClaw | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 100 | 15 |
|---|