Evan
c25a321e88
* fix: pin npm package versions in MCP integration templates Prevent supply chain attacks by pinning exact versions instead of using unpinned `npx -y @package` which pulls latest on every run. 23 of 25 integrations pinned. sqlite-mcp and aws skipped (packages not found on npm registry). * fix: use stable azure/mcp version instead of beta
29 lines
969 B
TOML
29 lines
969 B
TOML
id = "gitlab"
|
|
name = "GitLab"
|
|
description = "Access GitLab projects, merge requests, issues, and CI/CD pipelines through the MCP server"
|
|
category = "devtools"
|
|
icon = "🦊"
|
|
tags = ["git", "vcs", "code", "merge-requests", "ci", "devops"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@modelcontextprotocol/server-gitlab@2025.4.25"]
|
|
|
|
[[required_env]]
|
|
name = "GITLAB_PERSONAL_ACCESS_TOKEN"
|
|
label = "GitLab Personal Access Token"
|
|
help = "A personal access token with api scope from your GitLab instance"
|
|
is_secret = true
|
|
get_url = "https://gitlab.com/-/user_settings/personal_access_tokens"
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Navigate to GitLab > User Settings > Access Tokens (https://gitlab.com/-/user_settings/personal_access_tokens).
|
|
2. Create a new personal access token with the 'api' scope and an appropriate expiration date.
|
|
3. Paste the token into the GITLAB_PERSONAL_ACCESS_TOKEN field above.
|
|
"""
|