MCP.so
Sign In

Custom GitLab MCP Server

@chris-miaskowski

About Custom GitLab MCP Server

No overview available yet

Basic information

Category

Version Control

Runtime

node

Transports

stdio

Publisher

chris-miaskowski

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

9

Search for GitLab projects

Get contents of a file or directory

Create or update a single file

Push multiple files in a single commit

Create a new GitLab project

Create a new issue

Create a new merge request

Fork a project

Create a new branch

Overview

What is Custom GitLab MCP Server?

Custom GitLab MCP Server is an implementation of the Model Context Protocol (MCP) that enables AI assistants like Claude to interact with GitLab repositories. It fixes schema validation issues present in the standard GitLab MCP server, specifically for the search_repositories tool. This server is for developers who want to search, read, create, and update GitLab resources through AI-powered workflows.

How to use Custom GitLab MCP Server?

Clone the repository, run npm install, then configure the server in your Claude settings file (either claude_desktop_config.json or the application settings JSON). Set the command to node, provide the path to index.js, and supply environment variables GITLAB_PERSONAL_ACCESS_TOKEN and GITLAB_API_URL (pointing to your GitLab instance). No additional invocation commands beyond the standard MCP server configuration are documented.

Key features of Custom GitLab MCP Server

  • Search GitLab repositories
  • Fetch file or directory contents
  • Create or update single files
  • Push multiple files in a single commit
  • Create new GitLab projects
  • Create issues and merge requests
  • Fork repositories and create branches

Use cases of Custom GitLab MCP Server

  • Use an AI assistant to search for GitLab projects and retrieve code files
  • Automate file creation and updates across multiple repositories via natural language prompts
  • Manage GitLab issues and merge requests directly from a conversational interface
  • Fork and branch projects without leaving your MCP‑compatible assistant

FAQ from Custom GitLab MCP Server

How does Custom GitLab MCP Server differ from the standard GitLab MCP server?

It fixes schema validation issues present in the standard implementation, specifically for the search_repositories tool.

What are the runtime requirements?

Node.js version 14 or higher is required. You also need a GitLab Personal Access Token with appropriate scopes.

What GitLab access token scopes are needed?

Use api for full API access, read_api for read‑only access, and read_repository / write_repository for repository operations.

Where does the server connect to?

It connects to any GitLab instance via the GITLAB_API_URL environment variable (e.g., https://your-gitlab-instance/api/v4).

Which MCP transport does the server use?

The server uses standard MCP transport as configured in the Claude settings file; it is started as a child process with environment variables.

Comments

More Version Control MCP servers