Connect GitLab (MCP) ​
GitLab ships an official MCP server built into your instance — no third-party bridge needed. This guide shows how to connect it to Mammouth as a custom MCP connector, for each of the three authentication methods.
Before you start
On the GitLab side you'll need:
- GitLab 18.6 or later (the MCP server is in Beta, available on the Free tier)
- GitLab Duo set to Always on or On by default
- Beta and experimental features enabled — at the instance level on Self-Managed/Dedicated, or for the top-level group on GitLab.com
- MCP server access allowed — at the instance level on Self-Managed/Dedicated, or for the top-level group on GitLab.com
See GitLab's MCP server documentation for how to turn these on.
Server URL ​
Use https://<your-gitlab-instance>/api/v4/mcp on Self-Managed or Dedicated, or https://gitlab.com/api/v4/mcp on GitLab.com. This is the same URL for all three connection methods below.
Automatic connection (OAuth) ​
GitLab's MCP server supports OAuth 2.0 dynamic client registration, so Automatic connection works with nothing to configure on the GitLab side.
- In Mammouth, add a custom MCP connector with the server URL above.
- Choose Automatic connection.
- Click Connect. Mammouth registers itself with GitLab and opens the authorization window — sign in and approve access.
API key ​
GitLab's MCP server only supports OAuth today — it does not accept a static API key or personal access token as a bearer credential (GitLab is tracking PAT support as a feature request, not yet shipped). Use Automatic connection or Manual connection instead.
Manual connection (client ID and secret) ​
Requires GitLab 19.3 or later — earlier versions don't expose the mcp scope in the OAuth application form.
Use this if dynamic client registration is disabled on your GitLab instance, or if you'd rather register one shared OAuth application for your whole team instead of letting every user's Mammouth account register its own.
- In GitLab, create an OAuth application:
- User level: your avatar → Edit profile → Access → Applications → Add new application
- Group level: the group's Settings → Applications
- Instance level (Self-Managed admins): Admin Area → Applications → New application
- Set Redirect URI to the one shown in Mammouth's Manual connection form.
- Under Scopes, select mcp.
- Clear the Confidential checkbox — Mammouth's manual connection sends no client secret, so the application must be registered as a public client.
- Save the application and copy its Application ID.
- In Mammouth, choose Manual connection, paste that ID as the Client ID, and leave Client secret blank.
WARNING
A single shared OAuth application can't serve MCP clients that use different redirect URIs. If Mammouth's redirect URI ever changes, you'll need to update the application in GitLab.