A
licenseB
qualityD
maintenanceProvides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.
6
6 npm
3
MIT
Personal JIRA MCP
by yuezheng2006
Related Servers
Alternatives to Personal JIRA MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to manage JIRA issues, workflows, and tasks through a standardized MCP interface, facilitating real-time updates and seamless interaction with JIRA's API.10MIT
- AlicenseNot gradedqualityFmaintenanceA simple MCP server that provides access to Jira issues from Cursor AI, allowing users to reference and query Jira tickets directly in the chat panel.17MIT
- AlicenseCqualityDmaintenanceAn MCP server that enables communication with Jira, allowing users to perform operations like getting, searching, creating, and editing issues through natural language interaction.130 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to interact with Atlassian products (Confluence and Jira) for content management, issue tracking, and project management through a standardized interface.2,649 npm6MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables AI assistants to create and manage JIRA issues with rich markdown formatting and automatic conversion to Atlassian Document Format.4MIT
TDQS
C2.4/5.0
Scored across 12 tools
Disambiguation3/5
There is significant overlap between attachment-related tools (download_all_attachments, get_attachment_by_filename, get_issue_attachment, get_issue_attachments, getIssues includes attachments) that could cause confusion about which to use. However, core issue operations (create, get, update, search) and project operations are clearly distinct.
Naming Consistency2/5
The naming is inconsistent with mixed conventions: most tools use snake_case (create_issue, get_issue), but getIssues uses camelCase. There's also redundancy in naming (get_issue_attachment vs get_attachment_by_filename) and unclear verb choices (debug_issue_fields stands out as different from other CRUD-style names).
Tool Count4/5
12 tools is reasonable for a JIRA server covering issues, projects, and attachments. While there are some redundant tools, the count aligns well with the domain scope and doesn't feel excessive or insufficient for basic JIRA operations.
Completeness4/5
The toolset covers core JIRA workflows well: CRUD for issues (create, get, update, search), project access (get, list), and attachment handling. Minor gaps include no delete operations for issues or attachments, and debug_issue_fields is a niche tool that doesn't fit standard CRUD patterns, but agents can work around these limitations.