MCP server intelligence profile

Jira MCP Server

Lets an AI assistant read and write Jira Server/Data Center tickets via direct API access

Local Onlynamcpgem
Awaiting current scanNpm · 2.3.0

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

1Distribution channel
9Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install g-jira-mcp from npm

Version 2.3.0 declares 1 executable entrypoint.

npm install --save-exact g-jira-mcp@2.3.0
npx -y -p g-jira-mcp@2.3.0 g-jira-mcp
MCP client configuration example
{
  "mcpServers": {
    "g-jira-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "g-jira-mcp@2.3.0",
        "g-jira-mcp"
      ]
    }
  }
}

Identity

Canonical slugjira-mcp-e70a8f48DeploymentLocal Only
Canonical packagenpm:g-jira-mcpRepositorynamcpgem/gem-jira-mcp
First published—Latest release—
Last security verification—Classification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
npmg-jira-mcp2.3.01Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npmg-jira-mcp2.3.0CurrentSep 5, 20269 toolsSucceeded · 0 resources · 0 promptsEvidence restricted
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

No public current-version evidence is available yet.

Current protocol inventory

2025-06-18Negotiated protocol
jira-mcpServer-reported name
1Capability groups
Aug 22, 2026Observed

Tools 9

ToolCategoryAnnotationsRisk
add_commentAdd a comment to a Jira ticket
Input schema
{
  "type": "object",
  "properties": {
    "body": {
      "type": "string",
      "description": "Comment text (plain text)"
    },
    "ticket_id": {
      "type": "string",
      "description": "Jira issue key, e.g. GEM-234"
    }
  },
  "required": [
    "body",
    "ticket_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
create_ticketCreate a new Jira ticket
Input schema
{
  "type": "object",
  "properties": {
    "assignee": {
      "type": "string",
      "description": "Assignee username, e.g. username"
    },
    "body": {
      "type": "string",
      "description": "Description text"
    },
    "due_date": {
      "type": "string",
      "description": "Due date YYYY-MM-DD"
    },
    "issue_type": {
      "type": "string",
      "description": "Issue type: Story, Task, Bug, Sub-task"
    },
    "labels": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Labels to assign"
    },
    "original_estimate": {
      "type": "string",
      "description": "Time estimate e.g. \"2h\""
    },
    "parent_key": {
      "type": "string",
      "description": "Parent ticket key for Sub-task"
    },
    "project": {
      "type": "string",
      "description": "Project key, e.g. GEM"
    },
    "start_date": {
      "type": "string",
      "description": "Start date YYYY-MM-DD"
    },
    "summary": {
      "type": "string",
      "description": "Issue title"
    }
  },
  "required": [
    "issue_type",
    "project",
    "summary"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
generate_release_notesGenerate Markdown release notes for a fix version, grouped by issue type
Input schema
{
  "type": "object",
  "properties": {
    "fix_version": {
      "type": "string",
      "description": "Release version label, e.g. \"v2.4\""
    },
    "project": {
      "type": "string",
      "description": "Limit to project key, e.g. \"GEM\""
    }
  },
  "required": [
    "fix_version"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
get_ticketGet full details of a Jira ticket by its key
Input schema
{
  "type": "object",
  "properties": {
    "include_comments": {
      "type": "boolean",
      "description": "Include the ticket's comments (default false)"
    },
    "ticket_id": {
      "type": "string",
      "description": "Jira issue key, e.g. GEM-234"
    }
  },
  "required": [
    "ticket_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
link_issuesCreate a link between two Jira tickets
Input schema
{
  "type": "object",
  "properties": {
    "inward_issue": {
      "type": "string",
      "description": "Issue key being linked FROM, e.g. GEM-1"
    },
    "link_type": {
      "type": "string",
      "default": "Blocks",
      "description": "Link type: Blocks, Clones, Relates to, Duplicate, etc."
    },
    "outward_issue": {
      "type": "string",
      "description": "Issue key being linked TO, e.g. GEM-2"
    }
  },
  "required": [
    "inward_issue",
    "outward_issue"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
log_workLog work (time) on a Jira ticket, optionally setting WorklogPRO Type of Work and Type of Activity
Input schema
{
  "type": "object",
  "properties": {
    "activity": {
      "type": "string",
      "description": "Type of Activity (required when work_type is set): correct, create, review"
    },
    "comment": {
      "type": "string",
      "description": "Optional work log comment"
    },
    "started": {
      "type": "string",
      "description": "Start datetime ISO, e.g. '2026-06-29T09:00:00.000+0700'"
    },
    "ticket_id": {
      "type": "string",
      "description": "Jira issue key, e.g. GEM-234"
    },
    "time_spent": {
      "type": "string",
      "description": "Time spent, e.g. '2h 30m', '1d', '45m'"
    },
    "work_type": {
      "type": "string",
      "description": "Type of Work: code, deploy, design, fix, management, meeting, misc, operation, qa, req, research, translation"
    }
  },
  "required": [
    "ticket_id",
    "time_spent"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
search_ticketsSearch Jira tickets using JQL query language
Input schema
{
  "type": "object",
  "properties": {
    "jql": {
      "type": "string",
      "description": "JQL query, e.g. 'project = GEM AND status = \"In Progress\"'"
    },
    "max_results": {
      "type": "number",
      "default": 25,
      "description": "Max results to return (default 25)"
    }
  },
  "required": [
    "jql"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
transition_ticketChange a Jira ticket's status. Matches the transition name or its target status; common aliases (Closed/Resolved -> Done, Reopen -> Re-Open) resolve to whatever the workflow offers. Valid options vary per issue and are listed in the error when no match is found.
Input schema
{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Target status name, e.g. \"In Progress\", \"Done\""
    },
    "ticket_id": {
      "type": "string",
      "description": "Jira issue key, e.g. GEM-234"
    }
  },
  "required": [
    "status",
    "ticket_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
update_ticketUpdate fields of a Jira ticket. Converting between a standard issue type and Sub-task is a Jira REST API limitation — use Jira's UI "Move" action instead.
Input schema
{
  "type": "object",
  "properties": {
    "assignee": {
      "type": "string",
      "description": "Username to assign, or empty string to unassign"
    },
    "description": {
      "type": "string",
      "description": "Replace full description"
    },
    "due_date": {
      "type": "string",
      "description": "Due date YYYY-MM-DD"
    },
    "epic_key": {
      "type": "string",
      "description": "Epic ticket key to set as this issue's Epic Link (shows under the Epic's \"Issues in Epic\" panel, not Linked Issues)"
    },
    "implementation_notes": {
      "type": "string",
      "description": "Append implementation notes to description"
    },
    "issue_type": {
      "type": "string",
      "description": "Issue type: Story, Task, Bug, Sub-task"
    },
    "labels": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Labels to set"
    },
    "original_estimate": {
      "type": "string",
      "description": "Time estimate e.g. \"2h\", \"1d 4h\""
    },
    "parent_key": {
      "type": "string",
      "description": "Parent ticket key for Sub-task"
    },
    "priority": {
      "type": "string",
      "description": "Priority name, e.g. \"High\", \"Medium\", \"Low\""
    },
    "start_date": {
      "type": "string",
      "description": "Start date YYYY-MM-DD"
    },
    "summary": {
      "type": "string",
      "description": "Replace ticket summary/title"
    },
    "ticket_id": {
      "type": "string",
      "description": "Jira issue key, e.g. GEM-234"
    }
  },
  "required": [
    "ticket_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

Jira MCP Server questions

How do I install Jira MCP Server?

Install the selected package version with: npm install --save-exact g-jira-mcp@2.3.0

What tools does Jira MCP Server provide?

Jira MCP Server exposed 9 tools during independent protocol observation, including add_comment, create_ticket, generate_release_notes, get_ticket, link_issues, log_work, search_tickets, transition_ticket, and others.

Is Jira MCP Server secure?

The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.

Company and product intelligence

These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.

Associated company landscape

Atlassian intelligence →

Association is based on retained identity fields; it does not by itself prove first-party publication.

Jira 259 matches

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.