Jira
About
A server for querying Jira issues, requiring a Jira token for authentication.
Details
- Author
- redhat-ai-tools
- Categories
- Productivity, Project Management
Jump to
Setup
Install Jira in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/redhat-ai-tools/jira-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
A containerized Python MCP server for Cursor to provide access to Jira.
[!IMPORTANT] This project is experimental and was initially created as a learning exercise. Be aware there are more capable and mature Jira MCP solutions available, such assooperset/mcp-atlassian, and Atlassian's ownMCP Server.
See alsoredhat-ai-tools/jira-mcp-snowflakewhich provides another way to access Red Hat Jira data.
- Go toRed Hat Jira Personal Access Tokensand create a token
- Create a .env file similar toexample.env
- In Cursor go to "Settings", "Tools & Integrations", and click "New MCP Server"
- Paste in the following JSON, (or insert just thejiraMcpobject under themcpServerskey).
- Update"/path/to/your/dotenv/file.env"to point to the file from step 1.
- Save
{ "mcpServers": { "jiraMcp": { "command": "podman", "args": [ "run", "-i", "--rm", "--env-file", "/path/to/your/dotenv/file.env", "quay.io/sbaird/jira-mcp:latest" ], "description": "A containerized MCP server to query Jira issues" } } }
- podman- Install withsudo dnf install podman(Fedora/RHEL) orbrew install podman(macOS)
- yq- Install withsudo dnf install yq(Fedora/RHEL) orbrew install yq(macOS)
- make- Usually pre-installed on most systems
git clone git@github.com:redhat-ai-tools/jira-mcp.git cd jira-mcp
- Build the image & configure Cursor
This also creates a~/.rh-jira-mcp.envfile likethis.
Decide whether to enable write operations
Enabling your MCP server to make edits to Jira can be very useful, but can also cause a lot of problems if you are not careful in how you use the MCP tools. By default, the server has write operations turned off. If you want to turn it on, edit the.rh-jira-mcp.envfile in your home directory to setJIRA_ENABLE_WRITE=true.
To confirm it's working, run Cursor, go to Settings and click on "Tools & Integrations". Under MCP Tools you should see "jiraMcp" with 20 tools enabled ifJIRA_ENABLE_WRITE=false(the default value) or 30 tools enabled ifJIRA_ENABLE_WRITE=true.
Using with an HTTP-based MCP application
If you want to use this MCP server with an application that communicates via HTTP, then you need to run the server with an HTTP-based transport mechanism. Here is an example of how to do this using Streamable HTTP, which is the current recommended http-based transport mechanism for MCP:
export $(grep -v '^#' ~/.rh-jira-mcp.env | xargs) && python server.py --transport http --port 3075
Here is an example of how to do this using SSE, which is a deprecated http-based transport mechanism (e.g., because you have an older MCP client application that depends on SSE):
export $(grep -v '^#' ~/.rh-jira-mcp.env | xargs) && python server.py --transport sse --port 3075
For either Streamable HTTP or SSE, the JIRA_API_KEY in your environment is ignored (and not neeed). This is an important security feature, because otherwise anyone who had access to the HTTP service would have access to the account information for whoever configured and ran that server. Instead, calling applications must send in their own Jira token as a Bearer token. Here is an example of how to do that using Llama Stack:
from llama_stack_client import LlamaStackClient client = LlamaStackClient(base_url=LLAMA_STACK_URL) mcp_llama_stack_client_response = client.responses.create( model=LLAMA_STACK_MODEL_ID, input="Tell me about RHAISTRAT-24.", tools=[ { "type": "mcp", "server_url": JIRA_MCP_URL, "server_label": "Jira_tools", "headers": { "Authorization": f"Bearer {JIRA_API_TOKEN}" } } ] )
This MCP server provides the following tools:
- get_jira- Get details for a specific Jira issue by key.
- search_issues- Search issues using JQL
- create_issue- Create a new Jira issue with summary, description, type, priority, and assignee
- update_issue- Update an existing issue's summary, description, priority, or assignee
- delete_issue- Delete a Jira issue (use with caution)
- get_issue_comments- Get all comments for a Jira issue
- add_comment- Add a comment to a Jira issue
- delete_comment- Delete a comment from a Jira issue
- assign_issue- Assign a Jira issue to a user
- unassign_issue- Unassign a Jira issue
- transition_issue- Transition a Jira issue to a new status (e.g., "In Progress", "Done")
- get_issue_transitions- Get available transitions for a Jira issue
- add_issue_labels- Add labels to a Jira issue
- remove_issue_labels- Remove labels from a Jira issue
- list_projects- List all projects
- get_project- Get project details by key
- get_project_components- Get components for a project
- get_project_versions- Get versions for a project
- get_project_roles- Get roles for a project
- get_project_permission_scheme- Get permission scheme for a project
- get_project_issue_types- Get issue types for a project
- list_boards- List all boards
- list_sprints- List sprints for a board
- get_sprint- Get sprint details by ID
- get_sprints_by_name- Get sprints by name for a board, optionally filtered by state
- search_users- Search users by query
- get_user- Get user details by account ID
- get_current_user- Get current user info
- get_assignable_users_for_project- Get assignable users for a project
- get_assignable_users_for_issue- Get assignable users for an issue
- make build- Build the image
- make run- Run the container
- make clean- Clean up the built image
- make cursor-config- Modify~/.cursor/mcp.jsonto install this MCP Server
- make setup- Builds the image, configures Cursor, and creates~/.rh-jira-mcp.envif it doesn't exist
- Confirm thatmake runworks
- Check that the JIRA_API_TOKEN is correct
- Verify the image was built successfully withpodman images jira-mcp
- Go to the "Output" tab in Cursor's bottom pane, choose "MCP Logs" from the drop-down select and examine the logs there
- (MacOS) jiraMcp shows up in Cursor tools section but shows no active tools:
- Edit args section of jiraMcp of yourmcp.jsonfile to include your full path to the.rh-jira-mcp.envfile.
- Example:"~/.rh-jira-mcp.env",to"/Users/your_username/.rh-jira-mcp.env",
- Restart Cursor after configuration changes
- Check Cursor's developer console for error messages
- Verify the Jira URL is accessible from your network
This project is licensed under the MIT License. See theLICENSEfile for details.
Interact with Atlassian tools like Confluence and Jira.
Integrates AI with Atlassian Jira to manage projects, search for issues, and view development information like commits and pull requests.
Integrate with Jira's REST API to manage projects, track issues, and perform analytics.
Interact with Jira to manage issues, projects, and workflows using the Jira Cloud Platform REST API.
An MCP server for interacting with Jira's REST API to manage projects, issues, and users.
Interact with JIRA to search for issues using JQL and retrieve detailed issue information.
Access and manage JIRA issues, projects, and users with optimized data payloads for AI context windows.
Integrate with JIRA to allow AI assistants to directly interact with JIRA issues.
Integrate Atlassian JIRA into any MCP-compatible application to manage issues and projects.
MCP server for connecting AI assistants to your own Jira instance
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



