Best for
- Teams using Jira for project management
- Users who want to manage tasks via natural language with AI assistants
- Developers needing to automate common PM operations like assignment and status updates
J
Jira MCP Server
Community
Interact with Jira using natural language to manage projects efficiently.
GitHub source repository ↗
42FMRS · D
This MCP server simplifies Jira operations through natural language, suitable for teams using Jira. It provides comprehensive issue management features, but requires valid credentials and attention to delete operation risks.
This is an MCP server that enables interaction with Jira using natural language, allowing users to retrieve information and modify projects. It supports project creation and configuration, issue and subtask management, issue linking and dependencies, and automated issue workflows.
Tools
GetUserByEmail
Get a user's account ID by email.
GetAllIssueTypes
List all available issue types.
GetAllIssueLinkTypes
List all available issue link types.
GetIssuesFromProject
Get issues from a project with optional JQL filtering.
CreateIssue
Create a standard issue.
CreateSubtask
Create a subtask.
UpdateIssue
Update issue fields.
CreateIssueLink
Create a link between issues.
DeleteIssue
Delete a single issue.
DeleteIssueWithSubtasks
Delete an issue along with its subtasks.
DeleteMultipleIssues
Delete multiple issues at once.
Setup
- Clone the repository: git clone https://github.com/George5562/Jira-MCP-Server.git
- Install dependencies: npm install
- Configure environment variables: Create a .env file with JIRA_HOST, JIRA_API_TOKEN, and JIRA_AUTH_TYPE (optional JIRA_EMAIL for basic auth)
- Build the project: npm run build
- Start the server: npm start
For Claude Desktop, add the mcpServers entry to the configuration file (claude_desktop_config.json).
claude_desktop_config.json
{
"mcpServers": {
"jira-server": {
"command": "node",
"args": [
"/path/to/jira-server/build/index.js"
],
"cwd": "/path/to/jira-server",
"env": {
"JIRA_HOST": "your-jira-instance.atlassian.net",
"JIRA_EMAIL": "[email protected]",
"JIRA_API_TOKEN": "your-api-token",
"JIRA_AUTH_TYPE": "basic"
}
}
}
}
Fit and risk
Not for
- Users who do not use Jira
- Scenarios requiring complex permission management
- Developers who need direct API access without natural language interaction
Required permissions
- Read access to Jira projects, issues, and user information
- Create, update, and delete issues and subtasks
- Create issue links (dependencies)
- Requires JIRA_HOST, JIRA_API_TOKEN or PAT, and JIRA_EMAIL for basic auth
Risks and side effects
- If API tokens are leaked, attackers can access and modify Jira data
- Delete operations are irreversible and may cause data loss, especially when deleting subtasks
- Misconfiguration may lead to permission issues or API rate limits
- Dependent on Jira API version, subject to instance limitations
Troubleshooting
- If connection fails, check that JIRA_HOST is correct (e.g., your-instance.atlassian.net), JIRA_API_TOKEN is valid, JIRA_AUTH_TYPE is set correctly (basic or bearer), and network connectivity to the Jira instance is available. For PAT, ensure PAT support is enabled.
Use cases
List all issues in a project
Create new issues or subtasks and assign them to team members
Query issues with JQL, such as tasks assigned to me
Update issue status, priority, description, etc.
Establish dependencies between issues (e.g., blocks/is blocked by)
Supported clients
Claude DesktopFull support
CursorFull support