How to integrate Gitlab MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Gitlab logo
OpenCode logo
divider

How to integrate Gitlab MCP with OpenCode

This guide explains how to connect Gitlab MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Gitlab with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Gitlab with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Gitlab

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Gitlab Composio".
  3. Complete the authentication and authorization flow, and your Gitlab integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Gitlab to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Gitlab with OpenCode

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

For example, ask it 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 to Gitlab.

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

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.

Way Forward

Now that Gitlab is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

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 OpenCode?

Yes, you can. OpenCode 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.