mcp-gitlab-jira
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_URL | Yes | The URL of your GitLab instance | |
| ATLASSIAN_API_TOKEN | Yes | Your Jira API token | |
| ATLASSIAN_SITE_NAME | Yes | Your Atlassian site name | |
| GITLAB_ACCESS_TOKEN | Yes | Your GitLab Personal Access Token with API access | |
| ATLASSIAN_USER_EMAIL | Yes | Your email address for Atlassian/Jira |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitlab_get_merge_request_detailsB | Fetches detailed information about a GitLab Merge Request, including file diffs. |
| gitlab_get_file_contentB | Fetches the content of a specific file at a given SHA in a GitLab project. |
| gitlab_add_comment_to_merge_requestB | Adds a comment to a GitLab Merge Request. Can be a general comment, a reply to an existing discussion, or an inline comment on a specific line. |
| gitlab_list_merge_requestsC | Lists merge requests for a given GitLab project. |
| gitlab_assign_reviewers_to_merge_requestC | Assigns reviewers to a GitLab Merge Request. |
| gitlab_list_project_membersC | Lists all members (contributors) of a given GitLab project. |
| gitlab_list_project_members_by_project_nameC | Lists all members (contributors) of a given GitLab project by project name. |
| gitlab_list_projects_by_nameB | Filters GitLab projects by name using a fuzzy, case-insensitive match. |
| gitlab_list_all_projectsA | Lists all accessible GitLab projects. (Try to use list_projects_by_name as it is more efficient) |
| gitlab_list_all_releasesC | Fetches releases for a given GitLab project. |
| gitlab_list_releases_since_versionC | Filters releases for a given GitLab project since a specific version. |
| gitlab_get_user_id_by_usernameB | Retrieves the GitLab user ID for a given username. |
| gitlab_get_user_activitiesC | Fetches activities for a given GitLab user by their username, optionally filtered by date. |
| gitlab_get_project_pipelinesC | Gets pipelines for a GitLab project, optionally filtered by branch/ref. |
| gitlab_get_merge_request_pipelinesC | Gets pipelines for a specific GitLab Merge Request. |
| gitlab_get_pipeline_detailsB | Gets detailed information about a specific pipeline. |
| gitlab_get_pipeline_jobsC | Gets jobs for a specific pipeline. |
| gitlab_get_job_logsC | Gets logs for a specific job. |
| gitlab_trigger_pipelineC | Triggers a new pipeline for a specific branch/ref. |
| gitlab_retry_pipelineC | Retries a failed pipeline. |
| gitlab_cancel_pipelineC | Cancels a running pipeline. |
| gitlab_list_branchesC | Lists all branches in a GitLab project. |
| gitlab_create_branchC | Creates a new branch in a GitLab project. |
| gitlab_delete_branchC | Deletes a branch from a GitLab project. |
| gitlab_get_branch_detailsC | Gets detailed information about a specific branch. |
| gitlab_list_project_issuesC | Lists issues in a GitLab project. |
| gitlab_get_issue_detailsC | Gets detailed information about a specific GitLab issue. |
| gitlab_create_issueC | Creates a new issue in a GitLab project. |
| gitlab_update_issueC | Updates an existing GitLab issue. |
| gitlab_close_issueC | Closes a GitLab issue. |
| gitlab_add_comment_to_issueC | Adds a comment to a GitLab issue. |
| gitlab_get_issue_commentsC | Gets comments for a GitLab issue. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 32 tools
Most tools have distinct purposes targeting specific GitLab resources and actions, with clear boundaries like gitlab_create_issue vs. gitlab_update_issue. However, some overlap exists between gitlab_list_project_members and gitlab_list_project_members_by_project_name, which could cause confusion as they serve similar functions with minor differences in input parameters.
All tools follow a consistent gitlab_verb_noun pattern with snake_case throughout, such as gitlab_get_issue_details and gitlab_trigger_pipeline. This predictability makes it easy for agents to understand and navigate the toolset without naming conflicts or style variations.
With 32 tools, the count is borderline high for a GitLab-focused server, as it may feel heavy and potentially overwhelming for agents. While it covers many aspects, it approaches the upper limit where efficiency could be impacted, though it remains within a reasonable scope for comprehensive GitLab operations.
The toolset provides extensive coverage of GitLab's domain, including CRUD operations for issues, merge requests, branches, pipelines, and more, with no obvious gaps. It supports full lifecycle management from creation to updates and deletions, ensuring agents can handle most workflows without dead ends.