mcp-server-atlassian-jira and mcp-atlassian-server
Both tools are **competitors**, as they offer overlapping functionality by providing MCP servers to connect AI systems with Atlassian products like Jira, making them alternative solutions for the same core problem.
About mcp-server-atlassian-jira
aashari/mcp-server-atlassian-jira
Node.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.
Implements MCP (Model Context Protocol) with stdio transport, allowing seamless integration with Claude Desktop, Cursor AI, and other compatible LLM clients through a single standardized interface. Exposes five generic HTTP tools (GET, POST, PUT, PATCH, DELETE) covering the full Jira REST API v3, enabling AI systems to perform CRUD operations on projects, issues, comments, and worklogs. Features token-efficient TOON output format (30-60% reduction vs JSON), JMESPath filtering for response refinement, and automatic truncation handling for large responses exceeding 40k characters.
About mcp-atlassian-server
phuc-nt/mcp-atlassian-server
MCP server connecting AI assistants with Jira & Confluence for smart project management.
Exposes 48 Jira and Confluence operations through standardized MCP resources (read-only) and tools (mutations), supporting advanced workflows like sprint management, version history, and dashboard automation. Built as a Node.js MCP server compatible with Cline, Claude Desktop, and Cursor, it authenticates via Atlassian API tokens and communicates through the Model Context Protocol. The architecture separates read operations (resources) from write operations (tools) for clear permission boundaries and integrates directly with Jira API v3 and Confluence API v2.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work