GitLab + Grok Bot
How to connect GitLab to Grok Bot
Connect GitLab to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
On this page
Overview
This guide connects GitLab to Grok Bot through Agent200's MCP server. When you finish, Grok Bot can search, read and act in GitLab with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Grok Bot with your Agent200 API key. Your GitLab account is connected through managed OAuth: you approve access once on GitLab's own page, and Agent200 keeps the connection working.
- Connector
- GitLab
- Works with
- Grok Bot ยท Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 8 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- GitLab enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a GitLab account. They approve access once, on GitLab's own page.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect GitLab to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers GitLab and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it. -
5
Step 5: Connect your GitLab account
The first time you ask Grok Bot for something in GitLab, Agent200 returns an authorization link. Open it and approve access on GitLab's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Which merge requests are waiting for my review
What should come back
- An answer built from your own GitLab data.
-
Behind the scenes, Grok Bot calls an Agent200 tool for GitLab, such as
gitlab_list_merge_requests.
If Grok Bot shows an authorization link instead, you have not connected GitLab yet: open it, approve access, then ask again.
Get your API key
Create a key in the Agent200 dashboard. It reaches GitLab and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect GitLab to Grok Bot.
Goal: connect GitLab to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/tools/gitlab/framework/grok-bot/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure GitLab is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands. 4. The first GitLab request returns an authorization link if the user has not connected GitLab yet: show it to them and continue once they have approved access on GitLab's own page. 5. Check it works with this request: "Which merge requests are waiting for my review" What should come back: - An answer built from your own GitLab data. - Behind the scenes, Grok Bot calls an Agent200 tool for GitLab, such as `gitlab_list_merge_requests`. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in GitLab, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /tools/gitlab/framework/grok-bot.md
GitLab tools Grok Bot can call
-
List merge requests
Readgitlab_list_merge_requestsList a project's merge requests, filtered by state, author or reviewer.
-
Get a merge request
Readgitlab_get_merge_requestRead a merge request's description, status and changes.
-
Search issues
Readgitlab_search_issuesFind issues by text, label, assignee or state.
-
Create an issue
Writegitlab_create_issueOpen an issue in a project, with labels and an assignee.
-
Add a comment
Writegitlab_create_noteComment on an issue or a merge request.
-
Read a file
Readgitlab_get_fileRead a file from a repository at a branch, tag or commit.
-
List pipelines
Readgitlab_list_pipelinesList a project's CI/CD pipelines and their status.
-
Retry a pipeline
Writegitlab_retry_pipelineRun a pipeline's failed jobs again.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in GitLab.
-
02
Grok Bot picks a tool
It sees the GitLab tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own GitLab connection, within the tools and scopes your project allows.
-
04
Grok Bot answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's GitLab account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and GitLab enforces what its API grants.
Troubleshooting
The server cannot be saved, or shows Disabled by team admin
Your team’s connector policy blocks it. Ask the admin to allow the Agent200 server address on the Plugins & MCPs page of the Cursor dashboard.
Calls fail on a team with a network allowlist
If the admin applies the network allowlist to MCP servers, api.agent200.com must be on it.
The connector shows Needs auth, or tools return 401
Check the Authorization header is exactly Bearer, a space and a valid key, then reconnect. If the key was replaced, remove the connector and add it again.
The Bot cannot see the GitLab tools
Check Agent200 is enabled in your plugins, attach it with @ in the chat, and start a new chat if it was added mid-conversation.
Grok Bot shows a GitLab authorization link
You have not connected GitLab yet, or the connection needs to be approved again. Open the link, approve access on GitLab's own page, then ask Grok Bot again.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that GitLab and the tools you need are enabled in the dashboard's Connectors settings, and that you granted GitLab the access the task needs.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Grok Bot's MCP settings, and stop using the old one. Paste the key only into Grok Bot's settings, never into a chat.