Labsco
MCP SERVER

Work a GitLab project from the conversation — read files, push a commit, open a branch, raise an issue or a merge request.

Git Hosting & Code Review
Summary
A fixed GitLab server with the whole change flow in it.

It carries the ordinary GitLab operations — read, commit, branch, issue, merge request — and repairs the schema validation bug that made repository search fail in the standard implementation.

What it is

A GitLab client covering search, file reads and the write path through to merge requests. It is a corrected implementation: the schema validation that broke search_repositories in the standard GitLab server is fixed here.

What you get
  • GitLab projects searched by name
  • File or directory contents read out of a repository
  • A single file created or updated, or several files pushed in one commit
  • New projects created and existing ones forked
  • Branches created
  • Issues and merge requests opened
Requirements

Node.js v14 or higher and a GitLab personal access token scoped to what you need — api for full access, or read_api, read_repository and write_repository for narrower ones. The token and the GitLab API base URL both go in your client config, so self-hosted instances work.