MCP Gitlab
PYPI · MCP-GITLAB-CRUNCHTOOLS
Secure MCP server for GitLab projects, merge requests, issues, and pipelines
Available components
Last scanned (1 day ago)
Scores higher than 80% of PyPI servers
Category Version Control
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to crunchtools/mcp-gitlab). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4923 tokens (~78/item across 63 items; 63 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_project_tool" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/mcp-gitlab-crunchtools@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | crunchtools/mcp-gitlab |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/crunchtools/mcp-gitlab/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 1008249759 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9e4ad0dbf024cae0a507f4cf9c4b7d7aa9aa1a0c647b2f88bff6d9fd6a14d723 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_repository_tree_tool List Repository Tree Tool ~106
List repository tree (files and directories).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default: 1) |
| path | string | – | Path inside the repository (default: root) |
| per_page | integer | – | Results per page, max 100 (default: 20) |
| project_id | string | yes | Project ID or path |
| recursive | boolean | – | List files recursively |
| ref | – | – | Branch, tag, or commit SHA (default: default branch) |
Structured output declared, but exposes no named fields.
No examples provided.
list_snippets_tool List Snippets Tool ~64
List snippets for a GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default: 1) |
| per_page | integer | – | Results per page, max 100 (default: 20) |
| project_id | string | yes | Project ID or path |
Structured output declared, but exposes no named fields.
No examples provided.
list_users_tool List Users Tool ~84
List GitLab users.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Only return active users (default: true) |
| page | integer | – | Page number (default: 1) |
| per_page | integer | – | Results per page, max 100 (default: 20) |
| search | – | – | Search for users by name or email |
| username | – | – | Filter by exact username |
Structured output declared, but exposes no named fields.
No examples provided.
list_wiki_pages_tool List Wiki Pages Tool ~83
List wiki pages for a GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default: 1) |
| per_page | integer | – | Results per page, max 100 (default: 20) |
| project_id | string | yes | Project ID or path |
| with_content | boolean | – | Include page content in response (default: false) |
Structured output declared, but exposes no named fields.
No examples provided.
retry_job_tool Retry Job Tool ~39
Retry a specific failed CI/CD job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Job ID |
| project_id | string | yes | Project ID or path |
Structured output declared, but exposes no named fields.
No examples provided.
retry_pipeline_tool Retry Pipeline Tool ~41
Retry all failed jobs in a CI/CD pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_id | integer | yes | Pipeline ID |
| project_id | string | yes | Project ID or path |
Structured output declared, but exposes no named fields.
No examples provided.
search_global_tool Search Global Tool ~98
Search across all GitLab resources accessible by the token.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default: 1) |
| per_page | integer | – | Results per page, max 100 (default: 20) |
| scope | string | – | Search scope (projects, issues, merge_requests, milestones, snippet_titles, wiki_blobs, commits, blobs, notes, users) |
| search | string | yes | Search query string |
Structured output declared, but exposes no named fields.
No examples provided.
search_project_tool Search Project Tool ~100
Search within a specific GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default: 1) |
| per_page | integer | – | Results per page, max 100 (default: 20) |
| project_id | string | yes | Project ID or path |
| scope | string | – | Search scope (issues, merge_requests, milestones, wiki_blobs, commits, blobs, notes) |
| search | string | yes | Search query string |
Structured output declared, but exposes no named fields.
No examples provided.
update_file_tool Update File Tool ~96
Update an existing file in a GitLab repository.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | Branch to commit to |
| commit_message | string | yes | Commit message |
| content | string | yes | New file content |
| encoding | string | – | Content encoding - "text" or "base64" (default: text) |
| file_path | string | yes | Path to the file |
| project_id | string | yes | Project ID or path |
Structured output declared, but exposes no named fields.
No examples provided.
update_issue_tool Update Issue Tool ~106
Update an existing issue.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_ids | – | – | User IDs to assign |
| confidential | – | – | Whether the issue is confidential |
| description | – | – | Issue description (Markdown) |
| issue_iid | integer | yes | Issue internal ID |
| labels | – | – | Comma-separated label names |
| milestone_id | – | – | Milestone ID |
| project_id | string | yes | Project ID or path |
| state_event | – | – | State transition (close, reopen) |
| title | – | – | Issue title |
Structured output declared, but exposes no named fields.
No examples provided.
update_label_tool Update Label Tool ~73
Update an existing label in a GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| color | – | – | New color hex code |
| description | – | – | New description |
| label_id | integer | yes | Label ID |
| new_name | – | – | New label name |
| priority | – | – | New priority |
| project_id | string | yes | Project ID or path |
Structured output declared, but exposes no named fields.
No examples provided.
update_merge_request_tool Update Merge Request Tool ~130
Update an existing merge request.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_ids | – | – | User IDs to assign |
| description | – | – | MR description (Markdown) |
| labels | – | – | Comma-separated label names |
| merge_request_iid | integer | yes | Merge request internal ID |
| milestone_id | – | – | Milestone ID |
| project_id | string | yes | Project ID or path |
| remove_source_branch | – | – | Remove source branch after merge |
| reviewer_ids | – | – | User IDs to review |
| state_event | – | – | State transition (close, reopen) |
| target_branch | – | – | Target branch |
| title | – | – | MR title |
Structured output declared, but exposes no named fields.
No examples provided.
update_milestone_tool Update Milestone Tool ~93
Update an existing milestone.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | New description (Markdown) |
| due_date | – | – | New due date (YYYY-MM-DD) |
| milestone_id | integer | yes | Milestone ID |
| project_id | string | yes | Project ID or path |
| start_date | – | – | New start date (YYYY-MM-DD) |
| state_event | – | – | State transition (close, activate) |
| title | – | – | New title |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the MCP Gitlab server?
MCP Gitlab runs locally as a PyPI package, launched with uvx mcp-gitlab-crunchtools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-gitlab-crunchtools
claude mcp add crunchtools-gitlab -- uvx mcp-gitlab-crunchtools
What is the MCP Gitlab server?
MCP Gitlab is listed in the public MCP registry as io.github.crunchtools/gitlab. Secure MCP server for GitLab projects, merge requests, issues, and pipelines. This page covers its PyPI package (mcp-gitlab-crunchtools).
Is the MCP Gitlab server safe to use?
MCP Gitlab scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Gitlab server expose?
MCP Gitlab exposes 63 tools: list_projects_tool, get_project_tool, list_project_branches_tool, get_project_branch_tool, list_project_commits_tool, and 58 more. Their descriptions and schemas cost roughly 4,895 tokens of context every time the server is loaded.
Is the MCP Gitlab server still maintained?
MCP Gitlab is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Gitlab server under?
MCP Gitlab declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.