GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
GITLAB_PERSONAL_ACCESS_TOKENAPI keyrequiredGitLab personal access token for local stdio use. Create a token with the GitLab scopes needed by the tools you plan to use, such as api or read_api.
GITLAB_JOB_TOKENAPI keyoptionalOptional GitLab CI job token to use instead of a personal access token when running inside GitLab CI.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
merge_merge_requestNo description publishedThis tool published no description. Forge does not invent one.
approve_merge_requestNo description publishedThis tool published no description. Forge does not invent one.
unapprove_merge_requestNo description publishedThis tool published no description. Forge does not invent one.
get_merge_request_approval_stateNo description publishedThis tool published no description. Forge does not invent one.
get_merge_request_conflictsNo description publishedThis tool published no description. Forge does not invent one.
list_merge_request_pipelinesNo description publishedThis tool published no description. Forge does not invent one.
execute_graphqlprivilegedNo description publishedThis tool published no description. Forge does not invent one.
create_or_update_fileNo description publishedThis tool published no description. Forge does not invent one.
search_repositoriesNo description publishedThis tool published no description. Forge does not invent one.
create_repositoryNo description publishedThis tool published no description. Forge does not invent one.
create_groupNo description publishedThis tool published no description. Forge does not invent one.
get_file_contentsNo description publishedThis tool published no description. Forge does not invent one.
push_filesNo description publishedThis tool published no description. Forge does not invent one.
create_issueNo description publishedThis tool published no description. Forge does not invent one.
create_merge_requestNo description publishedThis tool published no description. Forge does not invent one.
fork_repositoryNo description publishedThis tool published no description. Forge does not invent one.
create_branchNo description publishedThis tool published no description. Forge does not invent one.
get_branchNo description publishedThis tool published no description. Forge does not invent one.
list_branchesNo description publishedThis tool published no description. Forge does not invent one.
delete_branchprivilegedNo description publishedThis tool published no description. Forge does not invent one.
list_protected_branchesNo description publishedThis tool published no description. Forge does not invent one.
get_protected_branchNo description publishedThis tool published no description. Forge does not invent one.
protect_branchNo description publishedThis tool published no description. Forge does not invent one.
unprotect_branchNo description publishedThis tool published no description. Forge does not invent one.
update_default_branchNo description publishedThis tool published no description. Forge does not invent one.
get_merge_requestNo description publishedThis tool published no description. Forge does not invent one.
get_merge_request_diffsNo description publishedThis tool published no description. Forge does not invent one.
list_merge_request_changed_filesNo description publishedThis tool published no description. Forge does not invent one.
list_merge_request_diffsNo description publishedThis tool published no description. Forge does not invent one.
get_merge_request_file_diffNo description publishedThis tool published no description. Forge does not invent one.
list_merge_request_versionsNo description publishedThis tool published no description. Forge does not invent one.
get_merge_request_versionNo description publishedThis tool published no description. Forge does not invent one.
get_branch_diffsNo description publishedThis tool published no description. Forge does not invent one.
update_merge_requestNo description publishedThis tool published no description. Forge does not invent one.
create_noteNo description publishedThis tool published no description. Forge does not invent one.
create_merge_request_threadNo description publishedThis tool published no description. Forge does not invent one.
resolve_merge_request_threadNo description publishedThis tool published no description. Forge does not invent one.
mr_discussionsNo description publishedThis tool published no description. Forge does not invent one.
delete_merge_request_discussion_noteprivilegedNo description publishedThis tool published no description. Forge does not invent one.
update_merge_request_discussion_noteNo description publishedThis tool published no description. Forge does not invent one.
0 of 40 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.