67
/ 100
25 days ago
glama

GitLab MCP

Exposes the GitLab REST API to MCP clients for managing projects, issues, merge requests, repositories, and CI/CD pipelines. It is multi-tenant, allowing each user to authenticate with their own token and instance URL.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: GITLAB_TOKEN, GITLAB_PRIVATE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configMCP_TRANSPORTe =streamable-http \
🔐 secretGITLAB_TOKEN, GITLAB_URL
🔐 secretGITLAB_PRIVATE_TOKEN
configGITLAB_URLGITLAB_TOKEN,
configMCP_HOST0.0.0.0 Bind host for networked transports
configMCP_PORT8000 Bind port for networked transports
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/shahabmosavi-gitlab-mcp-thxr7h)](https://m8ven.ai/mcp/shahabmosavi-gitlab-mcp-thxr7h)
commit: 18f45ccf36ad858792c3dfe6ed7bf36ebae1817f
code hash: 03e0706546ce83b74eb791e127b7fe3ee2c439dfa03b877e1ab83d5aec2f5ab3
verified: 7/6/2026, 10:39:16 AM
view raw JSON →