All servers / Project management / Jira MCP server
Jira MCP server
Model Context Protocol (MCP) server for Jira API integration
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.12.2. Package: mcp-jira-stdio · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.2 seconds including download)
- Tools offered: 23
- Last published: 2026-11-06
- Weekly downloads (npm): 1,746
- License: MIT · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
jira_get_visible_projects2 of 2 parameters describedRetrieves all projects accessible to the authenticated user. Returns project keys, names, descriptions, and basic metadata.
jira_get_issue3 of 3 parameters describedRetrieve details for a specific Jira issue by key or URL. Use this when the user mentions an issue like "PAYWALL-943" or pastes a Jira link (e.g., https://your.atlassian.net/browse/PAYWALL-943). Returns status, assignee, priority, project, type, labels, components, timestamps, and description.
jira_search_issues5 of 5 parameters describedSearch for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "project = PROJECT AND status = Open", "assignee = currentUser()". For pagination, use nextPageToken from previous response.
jira_get_my_issues4 of 4 parameters describedRetrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. For pagination, use nextPageToken from previous response.
jira_get_issue_types1 of 1 parameter describedRetrieves available issue types. Can get global issue types or project-specific issue types including regular issues and subtasks (Bug, Story, Task, Epic, etc.).
jira_get_users5 of 5 parameters describedSearch for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination.
jira_get_prioritiesno parametersRetrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions.
jira_get_statuses2 of 2 parameters describedRetrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information.
jira_get_project_info2 of 2 parameters describedRetrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list.
jira_get_create_meta2 of 2 parameters describedRetrieves create metadata for a project, showing all available fields (including custom fields) for creating issues. Shows required vs optional fields, field types, and allowed values. Use this before creating issues to discover what fields are needed.
jira_get_custom_fields1 of 1 parameter describedRetrieves all custom fields available in Jira. Shows custom field names, IDs (e.g., customfield_10071), and types. Useful for discovering what custom fields exist and their identifiers.
jira_get_comments4 of 4 parameters describedRetrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Supports pagination for issues with many comments.
jira_get_attachments1 of 1 parameter describedLists all attachments on a Jira issue. Returns attachment metadata including filename, size, MIME type, author, and download URL.
jira_get_transitions1 of 1 parameter describedRetrieves all available workflow transitions for a Jira issue. Use this to discover which status changes are possible for an issue before calling jira_transition_issue.
jira_create_issue11 of 11 parameters describedCreates a new Jira issue in the specified project. Supports setting issue type, priority, assignee, labels, components, and custom fields. Description format is controlled by the "format" parameter (default: markdown). For required custom fields, supply them via customFields (e.g., { "customfield_12345": { id: "..." } }). Returns the created issue with all details.
jira_update_issue11 of 11 parameters describedUpdates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, components, and fix versions. Description format is controlled by the "format" parameter (default: markdown). Only specified fields will be updated.
jira_add_comment4 of 4 parameters describedAdds a comment to an issue. Supports visibility restrictions for groups or roles. Comment format is controlled by the "format" parameter (default: markdown). Returns the created comment with author details and timestamp.
jira_create_subtask8 of 8 parameters describedCreates a subtask under an existing parent issue. Automatically determines the correct project and subtask issue type. Supports setting priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown).
jira_create_issue_link3 of 3 parameters describedCreates a link between two Jira issues. Supports common link types like "blocks", "relates", "duplicates", and "clones". Use this to establish relationships between issues.
jira_add_attachment5 of 5 parameters describedUploads an attachment (image, document, etc.) to a Jira issue. **EFFICIENT METHOD (recommended for large files):** - fileUrl: Provide URL to remote file - MINIMAL tokens (~60 tokens) Example: Upload to Dropbox/S3/imgur first, then provide URL **DIRECT METHOD (for small files):** - content: Base64 encoded content - WARNING: HIGH token cost (~330,000 tokens for 1MB file) Only suitable for small files (< 500 KB) Returns attachment metadata including ID and download URL. To reference the image in a comment or description, use wiki markup: !filename.png! or !filename.png|thumbnail!
jira_transition_issue6 of 6 parameters describedTransitions a Jira issue to a new workflow status (e.g., "To Do" -> "In Progress" -> "Done"). Use jira_get_transitions first to discover available transitions. Supports adding a comment and setting resolution during the transition.
jira_get_issue_graph6 of 6 parameters describedBuild a dependency/relationship graph starting from a seed issue. Returns a map of connected issues (parent/child hierarchy, blocks, relates to, duplicates, etc.) with nodes and edges, plus a Mermaid diagram for visualization. Use this to understand how issues are connected across epics, stories, and subtasks.
jira_delete_attachment1 of 1 parameter describedDeletes an attachment from Jira by its attachment ID. Use jira_get_attachments to find attachment IDs.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.