Custom GitLab

Provides seamless MCP integration with GitLab to search repositories, fetch contents, and manage files, issues, and branching operations.

javascript

GitHub Stars

javascript

Language

2 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "din-djarin2-custom-gitlab": {
      "command": "node",
      "args": [
        "/path/to/custom-gitlab-server/index.js"
      ],
      "env": {
        "GITLAB_API_URL": "https://your-gitlab-instance/api/v4",
        "GITLAB_PERSONAL_ACCESS_TOKEN": "your-gitlab-token"
      }
    }
  }
}

You can run a dedicated MCP server that connects to GitLab to search repositories, read and write files, manage issues and merge requests, and perform common repo operations from your AI assistants. This server provides a stable, MCP-compliant interface so your tools can interact with GitLab programmatically and safely.

How to use

You will connect your MCP client to the GitLab MCP Server as a local process. The server exposes a set of tools that let you search projects, fetch file contents, create or update files, push multiple files in a single commit, and perform common repository actions like forking, branching, creating issues, and creating merge requests. Use the provided environment variables to securely authorize against your GitLab instance, and reference the API URL to target your GitLab server.

How to install

Prerequisites: you need Node.js version 14 or higher and GitLab access with appropriate permissions.

Step 1. Clone the custom GitLab MCP server repository.

Step 2. Install dependencies.

npm install

Step 3. Configure the MCP server in your client settings. Use the following example to wire up the local server process. Replace the placeholder path and values with your actual setup.

{
  "mcpServers": {
    "gitlab_mcp": {
      "command": "node",
      "args": [
        "/path/to/custom-gitlab-server/index.js"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "your-gitlab-token",
        "GITLAB_API_URL": "https://your-gitlab-instance/api/v4"
      }
    }
  }
}

Additional notes

The server is designed for local deployment and runs as a standard Node.js process. Ensure the GitLab token has the necessary scopes: api for full access, read_api for read-only access, and read_repository/write_repository for repository operations as needed.

Configuration and security

Keep sensitive credentials like your GitLab access token in secure storage and reference them only through environment variables. Do not hard-code tokens in commands or configuration files that could be exposed. Rotate tokens periodically and restrict scopes to the minimum needed for your automation.

Troubleshooting

If the server fails to start, verify that Node.js is installed and that the path to index.js is correct. Check that GITLAB_API_URL points to your GitLab instance and that the access token has the required scopes. Review logs from the running process for any authentication or API errors.

Available tools

search_repositories

Search for GitLab projects based on query terms and filters.

get_file_contents

Retrieve the contents of a file or directory within a GitLab project.

create_or_update_file

Create a new file or update an existing file in a repository.

push_files

Push multiple files in a single commit to a repository.

create_repository

Create a new GitLab project.

create_issue

Create a new issue in a GitLab project.

create_merge_request

Create a new merge request for a branch or commit.

fork_repository

Fork a GitLab project into your account.

create_branch

Create a new branch in a repository.

Built by

VeilStrat

AI signals for GTM teams