Repocollab

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

GitLab projects, branches, files, issues and merge requests via the GitLab REST API.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

Repocollab's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Repocollab in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

repocollab

repocollab puts the everyday GitLab project workflow behind an MCP server: find a project, create or fork one, cut a branch, read and write files, and open and track issues and merge requests. It is a core subset of the documented GitLab MCP surface — the twelve tools an agent reaches for most — talking to the GitLab REST v4 API.

Authentication is a personal access token in GITLAB_PERSONAL_ACCESS_TOKEN, sent as a Bearer token. By default the server talks to https://gitlab.com/api/v4; point GITLAB_API_URL at a self-managed instance to use that instead. A project_id is a string throughout: either the numeric project id or the URL-encoded project path both work.

Install

bash
npx @reneturcios/repocollab search_repositories --search my-projectdocker run -i -e GITLAB_PERSONAL_ACCESS_TOKEN ghcr.io/cloudcorprecords/repocollab

CLI

bash
repocollab search_repositories --search my-projectrepocollab create_repository --name demo --visibility privaterepocollab get_file_contents --project-id group/demo --file-path README.md --ref mainrepocollab create_issue --project-id 42 --title "Bug report" --labels bugrepocollab list_merge_requests --project-id 42 --state openedrepocollab --version

Exit codes: 0 success, 1 API error, 2 usage error.

MCP server

bash
npx -y @reneturcios/repocollab mcp
json
{  "mcpServers": {    "repocollab": {      "command": "npx",      "args": ["-y", "@reneturcios/repocollab", "mcp"],      "env": { "GITLAB_PERSONAL_ACCESS_TOKEN": "glpat-..." }    }  }}

Tools

ToolRequiredOptional
search_repositoriessearch—
create_repositorynamedescription, visibility
fork_repositoryproject_idnamespace
create_branchproject_id, branchref
get_file_contentsproject_id, file_pathref
create_or_update_fileproject_id, file_path, content, commit_message, branchprevious_path
create_issueproject_id, titledescription, labels
list_issuesproject_idstate, per_page, page
get_issueproject_id, issue_iid—
create_merge_requestproject_id, title, source_branch, target_branchdescription
list_merge_requestsproject_idstate, per_page, page
get_merge_requestproject_id, merge_request_iid—

create_or_update_file checks whether the file already exists on the target branch and creates it (POST) or updates it (PUT) accordingly. A missing token is reported as a tool error naming GITLAB_PERSONAL_ACCESS_TOKEN; upstream HTTP errors surface with their status and GitLab's message.

Out of scope in this subset: pipelines and CI, wiki, snippets, milestones, label/epic management, user and group administration, protected branches, repository tree/archive/compare detail, merge request approvals, discussions and notes beyond get_merge_request, and search beyond projects.

Development

bash
npm installnpm run buildnpm testnpm run dev

Tests run entirely on fake-fetch fixtures; no network is used.

License

MIT — see LICENSE.

Source: README.md at commit ca9b0ca

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts