Jira Data Center MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_PAT | No | Personal Access Token (preferred auth method) | |
| LOG_LEVEL | No | debug | info | warn | error | info |
| JIRA_BASE_URL | Yes | Base URL of your Jira Data Center instance, e.g. https://jira.company.com | |
| JIRA_PASSWORD | No | Password for Basic auth (requires JIRA_USERNAME) | |
| JIRA_USERNAME | No | Username for Basic auth (requires JIRA_PASSWORD) | |
| JIRA_TIMEOUT_MS | No | HTTP request timeout in milliseconds | 15000 |
| JIRA_TLS_REJECT_UNAUTHORIZED | No | Set to false only for internal CAs without a valid chain | true |
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 |
|---|---|
| get_current_userA | Returns the Jira user identity associated with the configured credentials (GET /rest/api/2/myself). |
| server_infoA | Returns Jira Data Center deployment info: version, deployment type, and build number (GET /rest/api/2/serverInfo). |
| search_issuesC | Runs a JQL query and returns matching issues (GET /rest/api/2/search) with key, summary, status, assignee, reporter, created, and updated. |
| get_issueA | Fetches full details for a single issue (GET /rest/api/2/issue/{key}): summary, description, status, comments, labels, and assignee. Confluence access: linked Confluence pages are NOT part of an issue's fields and are never returned here. In Jira Data Center they are stored as REMOTE LINKS. To read the Confluence content associated with an issue, an agent should:
|
| create_issueB | Creates a new Jira issue (POST /rest/api/2/issue) and returns the created issue key. |
| add_commentA | Adds a comment to an issue (POST /rest/api/2/issue/{key}/comment). |
| transition_issueA | Moves an issue through its workflow (POST /rest/api/2/issue/{key}/transitions). Use get_transitions first to discover valid transitionId values. |
| get_projectsA | Lists all Jira projects visible to the authenticated user (GET /rest/api/2/project). |
| get_transitionsA | Lists the workflow transitions currently available for an issue (GET /rest/api/2/issue/{key}/transitions). |
| get_issue_commentsA | Lists all comments on an issue (GET /rest/api/2/issue/{key}/comment). |
| get_issue_remote_linksA | Lists an issue's remote links (GET /rest/api/2/issue/{key}/remotelink), including linked Confluence pages ('Wiki Page' links) and generic web links. |
| execute_jqlA | Runs an arbitrary JQL query (GET /rest/api/2/search) and returns raw issue data for the requested fields. Use this for ad-hoc reporting when search_issues' fixed field set isn't enough. |
| create_jira_story_from_requirementsA | Turns workshop notes or Fit/Gap analysis text into properly structured Jira Stories, Tasks, and Bugs, then creates them in the given project. If |
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 13 tools
Most tools target distinct resources and actions, such as issue retrieval, comment management, and workflow transitions. However, search_issues and execute_jql both run JQL queries with only a difference in field selection, and create_jira_story_from_requirements overlaps with create_issue for issue creation, requiring careful reading of descriptions to choose correctly.
Names generally follow a get_/create_/add_/transition_ verb-noun pattern, making the set predictable. Minor deviations include server_info (lacking the 'get_' prefix) and transition_issue (using the verb 'transition' rather than a noun like 'issue_transition'), but these are still clear and do not confuse the overall convention.
With 13 tools, the server covers a broad range of Jira operations without being overwhelming. Each tool addresses a meaningful capability, from basic issue CRUD-like operations to search, transitions, remote links, and a novel requirements-to-story transformer, fitting well within the typical 3-15 range.
The tool set lacks update_issue and delete_issue, which are fundamental for full issue lifecycle management. While it provides create, read, transition, comments, search, and project listing, an agent cannot modify an existing issue's fields or remove it, leaving a notable gap for many Jira workflows.