Jira

This MCP server provides a natural language interface to Jira, enabling you to query and manage projects, issues, subtasks, and dependencies through Jira's API. You can use it to retrieve issues with or without JQL, create and update issues and subtasks, manage issue links, and configure workflows. The server exposes tools for user management, issue type handling, link types, and full issue management workflows, making it suitable for delegating PM tasks or querying Jira data via natural language prompts. To use it, ensure the MCP server is running with the correct environment variables for your Jira instance, connect Claude Desktop or your chosen controller, and then issue structured requests that map to the available tool calls (e.g., get issues for a project, create a task, or define a dependency between issues).

When interacting with the server, consider providing precise IDs like project keys, issue keys, and account IDs where required. The tooling supports both basic authentication and PAT-based authentication, so choose the method that aligns with your Jira deployment and security requirements. The server also supports common Jira operations such as listing issue types, listing link types, and performing updates with status and priority changes.

Prerequisites:

• Node.js installed (version compatible with the server project)
• Git installed
• Access to your Jira instance with suitable permissions

Installation steps:

1. Clone the repository:

git clone https://github.com/George5562/Jira-MCP-Server.git
cd Jira-MCP-Server

2. Install dependencies:

npm install

3. Configure environment variables: Create a .env file or set environment variables in your runtime environment with the following required fields:

JIRA_HOST=your-instance.atlassian.net
JIRA_API_TOKEN=your-api-token
JIRA_AUTH_TYPE=basic  # or bearer for PAT

If using PAT (bearer):

JIRA_HOST=your-instance.atlassian.net
JIRA_API_TOKEN=your-personal-access-token
JIRA_AUTH_TYPE=bearer

4. Build the project (if applicable):

npm run build

5. Start the server:

npm start

Notes and tips:

• When using PAT authentication, prefer JIRA_AUTH_TYPE=bearer and ensure your PAT has the necessary scopes.
• If your Jira instance requires a specific API version, set JIRA_API_VERSION accordingly (default is 3).
• For Claude Desktop integration, ensure Claude is configured to point at the MCP server using the correct node path and the built index.js path (build/index.js).
• If you encounter authentication errors, double-check that JIRA_HOST includes the proper domain (with or without https) and that your tokens are valid.
• For production deployments, consider restricting environment variables and using a dedicated service account with minimal required permissions.