How to integrate Gitlab MCP with Claude Agent SDK

This guide walks you through connecting Gitlab to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Gitlab agent that can create new gitlab group for qa team, open bug issue in frontend project, create branch from latest main commit through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Gitlab account through Composio's Gitlab MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Gitlab logoGitlab
Oauth2

Gitlab is a web-based DevOps platform for managing source code, issues, and CI/CD pipelines. It streamlines software development with integrated collaboration and automation tools.

58 Tools

Introduction

This guide walks you through connecting Gitlab to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Gitlab agent that can create new gitlab group for qa team, open bug issue in frontend project, create branch from latest main commit through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Gitlab account through Composio's Gitlab MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Gitlab with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Gitlab
  • Configure an AI agent that can use Gitlab as a tool
  • Run a live chat session where you can ask the agent to perform Gitlab operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Gitlab account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Gitlab functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Gitlab
  const session = await composio.create(USER_ID, {
    toolkits: ['gitlab'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Gitlab
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Gitlab tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Gitlab
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Gitlab and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['gitlab']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Gitlab tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Gitlab through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Gitlab action and event your agent gets out of the box.

Archive Project

Tool to archive a project.

Create GitLab Group

Tool to create a new group in GitLab.

Create Project

Tool to create a new project in GitLab.

Create Project Issue

Tool to create a new issue in a GitLab project.

Create Repository Branch

Tool to create a new branch in a project.

Delete Project

Tool to delete a GitLab project by its ID.

Download Project Avatar

Tool to download a project's avatar image.

Erase Job

Tool to erase the content of a specified job within a project.

Get Commit References

Tool to get all references (branches or tags) a commit is pushed to.

Get Commit Sequence

Tool to get the sequence number of a commit in a project by following parent links from the given commit.

Get Group Details

Tool to retrieve information about a specific group by its ID.

Get Group Member

Tool to retrieve details for a specific group member.

Get Groups

Get Groups

Get Job Details

Tool to retrieve details of a single job by its ID within a specified project.

Get Merge Request Notes

Tool to fetch comments on a merge request.

Get Project

Tool to get a single project by ID or URL-encoded path.

Get Project Languages

Tool to list programming languages used in a project with percentages.

Get Project Member

Tool to retrieve details for a specific project member.

Get Project Member All

Tool to retrieve details for a specific project member (including inherited and invited members).

Get Project Merge Request

Tool to fetch full details for a single merge request when the MR IID is known.

Get Merge Request Commits

Tool to get commits of a merge request.

Get Project Merge Requests

Tool to retrieve a list of merge requests for a specific project.

Get Projects

Tool to list all projects accessible to the authenticated user.

List Merge Request Diffs

Tool to list all diff versions of a merge request.

Get Repository Branch

Tool to retrieve information about a specific branch in a project.

Get Repository Branches

Retrieves a list of repository branches for a project.

Get Single Commit

Tool to get a specific commit identified by the commit hash or name of a branch or tag.

Get Single Pipeline

Tool to retrieve details of a single pipeline by its ID within a specified project.

Get User

Tool to retrieve information about a specific user by their ID.

Get User Preferences

Tool to get the current user's preferences.

Get Users

Tool to retrieve a list of users from GitLab.

Get User Status

Tool to get a user's status by ID.

Get User Status

Tool to get the current user's status.

Get User Support PIN

Tool to get details of the current user's Support PIN.

Import project members

Tool to import members from one project to another.

List All Group Members

Tool to list all members of a group including direct, inherited, and invited members.

List All Project Members

Tool to list all members of a project (direct, inherited, invited).

List Billable Group Members

Tool to list billable members of a top-level group (including its subgroups and projects).

List Group Members

Tool to list direct members of a group.

List Group Projects

Tool to list projects within a GitLab group by group ID or full path.

List Pending Group Members

Tool to list pending members of a group and its subgroups and projects.

List Pipeline Jobs

Tool to retrieve a list of jobs for a specified pipeline within a project.

List Project Groups

Tool to list ancestor groups of a project.

List Project Invited Groups

Tool to list groups invited to a project.

List Project Issues

Tool to list issues for a project with filtering options (state, labels, search, assignee, author, etc.

List Project Pipelines

Tool to retrieve a list of pipelines for a specified project.

List Project Shareable Groups

Tool to list groups that can be shared with a project.

List Project Repository Tags

Tool to retrieve a list of repository tags for a specified project.

List Project Transfer Locations

Tool to list namespaces available for project transfer.

List project users

Tool to list users of a project.

List Repository Commits

Tool to get a list of repository commits in a project.

List User Projects

Tool to list projects owned by a specific user.

Create Support PIN

Tool to create a support PIN for your authenticated user.

Update User Preferences

Tool to update the current user's preferences.

Set User Status

Tool to set the current user's status.

Share Project With Group

Tool to share a project with a group.

Start Housekeeping Task

Tool to start the housekeeping task for a project.

Update Project Issue

Tool to update an existing issue in a GitLab project (title, description, labels, assignees, state, etc.

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Gitlab.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Gitlab tool your agent needs.Free to start.

Start building