Verified:GitHub

integration-gitlab

Connect GitLab to a self-hosted Hermes agent over SSH.

13|1|Updated Jun 1, 2026

Search Tags:#mcp #api integration #pipeline #gitlab #ssh #merge requests #hermes

One-click install

npx skills add https://github.com/paarths-collab/hstack --skill integration-gitlab

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: integration-gitlab
Source: https://github.com/paarths-collab/hstack/tree/main/skills/integration-gitlab
Command: npx skills add https://github.com/paarths-collab/hstack --skill integration-gitlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill connects GitLab to a self-hosted Hermes agent so AI coding agents can access repos, merge requests, issues, and CI/CD pipelines without manual rework.

Core Features & Use Cases

SSH-first wiring: Runs the setup on a VPS with idempotent, rollback-safe steps and clear validation.
Multiple auth paths: Supports the community static-token MCP sidecar, direct REST API access, and an OAuth-based first-party alternative.
Operational safety: Validates tokens, handles read-only versus write scopes, reloads the gateway correctly, and verifies registration and API reachability.
Use Case: A developer wants Claude Code or Cursor to inspect GitLab issues, comment on merge requests, or trigger pipelines from a remote Hermes agent.

Quick Start

Ask the agent to connect your GitLab instance to Hermes over SSH using the preferred path for your token scope and then verify that the gateway and API are working.

Frequently Asked Questions about integration-gitlab

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I connect a GitLab repository to a self-hosted Hermes agent over SSH?▼

To connect GitLab to a self-hosted Hermes agent, run an SSH-first setup flow that validates your personal access token, registers the MCP server or falls back to REST, and reloads the gateway to enable repository, merge request, and pipeline access.

Can I use a read-only GitLab token to integrate merge requests and pipelines with Hermes?▼

Yes, the GitLab integration supports read-only versus write token scopes, but a read-only PAT restricts AI agents to inspecting issues and pipelines rather than commenting on merge requests or triggering CI/CD workflows.

What is the best way to automate GitLab MCP registration on a remote VPS?▼

The best way to automate GitLab MCP registration is using an idempotent setup process that validates your PAT, attempts MCP registration with a REST API fallback, and performs rollback-safe verification to ensure the gateway is correctly configured.

Does the GitLab Hermes integration support self-managed and dedicated instances?▼

Yes, the GitLab Hermes integration applies to GitLab.com, self-managed, and dedicated instances, allowing AI coding agents to access repositories, merge requests, issues, and CI/CD pipelines across all deployment types.

Why does my GitLab gateway reload fail after registering an MCP server?▼

Gateway reload failures after MCP registration often stem from invalid PAT validation or incorrect token scopes; the integration includes rollback-safe verification steps to catch these issues and ensure API reachability.

Do I need an OAuth token to connect GitLab pipelines to AI coding agents?▼

No, you do not need an OAuth token; the integration supports multiple authentication paths including a community static-token MCP sidecar and direct REST API access alongside the OAuth-based first-party alternative.