Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/gitlab

PYPI · MCPARMORY-GITLAB · 2 COMPONENTS · SCANNED SEP 20

Manage projects, groups, branches, merge requests, and CI/CD pipelines

−15 this week 62 Trust /100
Trust breakdown (7 categories)

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 Security37
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Install-script risk not yet assessed.Unverified
  • 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 5140 tokens (~96/item across 53 items; 53 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety98
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 10 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_manual_job" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 53 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
Install

How do I install the com.mcparmory/gitlab MCP server?

com.mcparmory/gitlab runs locally as a PyPI package, launched with uvx mcparmory-gitlab. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-gitlab

# add to Claude Code
claude mcp add com-mcparmory-gitlab -- uvx mcparmory-gitlab
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-gitlab": {
      "command": "uvx",
      "args": [
        "mcparmory-gitlab"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-gitlab": {
      "command": "uvx",
      "args": [
        "mcparmory-gitlab"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-gitlab -- uvx mcparmory-gitlab
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-gitlab": {
      "type": "local",
      "command": [
        "uvx",
        "mcparmory-gitlab"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mcparmory-gitlab --command uvx --arg mcparmory-gitlab
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-gitlab:
    command: "uvx"
    args: ["mcparmory-gitlab"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-gitlab": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcparmory-gitlab"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-mcparmory-gitlab -t stdio -c uvx -a mcparmory-gitlab
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-gitlab": {
      "command": "uvx",
      "args": [
        "mcparmory-gitlab"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +16
    • Malware scan: unverified → pass security
  • 11 Sept 26 −18
    • Malware scan: pass → unverified security
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 2026 · Analysed pypi/mcparmory-gitlab@1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Dependencies 46 packages
Packages resolved 46
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 53 exposed · ~5,140 tokens

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 →

Tool Tokens
add_group_badge ~177

Adds a badge to a group to display custom branding or status indicators. The badge will be visible on the group's profile page.

NameTypeReqDescription
idstringyesThe ID or URL-encoded path of the group. You can use either the numeric group ID or the full URL-encoded group path (e.g., 'my-group' or 'parent-group%2Fchild-group').
image_urlstringyesThe URL of the badge image to display. This should be a valid HTTP or HTTPS URL pointing to an image file.
link_urlstringyesThe URL where the badge image links to when clicked. This should be a valid HTTP or HTTPS URL.
namestringA descriptive name for the badge to help identify its purpose. This is displayed as alt text and in the group's badge management interface.

No output schema declared.

No examples provided.

add_kubernetes_cluster ~252

Register an existing Kubernetes cluster as an instance cluster in GitLab. This allows GitLab to deploy applications and manage resources on the cluster.

NameTypeReqDescription
domainstringThe base domain for applications deployed to this cluster.
enabledbooleanWhether the cluster is active and available for deployments.
environment_scopestringThe environment scope this cluster is associated with, such as production or staging. Use * to match all environments.
managedbooleanWhether GitLab automatically manages Kubernetes namespaces and service accounts for this cluster.
management_project_idstringThe GitLab project ID that will manage this cluster's namespaces and service accounts.
namestringyesThe display name for the Kubernetes cluster.
namespace_per_environmentbooleanWhether to deploy each environment to its own isolated Kubernetes namespace for better resource separation and security.
platform_kubernetes_attributes_api_urlstringyesThe URL endpoint to access the Kubernetes API server.
platform_kubernetes_attributes_authorization_typestringThe authorization mechanism used by the Kubernetes cluster for access control.
platform_kubernetes_attributes_tokenstringyesThe authentication token or bearer token used to authenticate requests to the Kubernetes API.

No output schema declared.

No examples provided.

approve_access_request ~110

Approves a pending access request for a user to join the project. Optionally specify the access level to grant; defaults to Developer role.

NameTypeReqDescription
access_levelstringThe access level to grant the user upon approval. Valid levels range from 10 (Guest) to 50 (Owner).
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.
user_idstringyesThe user ID of the person whose access request is being approved.

No output schema declared.

No examples provided.

approve_group_access_request ~138

Approves a pending access request for a user to join a group. The authenticated user must own the group to perform this action.

NameTypeReqDescription
access_levelstringThe access level to grant the user upon approval. Specifies the user's role and permissions within the group (e.g., Developer, Maintainer).
idstringyesThe ID or URL-encoded path of the group. Use the numeric group ID or the full URL-encoded path (e.g., 'my-group' or 'parent-group%2Fmy-group').
user_idstringyesThe numeric ID of the user whose access request is being approved.

No output schema declared.

No examples provided.

check_branch_exists ~84

Verify whether a specific branch exists in a project repository. Returns a successful response if the branch is found, otherwise returns a 404 error.

NameTypeReqDescription
branchstringyesThe name of the branch to check for existence in the repository.
idstringyesThe project identifier, which can be either the numeric project ID or the URL-encoded path of the project.

No output schema declared.

No examples provided.

create_branch ~111

Create a new branch in a project from a specified commit SHA or existing branch. The new branch will be created with the given name and point to the specified reference.

NameTypeReqDescription
branchstringyesThe name for the new branch to be created.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., group%2Fproject for group/project).
refstringyesThe commit SHA or existing branch name from which to create the new branch.

No output schema declared.

No examples provided.

create_instance_variable ~181

Create a new instance-level CI/CD variable that is available to all projects. Instance variables are useful for storing secrets and configuration values needed across your entire GitLab instance.

NameTypeReqDescription
keystringyesThe unique identifier for the variable. Maximum 255 characters.
maskedbooleanWhen enabled, the variable value is masked in job logs and API responses to prevent accidental exposure of sensitive data.
protectedbooleanWhen enabled, the variable is only available to protected branches and tags, preventing exposure in unprotected environments.
rawbooleanWhen enabled, the variable value is treated as a literal string and not expanded. When disabled, variable references are expanded during job execution.
valuestringyesThe value assigned to the variable.
variable_typestringSpecifies whether the variable stores an environment value or a file path.

No output schema declared.

No examples provided.

create_project_badge ~113

Adds a new badge to a project. Badges are visual indicators that can link to external URLs and are displayed on the project page.

NameTypeReqDescription
idstringyesThe ID or URL-encoded path of the project. Accepts both integer IDs and string paths.
image_urlstringyesThe URL of the badge image to display.
link_urlstringyesThe URL that the badge links to when clicked.
namestringA descriptive name for the badge to identify its purpose.

No output schema declared.

No examples provided.

delete_alert_metric_image ~100

Remove a metric image associated with an alert in a project. This operation permanently deletes the specified metric image from the alert's collection.

NameTypeReqDescription
alert_iidstringyesThe internal ID (IID) of the alert from which to remove the metric image.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.
metric_image_idstringyesThe numeric ID of the metric image to delete.

No output schema declared.

No examples provided.

delete_application ~39

Permanently delete a specific application by its ID. This action cannot be undone.

NameTypeReqDescription
idstringyesThe unique identifier of the application to delete.

No output schema declared.

No examples provided.

delete_badge ~82

Removes a badge from a project. This operation permanently deletes the specified badge and its association with the project.

NameTypeReqDescription
badge_idstringyesThe unique identifier of the badge to remove from the project.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., group%2Fproject for group/project).

No output schema declared.

No examples provided.

delete_branch ~64

Delete a branch from a project repository. This operation permanently removes the specified branch.

NameTypeReqDescription
branchstringyesThe name of the branch to delete.
idstringyesThe project identifier, which can be either the numeric project ID or the URL-encoded project path.

No output schema declared.

No examples provided.

delete_broadcast_message ~46

Delete a broadcast message by its ID. This operation permanently removes the specified broadcast message from the system.

NameTypeReqDescription
idstringyesThe unique identifier of the broadcast message to delete.

No output schema declared.

No examples provided.

delete_cluster ~50

Delete an instance cluster from GitLab. This removes the cluster configuration but does not delete any resources within the connected Kubernetes cluster itself.

NameTypeReqDescription
cluster_idstringyesThe unique identifier of the cluster to delete.

No output schema declared.

No examples provided.

delete_instance_variable ~49

Delete an instance-level CI/CD variable by its key. This removes the variable from the GitLab instance configuration.

NameTypeReqDescription
keystringyesThe unique identifier key of the instance-level variable to delete.

No output schema declared.

No examples provided.

delete_merged_branches ~72

Delete all branches that have been merged into the project's default branch. This operation permanently removes merged branches to clean up the repository.

NameTypeReqDescription
idstringyesThe project identifier, which can be either the numeric project ID or the URL-encoded project path (e.g., group%2Fproject-name).

No output schema declared.

No examples provided.

deny_access_request ~81

Denies an access request from a user for the specified project. This removes the user's pending access request and prevents them from gaining project access through this request.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.
user_idstringyesThe numeric ID of the user whose access request should be denied.

No output schema declared.

No examples provided.

deny_group_access_request ~84

Denies an access request from a user to join a group. The access request is removed and the user is not granted group membership.

NameTypeReqDescription
idstringyesThe ID or URL-encoded path of the group. This identifies which group's access request should be denied.
user_idstringyesThe user ID of the person whose access request is being denied.

No output schema declared.

No examples provided.

execute_manual_job ~109

Execute a manual job for a project. Optionally provide custom variables to override job defaults during execution.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., group%2Fproject for group/project).
job_idintegeryesThe numeric ID of the manual job to execute.
job_variables_attributesarrayOptional array of custom variables to make available to the job during execution. Variables are applied in the order provided.

No output schema declared.

No examples provided.

get_admin_ci_variable ~55

Retrieve the details of a specific instance-level CI/CD variable by its key. This operation returns the variable's configuration and metadata.

NameTypeReqDescription
keystringyesThe unique identifier key of the instance-level CI/CD variable to retrieve.

No output schema declared.

No examples provided.

get_branch ~73

Retrieve details for a specific branch in a repository. Returns branch information including commit details and protection status.

NameTypeReqDescription
branchstringyesThe name of the branch to retrieve.
idstringyesThe project identifier, which can be a numeric ID or URL-encoded project path (e.g., group/subgroup/project).

No output schema declared.

No examples provided.

get_broadcast_message ~46

Retrieve a specific broadcast message by its ID. Broadcast messages are system-wide announcements visible to all users.

NameTypeReqDescription
idstringyesThe unique identifier of the broadcast message to retrieve.

No output schema declared.

No examples provided.

get_bulk_import ~45

Retrieve details about a GitLab Migration bulk import job, including its status and progress information.

NameTypeReqDescription
import_idstringyesThe unique identifier of the bulk import migration to retrieve.

No output schema declared.

No examples provided.

get_cluster ~47

Retrieve details for a single instance cluster by its ID. This operation requires GitLab 13.2 or later.

NameTypeReqDescription
cluster_idstringyesThe unique identifier of the cluster to retrieve.

No output schema declared.

No examples provided.

get_group_badge ~82

Retrieves a specific badge belonging to a group. This allows you to fetch details about a badge that has been assigned to a group.

NameTypeReqDescription
badge_idstringyesThe unique identifier of the badge within the group.
idstringyesThe ID or URL-encoded path of the group. This identifies which group owns the badge you want to retrieve.

No output schema declared.

No examples provided.

get_job ~78

Retrieve details for a specific job within a project. Returns comprehensive job information including status, logs, and execution details.

NameTypeReqDescription
idstringyesThe project identifier, which can be a numeric ID or URL-encoded project path (e.g., group/subgroup/project).
job_idintegeryesThe numeric identifier of the job to retrieve.

No output schema declared.

No examples provided.

get_migration_entity ~85

Retrieve detailed information about a specific entity within a GitLab Migration. This allows you to inspect the status and properties of individual migrated items.

NameTypeReqDescription
entity_idstringyesThe unique identifier of the specific entity within the migration whose details you want to retrieve.
import_idstringyesThe unique identifier of the GitLab Migration batch containing the entity you want to retrieve.

No output schema declared.

No examples provided.

get_project_badge ~83

Retrieve a specific badge associated with a project. This allows you to fetch details about a project badge by its ID.

NameTypeReqDescription
badge_idstringyesThe unique identifier of the badge to retrieve.
idstringyesThe project identifier, which can be either the numeric project ID or the URL-encoded project path (e.g., group/subgroup/project).

No output schema declared.

No examples provided.

get_user_avatar ~77

Retrieve the avatar URL for a user based on their email address. Optionally specify a custom image size for the avatar.

NameTypeReqDescription
emailstringyesThe public email address of the user whose avatar should be retrieved.
sizestringThe width and height in pixels for the returned avatar image. Larger sizes provide higher resolution avatars.

No output schema declared.

No examples provided.

list_access_requests ~78

Retrieves a list of access requests for a project. Access requests allow users to request membership in a project.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., group%2Fproject).
per_pagestringNumber of access requests to return per page for pagination.

No output schema declared.

No examples provided.

list_alert_metric_images ~77

Retrieve metric images associated with a specific alert in a project. Metric images provide visual context for alert conditions and their impact.

NameTypeReqDescription
alert_iidstringyesThe internal ID of the alert for which to retrieve associated metric images.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.

No output schema declared.

No examples provided.

list_clusters ~34

Retrieve a list of all instance clusters configured in GitLab. This operation provides an overview of cluster infrastructure available at the instance level.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_group_access_requests ~82

Retrieves a paginated list of pending access requests for a group. This allows group owners to review and manage user requests to join the group.

NameTypeReqDescription
idstringyesThe ID or URL-encoded path of the group. This identifies which group's access requests to retrieve.
per_pagestringNumber of access requests to return per page for pagination.

No output schema declared.

No examples provided.

list_group_badges ~100

Retrieves a paginated list of badges for a group that are viewable by the authenticated user. Introduced in GitLab 10.6.

NameTypeReqDescription
idstringyesThe ID or URL-encoded path of the group. This identifies which group's badges to retrieve.
namestringFilter badges by name. Returns only badges matching the specified name.
per_pagestringNumber of badges to return per page for pagination.

No output schema declared.

No examples provided.

list_instance_variables ~60

Retrieve all instance-level CI/CD variables available across the GitLab instance. These variables are accessible to all projects and groups.

NameTypeReqDescription
per_pagestringMaximum number of variables to return per page. Use this to control pagination when retrieving large result sets.

No output schema declared.

No examples provided.

list_jobs ~99

Retrieve all jobs for a specified project, with optional filtering by job status. Use this to monitor job execution, track pipeline progress, or retrieve job details.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded project path (e.g., group/subgroup/project).
scopearrayFilter results to include only jobs with the specified statuses. Provide as an array of status values; order is not significant.

No output schema declared.

No examples provided.

list_migration_entities ~100

Retrieve a list of entities from a GitLab Migration import job. Filter by status and paginate through results to monitor migration progress.

NameTypeReqDescription
import_idstringyesThe unique identifier of the GitLab Migration import job to retrieve entities from.
per_pagestringNumber of entities to return per page for pagination. Defaults to 20 items per page.
statusstringFilter entities by their current processing status in the migration workflow.

No output schema declared.

No examples provided.

list_migration_entities_all ~104

Retrieve a list of all entities from GitLab Migrations. This operation supports pagination, sorting, and filtering by migration status to help track the progress of bulk import operations.

NameTypeReqDescription
per_pagestringMaximum number of entities to return per page for pagination purposes.
sortstringOrder in which to sort the returned entities by creation date.
statusstringFilter entities by their current migration status to view only those in a specific state.

No output schema declared.

No examples provided.

list_migrations ~88

Retrieve a list of all GitLab Migrations with optional filtering and sorting. This feature was introduced in GitLab 14.1.

NameTypeReqDescription
per_pagestringNumber of migration records to return per page for pagination.
sortstringSort migrations by creation date in ascending or descending order.
statusstringFilter migrations by their current status in the migration lifecycle.

No output schema declared.

No examples provided.

list_project_badges ~111

Retrieves a paginated list of badges for a project that are visible to the authenticated user. This endpoint was introduced in GitLab 10.6.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., group%2Fproject for group/project).
namestringFilter badges by name. Returns only badges whose name matches the provided value.
per_pagestringNumber of badges to return per page for pagination.

No output schema declared.

No examples provided.

list_repository_branches ~107

Retrieve a list of branches from a project's repository. Supports pagination and sorting by branch name or last update time.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., 'group%2Fproject').
per_pagestringNumber of branches to return per page for pagination.
sortstringSort the returned branches by name in ascending order, or by last update time in ascending or descending order.

No output schema declared.

No examples provided.

pause_batched_background_migration ~80

Pause an active batched background migration by its ID. The migration can be resumed later from where it was paused.

NameTypeReqDescription
databasestringThe database instance where the batched background migration is running. Defaults to 'main' if not specified.
idstringyesThe unique identifier of the batched background migration to pause.

No output schema declared.

No examples provided.

protect_branch ~101

Protect a branch by restricting push and merge permissions. Configure whether developers can push to or merge into the specified branch.

NameTypeReqDescription
branchstringyesThe name of the branch to protect.
developers_can_mergebooleanAllow developers to merge pull requests into this branch.
developers_can_pushbooleanAllow developers to push commits to this branch.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.

No output schema declared.

No examples provided.

remove_group_badge ~81

Removes a badge from a group. This allows administrators to delete badges that are no longer needed or relevant to the group.

NameTypeReqDescription
badge_idstringyesThe unique identifier of the badge to remove from the group.
idstringyesThe ID or URL-encoded path of the group. This identifies which group the badge should be removed from.

No output schema declared.

No examples provided.

request_group_access ~56

Submit an access request for the authenticated user to join a group. The group owner can then review and approve or deny the request.

NameTypeReqDescription
idstringyesThe ID or URL-encoded path of the group to request access for.

No output schema declared.

No examples provided.

request_project_access ~72

Request access to a project as the authenticated user. This allows users to formally request membership or elevated permissions for a project they don't currently have access to.

NameTypeReqDescription
idstringyesThe project identifier, either as a numeric ID or URL-encoded path (e.g., group%2Fproject for group/project).

No output schema declared.

No examples provided.

start_bulk_migration ~309

Initiate a bulk migration of GitLab entities from a source instance to the destination. This operation supports migrating groups and projects with their nested resources between GitLab instances.

NameTypeReqDescription
configuration_access_tokenstringyesPersonal access token or project access token from the source GitLab instance with sufficient permissions to read the entities being migrated
configuration_urlstringyesURL of the source GitLab instance to migrate from (e.g., https://source.gitlab.com)
entities_destination_namespacearrayyesArray of destination namespaces where entities will be imported. Each namespace corresponds to the entity at the same index. Specify the target group or namespace path on the destination instance
entities_destination_slugarrayArray of optional destination slugs for imported entities. When provided, overrides the default slug derived from the source entity name. Each slug corresponds to the entity at the same index
entities_migrate_projectsarrayArray of boolean flags indicating whether to include nested projects during group migration. Each flag corresponds to the group at the same index in entities_source_type
entities_source_full_patharrayyesArray of relative paths for source entities to import. Each path corresponds to the entity at the same index in entities_source_type. Paths should be in the format of full project or group paths on t…
entities_source_typearrayyesArray of entity types to migrate from the source instance. Each element specifies the type of resource (group or project) being imported

No output schema declared.

No examples provided.

unprotect_branch ~88

Remove protection from a branch in a project, allowing it to be modified or deleted. This operation reverses any branch protection rules that were previously applied.

NameTypeReqDescription
branchstringyesThe name of the branch to unprotect.
idstringyesThe project identifier, which can be either the numeric project ID or the URL-encoded project path (e.g., group/subgroup/project).

No output schema declared.

No examples provided.

update_alert_metric_image ~128

Update the metric image associated with an alert, including its display URL and descriptive text for reference.

NameTypeReqDescription
alert_iidstringyesThe internal ID of the alert containing the metric image.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.
metric_image_idstringyesThe unique identifier of the metric image to update.
urlstringThe URL where the metric image or additional metric information can be viewed.
url_textstringA descriptive label or caption for the metric image or its associated URL.

No output schema declared.

No examples provided.

update_cluster ~182

Update an existing instance cluster configuration. Modify cluster settings such as name, connectivity status, environment scope, and management preferences.

NameTypeReqDescription
cluster_idstringyesThe unique identifier of the cluster to update.
domainstringThe base domain for the cluster, used for generating application URLs.
enabledbooleanEnable or disable GitLab's connection to the Kubernetes cluster.
environment_scopestringThe environment associated with this cluster deployment.
managedbooleanWhen enabled, GitLab automatically manages Kubernetes namespaces and service accounts for this cluster.
management_project_idstringThe ID of the GitLab project that manages this cluster's resources and configurations.
namestringThe display name for the cluster.
namespace_per_environmentbooleanWhen enabled, each environment is deployed to a separate Kubernetes namespace for isolation.

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/gitlab MCP server?

com.mcparmory/gitlab is an MCP server listed in the public MCP registry as com.mcparmory/gitlab. Manage projects, groups, branches, merge requests, and CI/CD pipelines. This page covers its PyPI package (mcparmory-gitlab).

Is the com.mcparmory/gitlab MCP server safe to use?

com.mcparmory/gitlab scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 com.mcparmory/gitlab MCP server expose?

com.mcparmory/gitlab exposes 53 tools: get_group_badge, update_group_badge, remove_group_badge, list_group_badges, add_group_badge, and 48 more. Their descriptions and schemas cost roughly 5,140 tokens of context every time the server is loaded.

Is the com.mcparmory/gitlab MCP server still maintained?

com.mcparmory/gitlab is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.