How to integrate Gitlab MCP with Grok Build

Connect Grok Build to Gitlab MCP. Create new gitlab group for qa team, open bug issue in frontend project, and more from your terminal, with authentication handled for you.

Get started for free Get a demo

Gitlab

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

Managed auth

Connect Gitlab without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

How to integrate Gitlab MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Gitlab account to Grok Build through Composio, so it can create new GitLab group for QA team, open bug issue in frontend project, create branch from latest main commit, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Why use Composio over a standalone MCP server?

Read and write access. Composio's Gitlab integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
Access to the Gitlab account you want to connect.
The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Gitlab to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash

curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash

grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash

https://connect.composio.dev/mcp

Grok Build /mcps extensions modal listing MCP servers

Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server

Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Gitlab account through Composio. On the first Gitlab action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Gitlab

Create new GitLab group for QA team
Open bug issue in frontend project
Create branch from latest main commit
Archive completed API migration project

Security + privacy notes (important)

Use least-privilege access. Grant only the Gitlab scopes you actually need.
Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.

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

FRAMEWORKS

How to build Gitlab MCP Agent with another framework

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Supabase

Oauth2Api Key

Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.

Codeinterpreter

No Auth

Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

GitHub

Oauth2

GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.

1password

Api Key

1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk.

FAQ

Frequently asked questions

A standalone Gitlab MCP server gives Grok Build a fixed set of Gitlab tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Gitlab and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Gitlab data and credentials are handled to that standard.

Start with Gitlab.It takes 30 seconds.

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

Start building

How to integrate Gitlab MCP with Grok Build

Connect Gitlab without auth hassles

How to integrate Gitlab MCP with Grok Build

Also integrate Gitlab with

Why use Composio over a standalone MCP server?

Prerequisites

Step-by-step: Connect Gitlab to Grok Build

1. Install and verify Grok Build

2. Add the Composio server

3. Authenticate

4. Start building

What you can do after connecting Gitlab

Security + privacy notes (important)

Supported Tools

How to build Gitlab MCP Agent with another framework

ChatGPT Work

Antigravity

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

Kimi Code

Cursor

VS Code

OpenCode

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

1password

Frequently asked questions

What is the difference between the Composio Tool Router and a standalone Gitlab MCP server?+

Does Grok Build support MCP?+

Can I reuse the same MCP config I already use with Claude Code?+

How safe is my Gitlab data with Composio?+

Start with Gitlab.It takes 30 seconds.