Enables retrieving and searching JIRA issues using JQL (JIRA Query Language), with support for configurable field selection, pagination, and logging work on issues.
JIRA MCP Server
A simple Model Context Protocol (MCP) "vibe-coded" server for integrating JIRA with AI coding assistants. MCP is an open protocol that enables seamless integration between LLM applications and external data sources and tools.
Originally designed for Cursor IDE, this server now supports multiple AI coding assistants including Claude Code and Codex CLI.
BEWARE! Even this document is almost entirely written by AI coding assistant.
Features
Get JIRA issues by key
Search issues using JQL (JIRA Query Language)
Create and update issues (note: may have limitations with heavily customized JIRA projects)
Add comments to issues
Clone issues (useful for working around mandatory custom fields, but may have limitations with complex project configurations)
Configurable field selection
Pagination support
Detailed error handling and logging
Log work
Related MCP server: Cursor DB MCP Server
User Workflows
Search and Filter Flow
Issue Cloning Flow
For detailed technical architecture and system workflows, including issue lifecycle and authentication flows, see ARCHITECTURE.md.
About MCP
This server implements the Model Context Protocol specification, enabling AI coding assistants to seamlessly interact with JIRA data. The protocol standardizes how LLM applications communicate with external data sources and tools.
π Quick Integration
For AI Assistant Integration: See AI_INTEGRATION.md for complete setup guides for:
π€ Claude Code - Modern MCP integration
π― Cursor IDE - Original integration (multiple setup options)
π§ Codex CLI - See the Codex CLI section in AI_INTEGRATION.md
Setup
Create a virtual environment:
Install dependencies:
Configure environment variables: Create a
.envfile with:
Usage
Run the server:
Development
The project follows a modular structure:
Key Components
Models (
src/models/)IssueType,IssueArgs- Issue creation/update modelsIssueTransitionArgs- Issue state transition modelCloneIssueArgs- Issue cloning modelCommentArgs,GetCommentsArgs- Comment modelsLogWorkArgs- Work logging model
Core (
src/core/)JiraClient- Main JIRA API clientJiraConfig- Configuration managementError handling and logging
Operations (
src/operations/)Issue management (get, search, create, update, clone)
Comment handling (add, get)
Work logging
Project listing
The project follows the implementation plan outlined in IMPLEMENTATION_PLAN.md.
Current version: v0.4
β Basic JIRA integration
β Search functionality with JQL support
β Issue management (create, update, clone) with limitations for heavily customized projects
β Comment functionality
β Work logging
Related Links
Model Context Protocol - The main MCP project
MCP Python SDK - The SDK we use to implement this server
MCP Documentation - Protocol documentation and specifications
License
MIT
Security Considerations
This tool is primarily designed for personal workflow automation and individual developer use. Please be aware of the following security considerations:
β οΈ Usage Recommendations
Personal/Development Use: Ideal for individual developers managing their JIRA workflows
Small Team Use: Suitable for trusted team environments with proper security measures
NOT Recommended For:
Production deployment in its current form
Multi-tenant environments
Public-facing services
Processing sensitive/regulated data
π Security Requirements
If you choose to use this tool, please ensure:
Your JIRA instance uses HTTPS
You're using API tokens (not passwords) for authentication
Your
.envfile is properly secured and not committed to version controlYou understand the risks of running third-party tools with JIRA access
π‘οΈ Best Practices
Regularly rotate your API tokens
Monitor your JIRA audit logs for unexpected activity
Use the most recent version of the tool
Review the code before use in your environment
π Note on Enterprise Usage
This tool is not currently hardened for enterprise security requirements. If you need a solution for enterprise deployment, consider:
Implementing additional security controls
Conducting a security review
Contributing security improvements back to the project
Using official enterprise-grade alternatives
For security-related concerns or to report vulnerabilities, please open an issue or contact the maintainers directly.