About Jira MCP Server
Jira MCP Server connects AI assistants to Jira for project and issue operations. It supports searching and creating issues, checking project membership, and querying sprints.
Key features
- 01List accessible projects
- 02Retrieve issue details
- 03Search by project and assignee
- 04Check project members and assignments
- 05Create issues with custom fields
- 06Filter sprints by board, project, or state
Use cases
- 01Review a Jira issue before taking action
- 02Find issues assigned to a project member
- 03Create a task, bug, or story
- 04Check active sprints for a project
MCP support
An MCP server exposing Jira project, issue, membership, and sprint operations to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEJira MCP Server
A Model Context Protocol (MCP) server for Jira integration. This server allows AI assistants like Claude to interact with Jira using MCP.
Author: Samuel Rizzo
Features
- List all Jira projects
- Get detailed issue information
- Search issues by project and assignee
- List project members
- Check user's project membership and assigned issues
- Create new issues with custom fields
- List and query sprints with filtering options
Installation
# Clone the repository
git clone https://github.com/samuelrizzo/jira-mcp-server.git
cd jira-mcp-server
# Install dependencies
npm install
# Build the project
npm run build
Configuration
MCP Server Configuration
Add the following configuration to your cursor/windsurf mcp settings file:
{
"mcpServers": {
"jira-mcp": {
"command": "node",
"args": ["./dist/index.js"],
"env": {
"JIRA_HOST": "your-domain.atlassian.net",
"JIRA_EMAIL": "[email protected]",
"JIRA_API_TOKEN": "your-api-token-here"
}
}
}
}
Setting up API Access
-
Generate a Jira API token:
- Go to Atlassian Account Settings
- Click "Create API Token"
- Give it a name and click "Create"
- Copy the token (you'll need it for authentication)
-
Note your Jira host URL (e.g.,
your-domain.atlassian.net) and email address associated with your Atlassian account. -
Add these credentials to your MCP server configuration.
Available Tools
1. List Projects (mcp_jira_list_projects)
Lists all Jira projects the authenticated user has access to.
Parameters:
jiraHost: Your Jira domain (e.g., 'your-domain.atlassian.net')email: Your Jira emailapiToken: Your Jira API token
2. Get Issue Details (mcp_jira_get_issue)
Retrieves detailed information about a specific Jira issue.
Parameters:
issueKey: The Jira issue key (e.g., 'PROJECT-123')jiraHost: Your Jira domainemail: Your Jira emailapiToken: Your Jira API token
3. Search Issues (mcp_jira_search_issues)
Searches for issues in a specific project, optionally filtered by assignee.
Parameters:
projectKey: The Jira project keyassigneeName: (Optional) Filter issues by assignee namejiraHost: Your Jira domainemail: Your Jira emailapiToken: Your Jira API token
4. List Project Members (mcp_jira_list_project_members)
Lists all members of a specific Jira project.
Parameters:
projectKey: The Jira project keyjiraHost: Your Jira domainemail: Your Jira emailapiToken: Your Jira API token
5. Check User Issues (mcp_jira_check_user_issues)
Checks if a user is a member of a project and lists their assigned issues.
Parameters:
projectKey: The Jira project keyuserName: The display name of the user to checkjiraHost: Your Jira domainemail: Your Jira emailapiToken: Your Jira API token
6. Create Issue (mcp_jira_create_issue)
Creates a new issue in a Jira project with specified details.
Parameters:
projectKey: The Jira project keysummary: The title/summary of the issuedescription: Detailed description of the issueissueType: (Optional) Type of issue (e.g., 'Task', 'Bug', 'Story'), defaults to 'Task'assigneeName: (Optional) The display name of the person to assign the issue toreporterName: (Optional) The display name of the person reporting the issuesprintId: (Optional) ID of the sprint to add the issue tojiraHost: Your Jira domainemail: Your Jira emailapiToken: Your Jira API token
7. List Sprints (mcp_jira_list_sprints)
Lists current sprints in Jira with filtering options.
Parameters:
boardId: (Optional) Jira board ID to filter sprints by a specific boardprojectKey: (Optional) Project key to find sprints associated with the projectstate: (Optional) Sprint state to filter by (active, future, closed, or all), defaults to 'active'jiraHost: Your Jira domainemail: Your Jira emailapiToken: Your Jira API token
Usage Examples
Here are some example queries you can use with Claude:
"List all Jira projects in PROJECT"
"Get details for issue PROJECT-123"
"Search for issues assigned to John in PROJECT"
"List all members of PROJECT"
"Check what issues are assigned to Jane in PROJECT"
"Create a new bug issue titled 'Login page error' in PROJECT"
"List active sprints for PROJECT"
Continuous Development
This project is under active development. New tools and features are being added regularly to expand the integration capabilities with Jira. Future updates will include:
- Additional issue management tools
- Sprint and board management
- Advanced search and filtering options
- Custom field handling
- Workflow transitions
- And more!
Stay tuned by watching or starring the repository for updates.
Contributing
This is an open-source project and contributions are welcome! To contribute:
- Fork the repository
- Create your feature branch
- Make your changes
- Submit a pull request
Open Source
This code is completely open source. You are free to:
- Copy
- Modify
- Distribute
- Use commercially
- Use privately
No restrictions - do whatever you want with the code!
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.