A containerized Python MCP server for Cursor to provide access to Jira.
jira-mcp is an MCP project maintained in the redhat-ai-tools/jira-mcp repository. The maintainer describes its purpose as “A containerized Python MCP server for Cursor to provide access to Jira”. Read the project documentation for the complete scope.
The project provides a local client configuration using podman. Follow the repository’s build and installation steps before copying it, and replace example paths with the paths on your own computer.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| 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 |
{
"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"
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.