@sumirati/mcp-gitlab

MCPcomunidad
v3.0.1sumirati@buggycode.netMITActualizado hace 2 dnpmGitHub

Modern 2026 AI-native Model Context Protocol (MCP) server for GitLab API v4 with dynamic 2-step action discovery, 5-tool lean surface, and 70%+ token-reduction output projection

Funciona en
ClaudeCursorCopilotGemini

Inferido de los transportes que declara este listado (stdio). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.

Indexado automáticamente desde fuentes públicas. Aún sin verificar por su desarrollador en Forge.Reclamar este listado →
1Estrellas en GitHub
hace 2 dÚltima actualización
Necesita 1 credencial antes de poder ejecutarse
  • GITLAB_PERSONAL_ACCESS_TOKENClave de APIobligatoria

    GitLab Personal Access Token with api scope

Declarado por el autor en el registro oficial de MCP. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Paquete
Autorsumirati@buggycode.net
LicenciaMIT
Versión3.0.1
Fuentenpm+mcp-registry
Estado de confianza
B
60/100Bueno
✓Listado en el índice de Forge+10/10
—Identidad del publicador verificada+0/20
→ Publicador: ejecuta `forge publish` desde el repo del paquete para reclamar la propiedad
—Firma de publicación Ed25519+0/5
→ Se incluye automáticamente cuando el publicador ejecuta `forge publish`
—Verificación de dominio+0/5
→ Publicador: aloja /.well-known/forge.json en la página del paquete con { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publica desde GitHub Actions con --provenance para que la attestation vincule este paquete a este repo
—Coincidencia de maintainer en npm+0/5
→ Se consigue cuando tu identidad esté verificada arriba y ese login sea maintainer de este paquete en npm
✓Análisis CVE · limpio+30/30
✓Análisis estático · limpio+20/20
Pégalo en Claude Code, Cursor o cualquier asistente de IA para corregir todas las carencias
EstadoIndexado por la comunidad
PublicadorSin verificar
FirmaSin firmar
Dominio—
Procedencia—
Dependencias✓ 60 resueltas+ · ninguna vulnerable
Superficie de herramientas40 herramientas · 2 privilegiadas
Análisis de seguridad✓ Limpiov3.2.0 · hoy¿Qué tan bien funciona este análisis?
EvaluacionesNinguna
Indexado15 oct 2026

La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.

Herramientas

40 herramientas · 2 privilegiadas
Extraído estáticamente del paquete publicadov3.2.0 · 7h ago

Leído del código que npm publica realmente, en el momento del análisis. El paquete nunca se ejecutó. Las herramientas registradas dinámicamente en tiempo de ejecución, o escondidas en código empaquetado o minificado, pueden pasarse por alto — así que esto es un mínimo de la superficie de herramientas, no un censo completo.

list_branchesList repository branches with latest commit summaries, default branch indicators, and protected status. Use to discover active development branches or check branch existence. Do NOT use to inspect commit diffs (use 'get_commit') or list tags (use 'list_tags').

List repository branches with latest commit summaries, default branch indicators, and protected status. Use to discover active development branches or check branch existence. Do NOT use to inspect commit diffs (use 'get_commit') or list tags (use 'list_tags').

No se publicó ningún esquema de entrada para esta herramienta.

get_branchRetrieve comprehensive details for a specific Git branch, including latest commit SHA, author info, and branch protection rules. Use to verify commit alignment before creating merge requests. Do NOT use to inspect file contents directly; use 'get_file_contents' instead.

Retrieve comprehensive details for a specific Git branch, including latest commit SHA, author info, and branch protection rules. Use to verify commit alignment before creating merge requests. Do NOT use to inspect file contents directly; use 'get_file_contents' instead.

No se publicó ningún esquema de entrada para esta herramienta.

create_branchCreate a new Git branch starting from an existing branch, tag, or commit SHA. Use to initialize feature branches, bugfixes, or release branches. Side effect: creates a new branch pointer on the remote repository. Do NOT use to create new repositories; use 'create_repository' instead.

Create a new Git branch starting from an existing branch, tag, or commit SHA. Use to initialize feature branches, bugfixes, or release branches. Side effect: creates a new branch pointer on the remote repository. Do NOT use to create new repositories; use 'create_repository' instead.

No se publicó ningún esquema de entrada para esta herramienta.

delete_branchprivilegiadaDelete an existing Git branch from a project repository. Use to clean up merged or obsolete feature branches. Side effect: DESTRUCTIVE. Accidental deletion of the project's default branch is actively blocked for safety. Do NOT use to delete tags; use Git tag management instead.

Delete an existing Git branch from a project repository. Use to clean up merged or obsolete feature branches. Side effect: DESTRUCTIVE. Accidental deletion of the project's default branch is actively blocked for safety. Do NOT use to delete tags; use Git tag management instead.

No se publicó ningún esquema de entrada para esta herramienta.

list_protected_branchesList protected branch rules configured in a GitLab project, showing push/merge access levels, force-push permission, and code owner approval requirements. Use to audit branch governance and merge restrictions.

List protected branch rules configured in a GitLab project, showing push/merge access levels, force-push permission, and code owner approval requirements. Use to audit branch governance and merge restrictions.

No se publicó ningún esquema de entrada para esta herramienta.

protect_branchConfigure branch protection rules for a branch or wildcard pattern (e.g. 'main', 'release/*'). Controls push access levels, merge access levels, force push permission, and code owner approval.

Configure branch protection rules for a branch or wildcard pattern (e.g. 'main', 'release/*'). Controls push access levels, merge access levels, force push permission, and code owner approval.

No se publicó ningún esquema de entrada para esta herramienta.

unprotect_branchRemove branch protection rules from a specified branch or wildcard pattern. Side effect: DESTRUCTIVE. Removes push and merge access restrictions from the target branch.

Remove branch protection rules from a specified branch or wildcard pattern. Side effect: DESTRUCTIVE. Removes push and merge access restrictions from the target branch.

No se publicó ningún esquema de entrada para esta herramienta.

list_commitsList chronological commit history for a project, branch, or specific file path with author metadata and commit messages. Filter upstream by ref_name, author, path, and date range. To inspect exact code changes of a specific commit SHA, use 'get_commit' instead.

List chronological commit history for a project, branch, or specific file path with author metadata and commit messages. Filter upstream by ref_name, author, path, and date range. To inspect exact code changes of a specific commit SHA, use 'get_commit' instead.

No se publicó ningún esquema de entrada para esta herramienta.

get_commitRetrieve comprehensive details for a specific Git commit SHA, including author info, statistics, modified files, and selective unified file diffs. Use to inspect exact code changes made in a commit. Supports file_path filtering and line limits to prevent context exhaustion on large commits.

Retrieve comprehensive details for a specific Git commit SHA, including author info, statistics, modified files, and selective unified file diffs. Use to inspect exact code changes made in a commit. Supports file_path filtering and line limits to prevent context exhaustion on large commits.

No se publicó ningún esquema de entrada para esta herramienta.

system_health_checkPerform end-to-end connectivity, latency, and permission diagnostics against the GitLab instance. Verifies API availability, authentication identity, server version/edition (when permitted), and active read-only policy.

Perform end-to-end connectivity, latency, and permission diagnostics against the GitLab instance. Verifies API availability, authentication identity, server version/edition (when permitted), and active read-only policy.

No se publicó ningún esquema de entrada para esta herramienta.

list_push_mirrorsList remote push mirrors configured for a project, including synchronization status, target URLs, and last error diagnostics. Essential for verifying repository synchronization between local self-hosted instances and upstream GitLab instances or remote Git hosts.

List remote push mirrors configured for a project, including synchronization status, target URLs, and last error diagnostics. Essential for verifying repository synchronization between local self-hosted instances and upstream GitLab instances or remote Git hosts.

No se publicó ningún esquema de entrada para esta herramienta.

trigger_push_mirror_syncForce an immediate push mirror synchronization for a designated project remote mirror. Use when code has been committed locally and immediate upstream replication is required without waiting for the scheduled background sync interval.

Force an immediate push mirror synchronization for a designated project remote mirror. Use when code has been committed locally and immediate upstream replication is required without waiting for the scheduled background sync interval.

No se publicó ningún esquema de entrada para esta herramienta.

list_runnersList available GitLab CI/CD runners (instance, group, or project-level), detailing their online status, active/paused state, and executor types. Use to diagnose CI pipeline execution delays, runner connectivity, or missing executor tags.

List available GitLab CI/CD runners (instance, group, or project-level), detailing their online status, active/paused state, and executor types. Use to diagnose CI pipeline execution delays, runner connectivity, or missing executor tags.

No se publicó ningún esquema de entrada para esta herramienta.

get_runner_statusRetrieve comprehensive details and health status for a specific CI/CD runner, including IP address, architecture, runner version, tags, and last contacted timestamp. Use to troubleshoot stuck jobs or unresponsive self-hosted runners.

Retrieve comprehensive details and health status for a specific CI/CD runner, including IP address, architecture, runner version, tags, and last contacted timestamp. Use to troubleshoot stuck jobs or unresponsive self-hosted runners.

No se publicó ningún esquema de entrada para esta herramienta.

list_project_hooksList configured project webhooks and their subscribed triggers (push, merge requests, issues, pipeline events). Use to audit integration webhooks and verify CI/CD automation hook registrations.

List configured project webhooks and their subscribed triggers (push, merge requests, issues, pipeline events). Use to audit integration webhooks and verify CI/CD automation hook registrations.

No se publicó ningún esquema de entrada para esta herramienta.

gitlab_find_actionsSearch and discover available GitLab operations on-demand across the entire platform. Returns matching action names, purpose descriptions, and parameter schemas for use with 'gitlab_execute_action'. Keeps prompt context minimal (<500 tokens) while retaining 100% coverage.

Search and discover available GitLab operations on-demand across the entire platform. Returns matching action names, purpose descriptions, and parameter schemas for use with 'gitlab_execute_action'. Keeps prompt context minimal (<500 tokens) while retaining 100% coverage.

No se publicó ningún esquema de entrada para esta herramienta.

gitlab_execute_actionExecute any discovered GitLab platform action with input validation and token-optimized response projection. Dispatches directly to the corresponding API endpoint while enforcing read-only safety restrictions.

Execute any discovered GitLab platform action with input validation and token-optimized response projection. Dispatches directly to the corresponding API endpoint while enforcing read-only safety restrictions.

No se publicó ningún esquema de entrada para esta herramienta.

list_issuesList and filter project issues by state ('opened', 'closed', 'all'), milestone, labels, author, assignee, or keyword search pushed directly upstream to GitLab's indexed database. Architectural Best Practice: For known issues, always prefer 'get_issue' with exact issue_iid rather than broad listing.

List and filter project issues by state ('opened', 'closed', 'all'), milestone, labels, author, assignee, or keyword search pushed directly upstream to GitLab's indexed database. Architectural Best Practice: For known issues, always prefer 'get_issue' with exact issue_iid rather than broad listing.

No se publicó ningún esquema de entrada para esta herramienta.

get_issueRetrieve comprehensive details for a specific issue by its project-scoped IID (#<iid>), including description, assignees, labels, milestone, and issue status. Use to review issue requirements or track resolution. Do NOT use to list comments on the issue; use 'list_issue_notes' instead.

Retrieve comprehensive details for a specific issue by its project-scoped IID (#<iid>), including description, assignees, labels, milestone, and issue status. Use to review issue requirements or track resolution. Do NOT use to list comments on the issue; use 'list_issue_notes' instead.

No se publicó ningún esquema de entrada para esta herramienta.

create_issueCreate a new issue with a title, markdown description, milestone (by title or ID), labels, assignees, and optional due date. Use to report bugs, track user stories, or plan tasks. Side effect: creates a new GitLab issue immediately. Do NOT use to comment on existing issues; use 'create_issue_note'…

Create a new issue with a title, markdown description, milestone (by title or ID), labels, assignees, and optional due date. Use to report bugs, track user stories, or plan tasks. Side effect: creates a new GitLab issue immediately. Do NOT use to comment on existing issues; use 'create_issue_note'…

No se publicó ningún esquema de entrada para esta herramienta.

update_issueUpdate an existing issue's title, description, state ('close' or 'reopen'), milestone, labels, or assignees. Use to transition issue lifecycle or update task status. Side effect: alters issue state immediately. Do NOT use to post progress comments; use 'create_issue_note' instead.

Update an existing issue's title, description, state ('close' or 'reopen'), milestone, labels, or assignees. Use to transition issue lifecycle or update task status. Side effect: alters issue state immediately. Do NOT use to post progress comments; use 'create_issue_note' instead.

No se publicó ningún esquema de entrada para esta herramienta.

list_issue_notesList the chronological discussion notes, user comments, and activity audit log for a specific issue by IID. Use to review problem discussion, past comments, or implementation progress. Do NOT use for merge request discussions; use 'list_merge_request_discussions' instead.

List the chronological discussion notes, user comments, and activity audit log for a specific issue by IID. Use to review problem discussion, past comments, or implementation progress. Do NOT use for merge request discussions; use 'list_merge_request_discussions' instead.

No se publicó ningún esquema de entrada para esta herramienta.

create_issue_notePost a new markdown comment, progress update, or verification note to an existing issue. Use to communicate findings, document test results, or ask questions on a task. Side effect: posts a public comment to the issue thread immediately.

Post a new markdown comment, progress update, or verification note to an existing issue. Use to communicate findings, document test results, or ask questions on a task. Side effect: posts a public comment to the issue thread immediately.

No se publicó ningún esquema de entrada para esta herramienta.

list_issue_linksList issue dependency links ('relates_to', 'blocks', 'is_blocked_by') associated with a specific issue. Use when analyzing task dependencies or release blockers. Do NOT use to inspect issue discussion notes; use 'list_issue_notes' instead.

List issue dependency links ('relates_to', 'blocks', 'is_blocked_by') associated with a specific issue. Use when analyzing task dependencies or release blockers. Do NOT use to inspect issue discussion notes; use 'list_issue_notes' instead.

No se publicó ningún esquema de entrada para esta herramienta.

create_issue_linkSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

list_project_membersSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

get_project_memberSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

add_project_memberSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

update_project_memberSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

remove_project_memberprivilegiadaSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

list_merge_requestsSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

get_merge_requestSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

create_merge_requestSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

update_merge_requestSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

get_merge_request_changesSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

list_merge_request_discussionsSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

create_diff_discussionSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

reply_merge_request_discussionSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

update_merge_request_discussion_noteSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

resolve_merge_request_discussionSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

24 de 40 herramientas publicaron una descripción.

Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.

Acerca de

Modern 2026 AI-native Model Context Protocol (MCP) server for GitLab API v4 with dynamic 2-step action discovery, 5-tool lean surface, and 70%+ token-reduction output projection

Palabras clave
mcpmodel-context-protocolgitlabaiagenttoken-savingdeveloper-tools
Alternativas
Comparando superficies de herramientas…

Árbol de dependencias

Lo que un análisis de Forge resolvió a partir de los metadatos de npm el 2026-10-17: resolución observada, no una declaración del publicador.

60 paquetes resueltos · 3 directos · ninguno con avisos de seguridad La resolución se detiene en la profundidad 4 y en 60 paquetes.

El rastreo se detuvo en el límite de profundidad 4. Nada por debajo de ese nivel llegó a resolverse.

El rastreo se detuvo en el límite de 60 paquetes. El resto del árbol nunca se resolvió.

Hay 36 paquetes resueltos más que no se dibujan aquí (límite de visualización: 24). Toda dependencia con avisos de seguridad se dibuja aunque se supere el límite. Inventario completo (SBOM CycloneDX)

Declaradas pero no resueltas

54 dependencias declaradas nunca llegaron al árbol. Faltan en la resolución de Forge, no en el paquete.

+42 más sin listar. Los recuentos por motivo de arriba las incluyen todas.

No se siguen: peerDependencies. Este árbol cubre solo dependencias en tiempo de ejecución, así que lo que estas arrastren nunca se resolvió.

Temas

Relacionados en git & code hosting