mcp-jira-stdio and mcp-server-atlassian-jira
These are competitors, as both are distinct Model Context Protocol (MCP) servers designed for integrating with Atlassian Jira, offering overlapping functionality for AI systems to interact with Jira data.
About mcp-jira-stdio
freema/mcp-jira-stdio
MCP server for Jira integration with stdio transport. Issue management, project tracking, and workflow automation via Model Context Protocol.
Provides granular Jira API access through 20+ tools covering projects, issues, comments, and metadata discovery—including JQL-based search, custom field introspection, and subtask creation. Built in TypeScript with Node.js 18+, it integrates directly into Claude Desktop and Claude Code via stdio transport, enabling AI assistants to autonomously query and modify Jira workflows without manual client switching.
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.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work