Provides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools
Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 0.1.0 declares 1 executable entrypoint.
npm install --save-exact @hackdonalds/jira-mcp@0.1.0npx -y -p @hackdonalds/jira-mcp@0.1.0 @hackdonalds/jira-mcp{
"mcpServers": {
"@hackdonalds/jira-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"@hackdonalds/jira-mcp@0.1.0",
"@hackdonalds/jira-mcp"
]
}
}
}| Canonical slug | jira-mcp-server-bb4a62de | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:@hackdonalds/jira-mcp | Repository | hackdonalds/jira-mcp |
| First published | — | Latest release | — |
| Last security verification | — | Classification confidence | 90% |
| Publication | Draft | Official distribution | Not verified |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | @hackdonalds/jira-mcp | 0.1.0 | 1 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npm@hackdonalds/jira-mcp | 0.1.0Current | Sep 5, 2026 | 6 toolsSucceeded · 0 resources · 0 prompts | Evidence restricted |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
No public current-version evidence is available yet.
| Tool | Category | Annotations | Risk |
|---|---|---|---|
jira_add_commentAdd a comment to a JIRA issueInput schema{
"type": "object",
"properties": {
"issueKey": {
"type": "string",
"description": "The JIRA issue key"
},
"comment": {
"type": "string",
"description": "Comment text"
}
},
"required": [
"issueKey",
"comment"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_create_issueCreate a new JIRA issueInput schema{
"type": "object",
"properties": {
"project": {
"type": "string",
"description": "Project key"
},
"issueType": {
"type": "string",
"description": "Issue type (e.g., Bug, Task, Story)"
},
"summary": {
"type": "string",
"description": "Issue summary"
},
"description": {
"type": "string",
"description": "Issue description"
},
"assignee": {
"type": "string",
"description": "Assignee account ID"
},
"priority": {
"type": "string",
"description": "Priority name"
}
},
"required": [
"project",
"issueType",
"summary"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_get_issueGet details of a specific JIRA issueInput schema{
"type": "object",
"properties": {
"issueKey": {
"type": "string",
"description": "The JIRA issue key (e.g., PROJECT-123)"
}
},
"required": [
"issueKey"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_searchSearch issues using JQL (JIRA Query Language)Input schema{
"type": "object",
"properties": {
"jql": {
"type": "string",
"description": "JQL query string"
},
"startAt": {
"type": "number",
"description": "Starting index for pagination (default: 0)"
},
"maxResults": {
"type": "number",
"description": "Maximum number of results (default: 50)"
}
},
"required": [
"jql"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_transition_issueTransition an issue to a new statusInput schema{
"type": "object",
"properties": {
"issueKey": {
"type": "string",
"description": "The JIRA issue key"
},
"transitionId": {
"type": "string",
"description": "The transition ID"
},
"comment": {
"type": "string",
"description": "Optional comment for the transition"
}
},
"required": [
"issueKey",
"transitionId"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_update_issueUpdate an existing JIRA issueInput schema{
"type": "object",
"properties": {
"issueKey": {
"type": "string",
"description": "The JIRA issue key"
},
"summary": {
"type": "string",
"description": "New summary"
},
"description": {
"type": "string",
"description": "New description"
},
"assignee": {
"type": "string",
"description": "New assignee account ID"
},
"priority": {
"type": "string",
"description": "New priority name"
}
},
"required": [
"issueKey"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact @hackdonalds/jira-mcp@0.1.0
JIRA MCP Server exposed 6 tools during independent protocol observation, including jira_add_comment, jira_create_issue, jira_get_issue, jira_search, jira_transition_issue, jira_update_issue.
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.
Association is based on retained identity fields; it does not by itself prove first-party publication.
Curated product and capability guides containing this catalog record.