SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Gitlab MCP with LlamaIndex

Connect LlamaIndex to Gitlab MCP. Create new gitlab group for qa team, open bug issue in frontend project, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
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.

123 Tools

Introduction

This guide walks you through connecting Gitlab to LlamaIndex 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 LlamaIndex 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

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKClaude Agent SDKGrok BotCodexKimi CodeGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentPiDeepSeek HarnessCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Gitlab
  • Connect LlamaIndex to the Gitlab MCP server
  • Build a Gitlab-powered agent using LlamaIndex
  • Interact with Gitlab through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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 step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Gitlab account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Gitlab

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Gitlab access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called gitlab_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

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

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["gitlab"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Gitlab actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, gitlab)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Gitlab tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Gitlab
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Gitlab tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Gitlab
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Gitlab, then start asking questions.

Complete Code

Here's the complete code to get you started with Gitlab and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

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

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["gitlab"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Gitlab actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Gitlab to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Gitlab tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Add Spent Time

Adds spent time to a GitLab issue for time tracking purposes.

Approve Merge Request

Approves a merge request in a GitLab project.

Archive Project

Tool to archive a project.

Cancel Job

Cancel a GitLab CI/CD job within a specified project.

Cancel Pipeline

Tool to cancel a running pipeline in a GitLab project.

Create Commit

Creates a new commit with multiple file operations in a GitLab project.

Create Commit Comment

Posts a comment to a specific commit in a GitLab project repository.

Create Repository File

Creates a new file in a GitLab repository at the specified path with the given content.

Create GitLab Group

Tool to create a new group in GitLab.

Create Issue Note

Creates a new note (comment) on a project issue in GitLab.

Create Label

Creates a new label for a GitLab project with specified name, color, and optional attributes.

Create Merge Request

Creates a new merge request in a GitLab project to propose changes from a source branch into a target branch.

Create Merge Request Draft Note

Creates and saves an unpublished merge request draft note that is visible only to its author.

Create Milestone

Creates a new milestone in a GitLab project.

Create Pipeline

Tool to create a new pipeline for a specific branch or tag in a GitLab project.

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.

Create Project Webhook

Creates a new webhook (project hook) for a GitLab project to receive real-time event notifications.

Delete Group

Deletes a GitLab group by its ID or URL-encoded path.

Delete Issue Note

Deletes a note (comment) from an issue in a GitLab project.

Delete Label

Deletes a label from a GitLab project by its ID or title.

Delete Merge Request

Tool to permanently delete a merge request from a GitLab project.

Delete Milestone

Deletes a project milestone by its ID.

Delete Pipeline

Tool to delete a CI/CD pipeline by its ID within a specified project.

Delete Project

Tool to delete a GitLab project by its ID.

Delete Repository Branch

Tool to delete a branch from a GitLab project repository.

Delete Repository File

Deletes a file from a GitLab repository by creating a new commit.

Delete Webhook

Deletes a project webhook/hook permanently from a GitLab project, removing the integration and stopping all event notifications.

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.

Fork Project

Forks a GitLab project to a specified namespace or the current user's namespace.

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 Current User

Retrieves information about the currently authenticated user.

Get Repository File

Retrieves a single file from a GitLab repository at a specific ref (branch, tag, or 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 Issue

Retrieves a single issue from a GitLab project by its internal ID (iid).

Get Issue Note

Retrieves a single comment (note) from a GitLab issue by its ID.

Get Job Details

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

Get Job Trace

Retrieves the trace (log output) for a specific CI/CD job within a project.

Get Project Label

Retrieves a single project label by its ID or title.

Get Merge Request Approvals

Retrieves aggregate approval status for a GitLab merge request on any GitLab tier.

Get Merge Request Approval State

Retrieves rule-level approval satisfaction for a GitLab merge request.

Get Merge Request Notes

Tool to fetch comments on a merge request.

Get Milestone

Retrieves a single milestone by its ID for a specific project.

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 Diff Versions

Tool to list all diff versions of a merge request.

Get Raw File

Retrieves the raw contents of a file from a GitLab repository without Base64 encoding.

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 Issue Time Stats

Retrieves time tracking statistics for a specific issue in a 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 Any User's Status by ID

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.

Get Webhook

Retrieves detailed information about a specific project webhook by its ID.

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 Commit Comments

Retrieves all comments associated with a specific commit in a GitLab project.

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 Issue Notes

Retrieves all notes (comments and activity) for a specific project issue in GitLab.

List Labels

Lists all labels for a project with optional filtering by name, archived status, and ancestor inclusion.

List Merge Request Diffs

List the files changed by a GitLab merge request, including patch content.

List Merge Request Discussions

Lists grouped discussion threads and their notes for a merge request.

List Merge Requests

Retrieves a list of merge requests from across all accessible projects based on scope and filters.

List Project Milestones

Lists all milestones for a specific project with optional filtering by state, title, or search terms.

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 Repository Tree

List files and directories in a GitLab project's repository tree.

List User Projects

Tool to list projects owned by a specific user.

List Webhooks

Tool to list all webhooks configured for a GitLab project.

Merge Merge Request

Merge a GitLab merge request immediately or enable auto-merge when checks pass.

Move Issue

Moves an issue from one project to another in GitLab.

Play Job

Triggers execution of a manual job in a GitLab project.

Create Support PIN

Tool to create a support PIN for your authenticated user.

Protect Branch

Protects a repository branch in a GitLab project by setting access controls for push, merge, and unprotect operations.

Update User Preferences

Tool to update the current user's preferences.

Reset Spent Time

Resets the total spent time for a specified GitLab issue to 0 seconds.

Reset Time Estimate

Resets the estimated time for a specified issue to 0 seconds.

Retry Pipeline

Retries failed or canceled jobs in a pipeline.

Set Time Estimate

Sets the estimated time to complete an issue in a GitLab project.

Set User Status

Tool to set the current user's status.

Share Project With Group

Tool to share a project with a group.

Star Project

Stars a project in GitLab, marking it as a favorite for the authenticated user.

Start Housekeeping Task

Tool to start the housekeeping task for a project.

Unapprove Merge Request

Removes the approval from the currently authenticated user for a specified merge request.

Unprotect Branch

Tool to remove protection from a branch in a GitLab project.

Unstar Project

Unstar a previously starred GitLab project to remove it from your favorites list.

Update GitLab Group

Updates an existing GitLab group's settings and properties.

Update Issue Note

Updates an existing note (comment) on a GitLab issue.

Update Label

Updates an existing label in a GitLab project by modifying its name, color, description, priority, or archived status.

Update Merge Request

Updates an existing merge request in a GitLab project (title, description, assignees, reviewers, labels, state, etc.

Update Milestone

Updates an existing milestone in a GitLab project, allowing you to modify the title, description, dates, or state.

Update Project Issue

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

Update Repository File

Updates an existing file in a GitLab repository.

Update Webhook

Updates an existing project webhook configuration including URL, event triggers, SSL verification, and authentication token.

Validate Credential

Validates the authentication credentials by retrieving the currently authenticated user's information.

FRAMEWORKS

How to build Gitlab MCP Agent with another framework

Claude Code logo

Claude Code

Use Gitlab MCP with Claude Code

Cursor logo

Cursor

Use Gitlab MCP with Cursor

ChatGPT logo

ChatGPT

Use Gitlab MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Gitlab MCP with Claude Cowork

Antigravity logo

Antigravity

Use Gitlab MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Gitlab MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Gitlab MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Gitlab MCP with Grok Bot

Codex logo

Codex

Use Gitlab MCP with Codex

Kimi Code logo

Kimi Code

Use Gitlab MCP with Kimi Code

Grok Build logo

Grok Build

Use Gitlab MCP with Grok Build

VS Code logo

VS Code

Use Gitlab MCP with VS Code

OpenCode logo

OpenCode

Use Gitlab MCP with OpenCode

OpenClaw logo

OpenClaw

Use Gitlab MCP with OpenClaw

Hermes logo

Hermes

Use Gitlab MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Gitlab MCP with Atomic Agent

Pi logo

Pi

Use Gitlab MCP with Pi

DeepSeek Harness logo

DeepSeek Harness

Use Gitlab MCP with DeepSeek Harness

CLI logo

CLI

Use Gitlab MCP with CLI

Google ADK logo

Google ADK

Use Gitlab MCP with Google ADK

LangChain logo

LangChain

Use Gitlab MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Gitlab MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Gitlab MCP with Mastra AI

CrewAI logo

CrewAI

Use Gitlab MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Gitlab MCP with Pydantic AI

AutoGen logo

AutoGen

Use Gitlab MCP with AutoGen

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. LlamaIndex 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