Automatically exposes the entire Jira instance through MCP, providing access to issue management, project administration, user and permission management, dashboards, filters, webhooks, automation, and all other Jira Cloud API features with zero configuration overhead.
Jira MCP Server
A production-ready Jira MCP server using FastMCP 2.0's OpenAPI integration. Automatically exposes your entire Jira instance through the Model Context Protocol (MCP) with zero configuration overhead.
Features
- 🚀 Zero-maintenance OpenAPI integration - Automatically generates MCP tools from Jira's official API specification
- 🔐 Secure authentication - Uses Jira API tokens with environment variable support
- 🌐 Multiple transports - Support for stdio, HTTP, and SSE protocols
- ⚡ Fast and lightweight - Minimal overhead with async HTTP client
- 🔧 Production-ready - Type-safe, well-tested, and follows security best practices
- 📝 Self-documenting - All Jira API endpoints automatically become available as MCP tools
Quick Start
1. Installation
2. Setup Jira API Token
- Go to Atlassian Account Settings
- Create an API token
- Note your Jira instance URL (e.g.,
https://yourcompany.atlassian.net
)
3. Set Environment Variables
4. Run the Server
How It Works
The server automatically:
- Downloads Jira's official OpenAPI specification
- Generates MCP tools for every Jira API endpoint
- Authenticates requests using your API token
- Exposes your entire Jira instance through MCP
This means you get instant access to:
- Issue management (create, update, search, transition)
- Project administration
- User and permission management
- Dashboards and filters
- Webhooks and automation
- And every other Jira Cloud API feature!
Configuration
Environment Variables
Variable | Required | Default | Description |
---|---|---|---|
JIRA_BASE_URL | ✅ | - | Your Jira instance URL (e.g., https://company.atlassian.net ) |
JIRA_API_USER | ✅ | - | Your Jira username/email address |
JIRA_API_TOKEN | ✅ | - | Your Jira API token |
JIRA_TIMEOUT | ❌ | 30 | HTTP timeout in seconds |
MCP_TRANSPORT | ❌ | stdio | Transport method (stdio , http , sse ) |
MCP_PORT | ❌ | 8000 | Port for HTTP/SSE transports |
MCP_LOG_LEVEL | ❌ | INFO | Logging level (DEBUG , INFO , WARNING , ERROR ) |
Command Line Options
Integration with MCP Clients
Claude Desktop (Docker - Recommended)
Option 1: Using pre-built Docker image (easiest)
Option 2: Using environment variables (more secure)
Set your credentials in your shell profile (.bashrc
, .zshrc
, etc.):
Then use this config:
Option 3: Local installation (if you prefer)
Advanced Docker Usage
Running as HTTP Service (for multiple clients)
Other MCP Clients
The Docker image supports all MCP transport protocols:
- stdio: For local desktop applications (Claude Desktop, etc.)
- HTTP: For web applications and remote clients
- SSE: For real-time web applications
Example HTTP usage:
Docker
Build and run with Docker:
Development
Setup
Architecture
jira_mcp/config.py
: Pydantic models with environment variable loadingjira_mcp/auth.py
: HTTP client with Jira Basic Authjira_mcp/server.py
: FastMCP integration with OpenAPI spec fetchingjira_mcp/__main__.py
: CLI interface with environment-based configuration
Testing
The project includes 41 unit tests organized in tests/unit/
covering:
- Configuration validation and edge cases
- Authentication and HTTP client behavior
- Server initialization and error handling
- Environment variable parsing and type conversion
Troubleshooting
Common Issues
"Configuration error" on startup: Check that all required environment variables (JIRA_BASE_URL
, JIRA_API_USER
, JIRA_API_TOKEN
) are set.
Authentication errors: Verify your API token is correct and your email matches your Jira account.
Connection timeout: Check your JIRA_BASE_URL
is correct and accessible. Increase JIRA_TIMEOUT
if needed.
Claude Desktop not finding server: Ensure environment variables are available to GUI applications (may require restart or launchctl setenv
on macOS).
Getting Help
- Check the CLAUDE.md file for development guidance
- Review test files for usage examples
- Run
jira-mcp --help
for command line options
Security
- API tokens are stored in environment variables, never in code or config files
- All HTTP requests use TLS encryption
- No sensitive data is logged or exposed
- Follows OAuth 2.0 and Atlassian security best practices
License
MIT
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
A production-ready server that automatically exposes your entire Jira instance through the Model Context Protocol, allowing seamless interaction with Jira's API features including issue management, project administration, and user management.
Related MCP Servers
- -securityFlicense-qualityA server implementation that allows AI models to interact with Jira through the Model Context Protocol, enabling tasks like JQL searches and retrieving issue details.Last updated -Python
- AsecurityAlicenseAqualityA Model Context Protocol server that provides integration with Jira, allowing Large Language Models to interact with Jira projects, boards, sprints, and issues through natural language.Last updated -5872TypeScriptMIT License
- -securityAlicense-qualityA Model Context Protocol server that enables interaction with Jira's REST API using natural language commands, allowing users to manage Jira projects, issues, comments, and workflows through Claude Desktop and other MCP clients.Last updated -1PythonMIT License
- -securityAlicense-qualityA Simple Model Context Protocol server that enables AI assistants to interact with Jira, allowing operations like fetching tickets, adding comments, and updating ticket status.Last updated -1PythonApache 2.0