Jira Enterprise MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_PAT | Yes | Your Jira Personal Access Token | |
| JIRA_BASE_URL | Yes | The base URL of your Jira instance (e.g., https://your-jira.example.com) | |
| JIRA_DEFAULT_PROJECT | Yes | The default Jira project key (e.g., YOURPROJECT) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_test_connectionA | Verify that the Jira PAT works and return the current user profile. |
| jira_get_issueA | Fetch a Jira issue by key, including common fields and rendered metadata. |
| jira_get_issue_with_imagesA | Fetch a Jira issue with attachment metadata and include screenshot/image attachments as MCP image content. |
| jira_get_attachmentA | Fetch Jira attachment metadata and optionally include attachment content. When includeContent is true, raw attachment bytes are returned as base64 in the JSON payload; image attachments also include MCP image preview content. |
| jira_list_issue_commentsC | List comments for a Jira issue in a simplified shape. |
| jira_transition_issueA | List available transitions for an issue or perform a transition by id. |
| jira_update_issueC | Update selected common fields on an existing Jira issue. |
| jira_add_attachmentC | Upload a file attachment to a Jira issue using base64-encoded content. |
| jira_add_comment_with_attachmentA | Upload an attachment to a Jira issue and then post a comment that references it, with optional inline image markup. |
| jira_get_issue_linksB | Fetch linked issues for a Jira issue in a simplified shape. |
| jira_get_worklogA | Fetch worklogs for a Jira issue. |
| jira_add_worklogC | Add a worklog entry to a Jira issue. |
| jira_list_projectsA | List Jira projects visible to the PAT. Useful for validating access and choosing a default project. |
| jira_get_create_metaA | Inspect issue creation metadata for a project, optionally filtered to a specific issue type. Falls back to project issue types and statuses when this Jira tenant does not expose createmeta. |
| jira_searchC | Run a JQL search in Jira. |
| jira_create_issueB | Create a Jira issue in the given project. |
| jira_add_commentB | Add a comment to an existing Jira 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 17 tools
Most tools have distinct purposes, but `jira_add_attachment` and `jira_add_comment_with_attachment` overlap in attachment functionality, potentially causing misselection. Descriptions help clarify, so ambiguity is minimal.
All tools follow the `jira_verb_noun` pattern consistently. Naming is predictable and clear, with only minor exceptions like `search` (no noun) which is still unambiguous.
17 tools is slightly above the typical well-scoped range but reasonable for a complex system like Jira. The set covers many aspects without being excessive.
Core issue operations (create, read, update, transition) are covered, but a delete issue tool is missing. Other gaps like project management and user operations are acceptable for a focused MCP server.