This is a Model Context Protocol (MCP) server implementation for the Jira 9.12.14 API. It allows AI models like Claude to securely interact with Jira through well-defined tools.
- JQL Search: Execute JQL queries to find issues in Jira
- Get Issue: Retrieve detailed information about a specific issue by ID or key
- Node.js (v16 or higher)
- npm or yarn
- A Jira instance
- Authentication credentials for Jira API
The easiest way to use this MCP server is with npx:
# Create a directory for your configuration
mkdir jira-mcp && cd jira-mcp
# Create .env file with your credentials
cat > .env << EOL
JIRA_API_URL=https://your-domain.atlassian.net
JIRA_AUTH_TOKEN=your-token-here
EOL
# Run the server directly
npx @andrewyun/jira-9-12-14-mcp-server
- Clone the repository
- Install dependencies:
npm install
- Build the project:
npm run build
The server reads configuration from a .env
file in the current directory. Create a file named .env
with the following settings:
JIRA_API_URL=https://your-domain.atlassian.net
JIRA_AUTH_TOKEN=your-jira-token
You must create this file in the directory where you run the server.
As an alternative to the .env file, you can configure the server using MCP JSON environment variables. Update your Claude for Desktop configuration in the mcpServers
section:
{
"mcpServers": {
"jira": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/jira-9.12.14-mcp-server/dist/index.js"
],
"env": {
"MCP_JIRA_API_URL": "https://your-domain.atlassian.net",
"MCP_JIRA_AUTH_TOKEN": "your-jira-token"
}
}
}
}
Using the MCP JSON environment variables means you don't need to create a .env file.
JIRA_API_URL
orMCP_JIRA_API_URL
: The base URL of your Jira instance (e.g.,https://your-domain.atlassian.net
)JIRA_AUTH_TOKEN
orMCP_JIRA_AUTH_TOKEN
: Your Jira API token or Personal Access Token (PAT)
- Log in to your Atlassian account
- Go to Account Settings > Security > Create and manage API tokens
- Click "Create API token"
- Give it a name like "MCP Server"
- Copy the generated token to your
.env
file or MCP JSON configuration
npm start
- Open your Claude for Desktop App configuration at
~/Library/Application Support/Claude/claude_desktop_config.json
(MacOS) or%AppData%\Claude\claude_desktop_config.json
(Windows) - Add the server configuration:
{
"mcpServers": {
"jira": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/jira-9.12.14-mcp-server/dist/index.js"
],
"env": {
"MCP_JIRA_API_URL": "https://your-domain.atlassian.net",
"MCP_JIRA_AUTH_TOKEN": "your-jira-token"
}
}
}
}
Replace /ABSOLUTE/PATH/TO/
with the actual path to the server on your system.
If you installed via npx, your Claude configuration would look like:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"--yes",
"@andrewyun/jira-9-12-14-mcp-server"
],
"env": {
"MCP_JIRA_API_URL": "https://your-domain.atlassian.net",
"MCP_JIRA_AUTH_TOKEN": "your-jira-token"
}
}
}
}
Important: If you're using the MCP JSON environment variables, you don't need a .env
file. If you're not using MCP JSON environment variables, make sure you have a .env
file in your home directory or in the directory where Claude for Desktop is installed when using npx.
Executes JQL queries to find issues in Jira.
Parameters:
jql
(required): JQL query stringfields
(optional): List of fields to return for each issuemaxResults
(optional): Maximum number of results to returnstartAt
(optional): Index of the first result to returnexpand
(optional): Additional information to include in the response
Retrieves detailed information about a specific issue by ID or key.
Parameters:
issueIdOrKey
(required): ID or key of the issuefields
(optional): List of fields to include in the responseexpand
(optional): Additional information to include in the responseproperties
(optional): Properties to include in the responsefailFast
(optional): Whether to fail quickly on errors (default: false)
If you see errors like JIRA_API_URL environment variable is required
, make sure you:
- Have created a
.env
file in the directory where you're running the server, OR - Have provided
MCP_JIRA_API_URL
andMCP_JIRA_AUTH_TOKEN
in your Claude for Desktop configuration MIT