GitLab Jira Context MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_TOKEN | Yes | GitLab personal access token with read access to projects. | |
| GRAFANA_TOKEN | No | Grafana service account token. Optional; must be paired with GRAFANA_BASE_URL. | |
| JIRA_BASE_URL | Yes | Base URL of your Jira Server or Data Center. | |
| JIRA_API_TOKEN | Yes | Jira personal access token for API access. | |
| GITLAB_BASE_URL | Yes | Base URL of your GitLab instance. | |
| CONFLUENCE_TOKEN | No | Confluence personal access token. Optional; must be paired with CONFLUENCE_BASE_URL. | |
| GRAFANA_BASE_URL | No | Base URL of your Grafana instance. Optional; must be paired with GRAFANA_TOKEN. | |
| CONFLUENCE_BASE_URL | No | Base URL of your Confluence Server or Data Center. Optional; must be paired with CONFLUENCE_TOKEN. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitlab_list_projectsB | List GitLab projects visible to the configured token. |
| gitlab_get_projectA | Get a GitLab project by numeric ID or URL-encoded path. |
| gitlab_list_merge_requestsC | List GitLab merge requests visible to the configured token. |
| gitlab_get_merge_requestC | Get one GitLab merge request and its metadata. |
| gitlab_list_pipelinesB | List recent CI/CD pipelines for a GitLab project. |
| gitlab_get_fileA | Read one file from a GitLab repository at a branch, tag, or commit ref. |
| jira_get_my_issuesA | List Jira issues assigned to the authenticated user. |
| jira_get_issueA | Get a Jira issue by key, including comments. |
| jira_search_issuesB | Search Jira issues using JQL. This tool is read-only. |
| jira_list_commentsC | List comments on a Jira issue. |
| jira_list_worklogsC | List worklog entries on a Jira issue. |
| jira_get_transitionsA | List the status transitions currently available for a Jira issue. |
| jira_get_changelogB | Get the status and field change history for a Jira issue. |
| jira_add_commentB | Add a plain-text comment to a Jira issue. Requires explicit confirmation. |
| jira_add_worklogA | Add a worklog entry to a Jira issue. Requires explicit confirmation. |
| confluence_get_pageA | Get a Confluence page by numeric page ID, including stored page content. |
| confluence_searchB | Search Confluence content with a CQL query. |
| grafana_search_dashboardsB | Search Grafana dashboards visible to the configured service account. |
| grafana_get_dashboardA | Get a Grafana dashboard by UID. |
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 19 tools
Tools are cleanly separated by domain prefixes (gitlab_, jira_, confluence_, grafana_) and each targets a distinct resource. Minor overlap exists between jira_get_issue (which includes comments) and jira_list_comments, but the descriptions clarify the intended use.
Uses consistent snake_case with domain prefixes and verb_noun structure. Some deviation: jira_get_my_issues is a list operation but named get_ rather than list_, and jira_search_issues uses search_ instead of list_. Otherwise consistent.
At 19 tools, the server is slightly above the typical 3-15 range, but given it covers four systems (GitLab, Jira, Confluence, Grafana) with read and write operations, each tool feels necessary and the count is reasonable.
The server provides strong coverage for retrieving context from all four systems, including issue details, comments, worklogs, pipelines, and dashboards. Minor gaps exist such as no GitLab commit listing or Jira issue creation, but these fall outside the 'context' scope.