Jira MCP Server
A comprehensive, production-ready MCP server for seamless Jira Cloud integration, enabling AI agents and custom applications to manage boards, issues, users, projects, and workflows via natural language commands.
README
Jira MCP Server
A comprehensive, production-ready Model Context Protocol (MCP) server for seamless Jira Cloud integration. This enhanced version provides advanced features, robust error handling, and extensive tooling for AI agents, automation systems, and custom applications.
๐ Features
Core Functionality
- Board Management: List, filter, and manage Jira boards with detailed information
- Issue Operations: Create, update, search, transition, and manage issues comprehensively
- User Management: Search users, get user details, and manage assignments
- Project Administration: View projects, get detailed project information
- Time Tracking: Add and view work logs with flexible time formats
- Comment System: Add comments with rich text support (ADF format)
- Server Information: Monitor server status and health
Enhanced Features
- Rate Limiting: Intelligent API request throttling to respect Jira limits
- Comprehensive Logging: Configurable logging with multiple levels
- Error Handling: Robust error handling with detailed error messages
- Input Validation: Thorough validation of environment variables and inputs
- Modular Architecture: Clean, maintainable codebase with service-based architecture
- TypeScript Support: Full TypeScript implementation with comprehensive type definitions
- Rich Formatting: Beautiful markdown tables and formatted responses
- Advanced Search: Support for complex JQL queries with helpful examples
๐ ๏ธ Requirements
- Node.js: 18.0.0 or higher
- Jira Cloud: Access to a Jira Cloud instance
- API Token: Jira API Token (create here)
โ๏ธ Environment Variables
Create a .env file or set these environment variables:
JIRA_BASE_URL=https://your-company.atlassian.net
JIRA_EMAIL=your-email@company.com
JIRA_API_TOKEN=your-jira-api-token
LOG_LEVEL=INFO # Optional: ERROR, WARN, INFO, DEBUG
๐ Quick Start
Option 1: Using npx (Recommended)
# Run directly without installation
npx @orengrinker/jira-mcp-server
# With environment variables
JIRA_BASE_URL=https://company.atlassian.net \
JIRA_EMAIL=user@company.com \
JIRA_API_TOKEN=your-token \
npx @orengrinker/jira-mcp-server
Option 2: Claude Desktop Configuration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["@orengrinker/jira-mcp-server"],
"env": {
"JIRA_BASE_URL": "https://your-company.atlassian.net",
"JIRA_EMAIL": "your-email@company.com",
"JIRA_API_TOKEN": "your-jira-api-token",
"LOG_LEVEL": "INFO"
}
}
}
}
Option 3: Global Installation
npm install -g @orengrinker/jira-mcp-server
jira-mcp-server
Option 4: Local Development
git clone https://github.com/OrenGrinker/jira-mcp-server.git
cd jira-mcp-server
npm install
npm run build
node dist/index.js
๐งฐ Available Tools
Board Tools
get_boards- List all boards with optional filtering by type and projectget_board_details- Get comprehensive board informationget_board_issues- Get board issues with advanced filtering options
Issue Tools
search_issues- Search issues using JQL with flexible parametersget_issue_details- Get comprehensive issue informationcreate_issue- Create new issues with full field supportupdate_issue- Update existing issuestransition_issue- Move issues between statusesadd_comment- Add comments with rich text support
User Tools
get_current_user- Get authenticated user informationsearch_users- Find users by name, email, or usernameget_user_details- Get detailed user information
Project Tools
get_projects- List all accessible projectsget_project_details- Get comprehensive project information
Time Tracking Tools
add_worklog- Log work time with flexible formatsget_worklogs- View work logs for issues
System Tools
get_server_info- Get server status and information
๐ก Usage Examples
Natural Language Commands with Claude
Once configured with Claude Desktop, you can use natural language commands:
"Show me all my open issues in high priority"
"Create a new bug in PROJECT-X about login issues"
"Move ticket ABC-123 to In Progress"
"Log 2 hours of work on ABC-456 for code review"
"Add a comment to ABC-789 saying the fix is deployed"
"Show me all Scrum boards for the mobile project"
"Get details for issue ABC-100 including comments and worklogs"
"List all projects I have access to"
Using with MCP Inspector
# List all boards
npx @modelcontextprotocol/inspector \
npx @orengrinker/jira-mcp-server \
get_boards
# Search for your issues
npx @modelcontextprotocol/inspector \
npx @orengrinker/jira-mcp-server \
search_issues \
'{"jql": "assignee=currentUser() AND status!=Done"}'
# Create a new issue
npx @modelcontextprotocol/inspector \
npx @orengrinker/jira-mcp-server \
create_issue \
'{"projectKey": "PROJ", "issueType": "Task", "summary": "New task from MCP"}'
JQL Query Examples
# Your open issues
assignee = currentUser() AND status != Done
# Recent issues in a project
project = "MYPROJ" AND created >= -7d
# High priority bugs
priority = High AND issuetype = Bug
# Issues due this week
duedate >= startOfWeek() AND duedate <= endOfWeek()
# Unassigned issues in current sprint
assignee is EMPTY AND sprint in openSprints()
# Issues updated in the last 24 hours
updated >= -1d
# Epic issues with their child stories
"Epic Link" = PROJ-123 OR parent = PROJ-123
๐ง Configuration
Getting Your Jira API Token
- Go to Atlassian Account Settings
- Click "Create API token"
- Give it a descriptive name (e.g., "MCP Server")
- Copy the generated token
- Use it in your environment variables
Permissions Required
Your Jira user should have:
- Browse projects permission
- Create issues permission (for issue creation)
- Edit issues permission (for updates and transitions)
- Work on issues permission (for worklogs)
- Add comments permission
๐๏ธ Development
Setup
git clone https://github.com/OrenGrinker/jira-mcp-server.git
cd jira-mcp-server
npm install
Development Scripts
npm run dev # Start development server with hot reload
npm run build # Build for production
npm run clean # Clean build directory
npm run start # Start production server
npm run test # Run tests (when available)
Project Structure
src/
โโโ index.ts # Main server entry point
โโโ jiraApiClient.ts # Enhanced API client
โโโ toolRegistry.ts # Tool registration and routing
โโโ types/
โ โโโ index.ts # TypeScript type definitions
โโโ services/
โ โโโ index.ts # Service exports
โ โโโ boardService.ts # Board operations
โ โโโ issueService.ts # Issue operations
โ โโโ userService.ts # User operations
โ โโโ projectService.ts # Project operations
โ โโโ worklogService.ts # Worklog operations
โ โโโ serverService.ts # Server operations
โโโ utils/
โโโ logger.ts # Logging utility
โโโ rateLimiter.ts # Rate limiting
โโโ validation.ts # Input validation
โโโ formatters.ts # Response formatting
๐ Troubleshooting
Common Issues
-
Authentication Failed
- Verify your API token and email are correct
- Check that your Jira base URL is correct (should end with .atlassian.net for cloud)
- Ensure your API token hasn't expired
-
Permission Denied
- Verify your Jira user has the required permissions
- Check project-level permissions for specific operations
-
Network Errors
- Verify your Jira base URL is accessible
- Check firewall and proxy settings
- Ensure you're using HTTPS
-
Rate Limiting
- The server includes built-in rate limiting
- If you hit Jira's rate limits, wait and retry
- Consider reducing concurrent requests
Debug Mode
Enable debug logging:
export LOG_LEVEL=DEBUG
๐งช Testing
# Test the server connection
JIRA_BASE_URL=https://your-company.atlassian.net \
JIRA_EMAIL=your@email.com \
JIRA_API_TOKEN=your-token \
node dist/index.js
๐ค Contributing
We welcome contributions! Please follow these guidelines:
- Fork the repository
- Create a feature branch:
git checkout -b feature/amazing-feature - Make your changes following our coding standards
- Add tests for new functionality
- Run the build:
npm run build - Commit changes:
git commit -m 'Add amazing feature' - Push to branch:
git push origin feature/amazing-feature - Open a Pull Request
Coding Standards
- Follow TypeScript best practices
- Use meaningful variable and function names
- Add JSDoc comments for public APIs
- Follow conventional commit messages
- Ensure all builds pass
๐ Performance
- Rate Limiting: Built-in rate limiting respects Jira API limits
- Connection Pooling: Efficient HTTP connection management
- Error Recovery: Automatic retry logic for transient failures
- Memory Efficient: Streaming responses for large datasets
๐ Security
- No Credential Storage: Uses environment variables only
- Input Validation: All inputs are validated and sanitized
- Secure Defaults: Follows security best practices
- Audit Trail: Comprehensive logging for debugging
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
๐ Links
- GitHub Repository: https://github.com/OrenGrinker/jira-mcp-server
- NPM Package: @orengrinker/jira-mcp-server
- Jira Cloud REST API: Documentation
- Model Context Protocol: Specification
- Create API Tokens: Atlassian Guide
๐ Support
- Issues: GitHub Issues
- Documentation: Check this README and inline code documentation
- Feature Requests: Open an issue with the "enhancement" label
๐ Acknowledgments
- Built with the Model Context Protocol SDK
- Inspired by the MCP community and best practices
- Thanks to all contributors and users providing feedback
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.