How to connect Gitlab to Claude Cowork

Gitlab logo
Claude Cowork logo
divider

Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.

This guide walks you through the easiest and most secure way to connect your Gitlab account to Cowork via Composio Connect, enabling it to create new GitLab group for QA team, open bug issue in frontend project, create branch from latest main commit, and more such actions on your behalf without compromising your account security.

Also integrate Gitlab with

Connecting Gitlab to Claude Cowork

1. Open Customize

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

2. Add the Composio MCP server

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

3. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Cowork

4. Connect your Gitlab account

Back in Cowork, ask the agent to connect to Gitlab or give it any Gitlab-related task.

For example, ask Cowork to:

  • "Create new GitLab group for QA team"
  • "Open bug issue in frontend project"
  • "Create branch from latest main commit"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Cowork, and your Gitlab account is ready to use.

What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.

With Composio Connect, Cowork can securely access apps like Gitlab through MCP without you sharing account credentials directly with the agent.

What is the Gitlab MCP server, and what's possible with it?

The Gitlab MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Gitlab account. It provides structured and secure access to your repositories, projects, and issues, so your agent can perform actions like creating projects, managing issues, handling branches, and automating DevOps workflows on your behalf.

  • Project and group automation: Instantly create new Gitlab projects or organize your workspaces by setting up project groups—all without manual clicks.
  • Issue creation and tracking: Have your agent report bugs, request features, or open new issues in specific projects to keep your team on top of tasks.
  • Branch management: Let your agent create repository branches from any commit or base branch, making it easy to streamline your development process.
  • Project lifecycle management: Archive completed projects or delete unneeded ones, keeping your workspace clean and up to date with minimal effort.
  • Commit and job insights: Retrieve commit references, determine commit sequence in project history, or erase job artifacts and logs for deeper CI/CD control.

Supported Tools & Triggers

Tools
Archive ProjectTool to archive a project.
Create GitLab GroupTool to create a new group in gitlab.
Create ProjectTool to create a new project in gitlab.
Create Project IssueTool to create a new issue in a gitlab project.
Create Repository BranchTool to create a new branch in a project.
Delete ProjectTool to delete a gitlab project by its id.
Download Project AvatarTool to download a project’s avatar image.
Erase JobTool to erase the content of a specified job within a project.
Get Commit ReferencesTool to get all references (branches or tags) a commit is pushed to.
Get Commit SequenceTool to get the sequence number of a commit in a project by following parent links from the given commit.
Get Group DetailsTool to retrieve information about a specific group by its id.
Get Group MemberTool to retrieve details for a specific group member.
Get GroupsGet groups
Get Job DetailsTool to retrieve details of a single job by its id within a specified project.
Get Merge Request NotesTool to fetch comments on a merge request.
Get ProjectTool to get a single project by id or url-encoded path.
Get Project LanguagesTool to list programming languages used in a project with percentages.
Get Project MemberTool to retrieve details for a specific project member.
Get Project Member AllTool to retrieve details for a specific project member (including inherited and invited members).
Get Merge Request CommitsTool to get commits of a merge request.
Get Project Merge RequestsTool to retrieve a list of merge requests for a specific project.
Get ProjectsTool to list all projects accessible to the authenticated user.
List Merge Request DiffsTool to list all diff versions of a merge request.
Get Repository BranchTool to retrieve information about a specific branch in a project.
Get Repository BranchesRetrieves a list of repository branches for a project.
Get Single CommitTool to get a specific commit identified by the commit hash or name of a branch or tag.
Get Single PipelineTool to retrieve details of a single pipeline by its id within a specified project.
Get UserTool to retrieve information about a specific user by their id.
Get User PreferencesTool to get the current user's preferences.
Get UsersTool to retrieve a list of users from gitlab.
Get User StatusTool to get a user's status by id.
Get User StatusTool to get the current user's status.
Get User Support PINTool to get details of the current user's support pin.
Import project membersTool to import members from one project to another.
List All Group MembersTool to list all members of a group including direct, inherited, and invited members.
List All Project MembersTool to list all members of a project (direct, inherited, invited).
List Billable Group MembersTool to list billable members of a top-level group (including its subgroups and projects).
List Group MembersTool to list direct members of a group.
List Pending Group MembersTool to list pending members of a group and its subgroups and projects.
List Pipeline JobsTool to retrieve a list of jobs for a specified pipeline within a project.
List Project GroupsTool to list ancestor groups of a project.
List Project Invited GroupsTool to list groups invited to a project.
List Project PipelinesTool to retrieve a list of pipelines for a specified project.
List Project Shareable GroupsTool to list groups that can be shared with a project.
List Project Repository TagsTool to retrieve a list of repository tags for a specified project.
List Project Transfer LocationsTool to list namespaces available for project transfer.
List project usersTool to list users of a project.
List Repository CommitsTool to get a list of repository commits in a project.
List User ProjectsTool to list projects owned by a specific user.
Create Support PINTool to create a support pin for your authenticated user.
Update User PreferencesTool to update the current user's preferences.
Set User StatusTool to set the current user's status.
Share Project With GroupTool to share a project with a group.
Start Housekeeping TaskTool to start the housekeeping task for a project.

Available tools and triggers

After setup, the supported Gitlab tools and triggers listed on this page are available to Cowork through Composio Connect.

You can now ask Cowork to handle Gitlab workflows in natural language, from quick summaries and drafting tasks to more complex multi-step work across connected apps.

How to build Gitlab MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Gitlab MCP?

With a standalone Gitlab MCP server, the agents and LLMs can only access a fixed set of Gitlab tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Gitlab and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Gitlab tools.

Can I manage the permissions and scopes for Gitlab while using Tool Router?

Yes, absolutely. You can configure which Gitlab scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Gitlab data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.