#GitLab Integration

DevBoy tools provides full integration with GitLab for managing issues, merge requests, and code reviews through AI assistants. Both GitLab.com and self-hosted GitLab instances are supported.

#Required token scopes

When creating a GitLab Personal Access Token, you need to select the following scopes:

#Configuration

#Basic configuration

# Set GitLab instance URL (defaults to https://gitlab.com)
devboy config set gitlab.url https://gitlab.com

# Set project ID (numeric ID or full path)
devboy config set gitlab.project_id group/project

# Store token in OS keychain
devboy config set-secret gitlab.token <token>

#Configuration file

Settings are stored in ~/.config/devboy-tools/config.toml:

[gitlab]
url = "https://gitlab.com"
project_id = "group/project"

The token is stored separately in the OS keychain for security.

#Self-hosted GitLab

For GitLab Enterprise or self-managed instances, set the url to your instance:

devboy config set gitlab.url https://gitlab.example.com
devboy config set gitlab.project_id my-group/my-project
devboy config set-secret gitlab.token <token>

#MCP tools

Once configured, the following MCP tools are available:

#Issue tools

#Merge request tools

#CI/CD tools

To start a manual job, first call get_pipeline and copy both IDs from its output:

devboy tools call get_pipeline '{"branch":"main","includeFailedLogs":false}'
devboy tools call run_pipeline_job '{"pipelineId":"501","jobId":"701"}'

Optional CI variables must have string values. GitLab 18.10 and later also accept typed jobInputs:

devboy tools call run_pipeline_job '{
  "pipelineId": "501",
  "jobId": "701",
  "variables": {
    "DEPLOY_ENV": "test"
  },
  "jobInputs": {
    "dry_run": true,
    "replicas": 2
  }
}'

run_pipeline_job fails closed: it fetches the job immediately before the write and refuses to call GitLab's /play endpoint when the job is missing, belongs to another pipeline, or is no longer in the manual state.

#Output formats

All tools support three output formats via the format parameter:

• markdown (default) - Human-readable with formatting
• compact - Condensed format for limited context
• json - Raw JSON data

Example:

{
  "key": "gitlab#123",
  "format": "json"
}

#Testing

Verify your GitLab configuration:

devboy test gitlab

This will test the connection and display your GitLab user information.

#Troubleshooting

#"401 Unauthorized" error

• Verify your token is copied correctly
• Check that the token hasn't expired
• Ensure the token has the required api scope

#"404 Not Found" error

• Verify the project ID or path is correct
• Ensure the project exists and is accessible with your token
• For paths with subgroups, use the full path (e.g., group/subgroup/project)

#"403 Forbidden" error

• Your token may lack the required scope
• The project may have restricted API access
• Check if your account has the necessary project permissions

#Rate limiting

GitLab API has rate limits:

• GitLab.com: 2,000 requests per minute for authenticated users
• Self-hosted: depends on instance configuration
• The tool will show a rate limit error if exceeded