JIRA STDIO MCP Server
Configuration
View docs{
"mcpServers": {
"hackdonalds-jira-mcp": {
"command": "npx",
"args": [
"@hackdonalds/jira-mcp"
],
"env": {
"JIRA_EMAIL": "YOUR_EMAIL (optional)",
"JIRA_BASE_URL": "https://your-jira-instance.com",
"JIRA_API_TOKEN": "YOUR_API_TOKEN"
}
}
}
}You can interact with JIRA through a dedicated MCP server that exposes standardized tools to read, create, update, and manage JIRA issues. This enables AI assistants and automation workflows to perform common JIRA actions reliably and consistently.
Connect your MCP client to the JIRA MCP Server using the provided commands. You will access a set of tools such as getting issue details, searching issues with JQL, creating issues, updating fields, transitioning workflows, and adding comments. Use these tools in your prompts to perform specific JIRA tasks and to retrieve structured responses that your assistant can act on.
Typical usage patterns include: querying issues youβre assigned to, creating new tasks in a project, updating task fields like summary or description, moving issues through statuses, and appending comments for collaboration. Each tool accepts a defined set of arguments and returns structured results that your client can parse and display.
Prerequisites you need before installing the MCP server are listed here. Ensure you have Node.js 18.0 or higher installed, and an active JIRA instance with API token access.
Choose one of the installation methods below to start the MCP server quickly or set it up for repeated use.
Option 1 β Quick Start with npx (recommended)
npx @hackdonalds/jira-mcp
Option 2 β Install Globally
npm install -g @hackdonalds/jira-mcp
jira-mcp
Option 3 β Install from Source
1. git clone <repository-url>
2. cd jira-mcp
3. npm install
4. npm start
You can also run directly:
node server.jsSet up your environment variables before running the server. You will provide your JIRA instance URL, a Personal Access Token, and optionally your account email for logging.
export JIRA_BASE_URL="https://your-jira-instance.com"
export JIRA_API_TOKEN="your-api-token"
export JIRA_EMAIL="[email protected]" # Optional
# Or create a .env file and populate these values
cp .env.example .env
# Edit .env with your JIRA credentialsThe server uses Bearer token authentication with the Personal Access Token. The JIRA_EMAIL variable is optional and primarily used for logging.
Supported JIRA versions include Atlassian Cloud, JIRA Server 9.0+, and JIRA Data Center.
Get details of a specific JIRA issue by key
Search issues using JQL with pagination support
Create a new issue with project, issue type, summary, and optional fields
Update an existing issue's fields such as summary, description, assignee, and priority
Transition an issue to a new status with an optional comment
Add a comment to an existing issue