# GitLab MCP server

> Lets AI assistants read and manage GitLab projects, merge requests, issues, pipelines, wikis, and more through a policy-controlled tool registry.

- Repository: https://github.com/mcpland/gitlab-mcp
- Page: https://hostedmcp.org/servers/mcpland/gitlab-mcp
- Transport: —
- Stars: 10
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `ENABLE_DYNAMIC_API_URL` | no | no |  |
| `GITLAB_ALLOWED_PROJECT_IDS` | no | no |  |
| `GITLAB_ALLOWED_TOOLS` | no | no |  |
| `GITLAB_ALLOW_CI_VARIABLE_VALUES` | no | no |  |
| `GITLAB_ALLOW_GRAPHQL_WITH_PROJECT_SCOPE` | no | no |  |
| `GITLAB_API_URL` | no | no |  |
| `GITLAB_DENIED_TOOLS_REGEX` | no | no |  |
| `GITLAB_DISABLED_CAPABILITIES` | no | no |  |
| `GITLAB_ENABLE_CI_VARIABLE_TOOLS` | no | no |  |
| `GITLAB_ENABLE_COMPATIBILITY_ALIASES` | no | no |  |
| `GITLAB_ENABLE_DEPENDENCY_PROXY_TOOLS` | no | no |  |
| `GITLAB_OAUTH_CLIENT_ID` | no | no |  |
| `GITLAB_OAUTH_CLIENT_SECRET` | no | no |  |
| `GITLAB_OAUTH_REDIRECT_URI` | no | no |  |
| `GITLAB_PERMISSION_MODE` | no | no |  |
| `GITLAB_PERSONAL_ACCESS_TOKEN` | no | no |  |
| `GITLAB_READ_ONLY_MODE` | no | no |  |
| `GITLAB_TOOLSETS` | no | no |  |
| `GITLAB_USE_OAUTH` | no | no |  |
| `MCP_ALLOWED_HOSTS` | no | no |  |
| `REMOTE_AUTHORIZATION` | no | no |  |
| `USE_GITLAB_WIKI` | no | no |  |
| `USE_MILESTONE` | no | no |  |
| `USE_PIPELINE` | no | no |  |

## FAQ

### What authentication methods are supported?

The server supports Personal Access Tokens (PAT), OAuth 2.0 PKCE, and remote per-request authorization.

### Can I restrict the AI's access to specific GitLab projects?

Yes, you can use the GITLAB_ALLOWED_PROJECT_IDS environment variable to set restrictions.
