Jira MCP Server
Allows interaction with Jira, providing tools for listing projects, getting issue details, searching issues, managing project members, creating issues with custom fields, and querying sprints with filtering options.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Jira MCP Server show me all open issues assigned to me in the PROJECT-123 sprint"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Jira 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
Related MCP server: Jira MCP Server
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 buildConfiguration
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": "your-email@example.com",
"JIRA_API_TOKEN": "your-api-token-here"
}
}
}
}Setting up API Access
Generate a Jira API token:
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
Available Tools
7 toolsjira_check_user_issuesC
Checks if a user is a member of a project and lists their assigned issues
Inputs: projectKey (required), userName (required), jiraHost, email, +1 more.
jira_create_issueC
Creates a new issue in a Jira project with specified details
Inputs: projectKey (required), summary (required), description (required), jiraHost, +6 more.
jira_get_issueC
Retrieves details of a specific Jira issue by key
Inputs: issueKey (required), jiraHost, email, apiToken.
jira_list_project_membersC
Lists all members of a specific Jira project
Inputs: projectKey (required), jiraHost, email, apiToken.
jira_list_projectsC
Lists all Jira projects the user has access to
Inputs: jiraHost, email, apiToken.
jira_list_sprintsC
Lists current sprints in Jira with filtering options
Inputs: jiraHost, email, apiToken, boardId, +2 more.
jira_search_issuesC
Searches for Jira issues by project and assignee
Inputs: projectKey (required), jiraHost, email, apiToken, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose targeting specific Jira resources and actions, such as checking user issues, creating issues, getting issue details, listing project members, listing projects, listing sprints, and searching issues. There is no overlap or ambiguity between these functions.
All tool names follow a consistent 'jira_verb_noun' pattern with snake_case, such as jira_create_issue and jira_list_projects. This predictable naming scheme makes it easy for agents to understand and select the right tool.
With 7 tools, this server is well-scoped for Jira operations, covering core functionalities like issue management, project access, and sprint tracking. Each tool earns its place without being overwhelming or insufficient for the domain.
The toolset provides good coverage for basic Jira workflows, including issue CRUD (create, get, search), project and member listing, and sprint management. A minor gap exists in missing update and delete operations for issues, which agents might need to work around.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- FlicenseDqualityDmaintenanceA Model Context Protocol server that enables integration with JIRA, allowing users to interact with JIRA tasks and issues through Claude AI assistant.33-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides integration with Jira, allowing Large Language Models to interact with Jira projects, boards, sprints, and issues through natural language.539 npm3MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Jira Cloud instances, providing capabilities for issue management, project listing, and JQL search.11,575 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for integrating JIRA with Claude, enabling AI assistants to create, search, update, and link JIRA tickets, as well as manage Zephyr test steps through natural language.876 npm7MIT