Connect GitLab to Claude Code

Let Claude triage issues and comment on merge requests in GitLab. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect GitLab to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect GitLab, you add a GitLab MCP server: a small hosted service that exposes GitLab's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own GitLab account. No API keys pasted into config files.

claude mcp add --transport http gitlab https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in GitLab once connected?

Full read-write GitLab access lets Claude open and triage issues, comment on merge requests, apply labels and milestones, assign reviewers, and update descriptions once you approve. The status updates and review chores that used to mean tab-switching happen where the work already lives, inside your projects.

Open a new issue from a bug report and apply the right labels
Comment on a merge request with a review summary or follow-up questions
Add labels, milestones, or assignees to triage an issue backlog
Update an issue or merge request description to reflect the latest decision
Close or reopen issues as you work through a list
Assign reviewers and request changes on an open merge request

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same GitLab access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the GitLab API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when GitLab changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build GitLab connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same GitLab connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own GitLab account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on GitLab's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to GitLab?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the GitLab account it signs in with. Revoking access is one click in GitLab.

More on the GitLab connector

GitLab connector for claude.ai GitHub + Claude Code PagerDuty + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us