MCP server intelligence profile

jira-dev-mcp Server

A local MCP server for Jira Cloud-driven development. Connects MCP clients to Jira for searching issues, reading tasks, parsing attachments, and mapping projects to local repos

Local Onlynianyi778
Awaiting current scanNpm · 1.4.7

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

1Distribution channel
10Independently 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 jira-dev-mcp from npm

Version 1.4.7 declares 1 executable entrypoint.

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

Identity

Canonical slugjira-dev-mcp-605d0d45DeploymentLocal Only
Canonical packagenpm:jira-dev-mcpRepositorynianyi778/jira-dev-mcp
First published—Latest release—
Last security verification—Classification confidence90%
PublicationDraftOfficial distributionNot verified

Distributions

ChannelIdentifierCurrent versionVersionsSource
npmjira-dev-mcp1.4.71Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npmjira-dev-mcp1.4.7CurrentSep 5, 202610 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-dev-mcpServer-reported name
1Capability groups
Aug 22, 2026Observed

Tools 10

ToolCategoryAnnotationsRisk
jira_add_commentPost a comment on a Jira issue. Returns the comment URL so you can verify it directly.
Input schema
{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Jira issue key (e.g. AT-123). Required for new comments, optional when confirming with confirm_token."
    },
    "body": {
      "type": "string",
      "description": "Comment text (plain text, will be wrapped in ADF paragraph). Required for new comments, optional when confirming with confirm_token."
    },
    "confirm_token": {
      "type": "string",
      "description": "Confirmation token from preview step. When provided, key and body are optional — the pending comment content is used."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_analyze_taskFull investigation and fix workflow for a Jira issue. Accepts an issue key (AT-123) or full browse URL. Reads the issue, prior comments, linked issues, and attachments; detects duplicate analysis (idempotency); selects a type-aware template (Bug/Story/Task); and provides step-by-step SOP: explore code → plan → baseline test → implement → build verify → post analysis comment. Use this instead of jira_read_task when you want to drive the full workflow end-to-end.
Input schema
{
  "type": "object",
  "properties": {
    "input": {
      "type": "string",
      "description": "Jira issue key (e.g. AT-123) or full browse URL (e.g. https://xxx.atlassian.net/browse/AT-123)"
    },
    "auto_comment": {
      "type": "boolean",
      "description": "Automatically post the completed analysis as a comment without asking for confirmation (default false, consistent with commentMode default of manual)"
    },
    "comment_max_results": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Max comments to fetch for prior-analysis check (1-100, default 50)"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default markdown)"
    }
  },
  "required": [
    "input"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_download_all_attachmentsDownload all attachments from a Jira issue in a single call. Optionally filter by MIME type (e.g. "image/" for images only). Returns all files with their content inline. Use this instead of multiple jira_download_attachment calls.
Input schema
{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Jira issue key (e.g. AT-123)"
    },
    "mime_filter": {
      "type": "string",
      "description": "Filter by MIME type prefix (e.g. \"image/\" for images only, \"text/\" for text files)"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default markdown)"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_download_attachmentDownload an attachment from a Jira issue. Text files (txt, md, json, log) are returned inline. CSV, XLS, XLSX, PDF are parsed by Python and returned as structured text. Images and other binary files are returned as base64.
Input schema
{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Jira issue key (e.g. AT-123)"
    },
    "filename": {
      "type": "string",
      "description": "Attachment filename as listed in jira_read_task"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default json)"
    }
  },
  "required": [
    "key",
    "filename"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_edit_commentEdit an existing Jira comment. In manual mode, returns a preview first and requires confirm_token to apply the update.
Input schema
{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Jira issue key (e.g. AT-123). Required for new edits, optional when confirming with confirm_token."
    },
    "commentId": {
      "type": "string",
      "description": "Existing Jira comment id. Required for new edits, optional when confirming with confirm_token."
    },
    "body": {
      "type": "string",
      "description": "Updated comment text (plain text, will be wrapped in ADF paragraph). Required for new edits, optional when confirming with confirm_token."
    },
    "confirm_token": {
      "type": "string",
      "description": "Confirmation token from preview step. When provided, key/commentId/body are optional — the pending content is used."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_get_project_pathGet the local repository path mapped to a Jira project key.
Input schema
{
  "type": "object",
  "properties": {
    "jiraProject": {
      "type": "string",
      "description": "Jira project key (e.g. AT)"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default json)"
    }
  },
  "required": [
    "jiraProject"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_my_tasksList Jira issues assigned to the currently authenticated user, optionally filtered by status.
Input schema
{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Filter by status name (e.g. \"In Progress\", \"To Do\")"
    },
    "maxResults": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "Max results (1-50, default 10)"
    },
    "startAt": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default json)"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_read_taskRead raw details of a Jira issue (description, subtasks, changelog, labels, priority, parent, attachments). Data-only — does NOT guide analysis or post comments. Use jira_analyze_task when you need the full investigation workflow.
Input schema
{
  "type": "object",
  "properties": {
    "input": {
      "type": "string",
      "description": "Jira issue key or full browse URL (e.g. AT-123 or https://xxx.atlassian.net/browse/AT-123)"
    },
    "includeComments": {
      "type": "boolean",
      "description": "Include comments (default false)"
    },
    "commentStartAt": {
      "type": "integer",
      "minimum": 0,
      "description": "Comment pagination offset"
    },
    "commentMaxResults": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "Max comments (1-50, default 20)"
    },
    "changelogStartAt": {
      "type": "integer",
      "minimum": 0,
      "description": "Changelog pagination offset"
    },
    "changelogMaxResults": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Max changelog entries (1-100, default 20)"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default json)"
    }
  },
  "required": [
    "input"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_search_issuesSearch Jira issues using natural language keywords or raw JQL. Returns issue keys, summaries, statuses, and assignees.
Input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query (keywords or JQL)"
    },
    "maxResults": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "Max results to return (1-50, default 10)"
    },
    "startAt": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "response_format": {
      "type": "string",
      "enum": [
        "json",
        "markdown"
      ],
      "description": "Output format (default json)"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
——
jira_set_project_pathMap a Jira project key to a local repository path. This enables jira_read_task to include the local path hint for code exploration.
Input schema
{
  "type": "object",
  "properties": {
    "jiraProject": {
      "type": "string",
      "description": "Jira project key (e.g. AT)"
    },
    "localPath": {
      "type": "string",
      "description": "Absolute local path to the project repository"
    }
  },
  "required": [
    "jiraProject",
    "localPath"
  ],
  "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-dev-mcp Server questions

How do I install jira-dev-mcp Server?

Install the selected package version with: npm install --save-exact jira-dev-mcp@1.4.7

What tools does jira-dev-mcp Server provide?

jira-dev-mcp Server exposed 10 tools during independent protocol observation, including jira_add_comment, jira_analyze_task, jira_download_all_attachments, jira_download_attachment, jira_edit_comment, jira_get_project_path, jira_my_tasks, jira_read_task, and others.

Is jira-dev-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.