An opinionated Jira MCP server built from years of real-world software development experience.
Jira MCP is an MCP project maintained in the nguyenvanduocit/jira-mcp repository. The maintainer describes its purpose as “An opinionated Jira MCP server built from years of real-world software development experience”. Read the project documentation for the complete scope.
The project provides a local client configuration using docker. 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 |
|---|---|
| jira_get_issue | Retrieve detailed information about a specific issue including status, assignee, description, subtasks, and available transitions |
| jira_create_issue | Create a new issue with specified details (returns key, ID, and URL) |
| jira_create_child_issue | Create a child issue (sub-task) linked to a parent issue |
| jira_update_issue | Modify an existing issue's details (supports partial updates) |
| jira_list_issue_types | List all available issue types in a project with their IDs, names, and descriptions |
| jira_search_issue | Search for issues using JQL (Jira Query Language) with customizable fields and expand options |
| jira_list_sprints | List all active and future sprints for a specific board or project |
| jira_get_sprint | Retrieve detailed information about a specific sprint by its ID |
| jira_get_active_sprint | Get the currently active sprint for a given board or project |
| jira_search_sprint_by_name | Search for sprints by name with exact or partial matching |
| jira_list_statuses | Retrieve all available issue status IDs and their names for a project |
| jira_transition_issue | Transition an issue through its workflow using a valid transition ID |
| jira_add_comment | Add a comment to an issue (uses Atlassian Document Format) |
| jira_get_comments | Retrieve all comments from an issue |
| jira_add_worklog | Add a worklog entry to track time spent on an issue |
| jira_get_issue_history | Retrieve the complete change history of an issue |
| jira_get_related_issues | Retrieve issues that have a relationship (blocks, is blocked by, relates to, etc.) |
| jira_link_issues | Create a link between two issues, defining their relationship |
| jira_get_version | Retrieve detailed information about a specific project version |
| jira_list_project_versions | List all versions in a project with their details |
| jira_get_development_information | Retrieve branches, pull requests, and commits linked to an issue via development tool integrations (GitHub, GitLab, Bitbucket) |
{
"mcpServers": {
"jira": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"ATLASSIAN_HOST=https://your-company.atlassian.net",
"-e",
"ATLASSIAN_EMAIL=your-email@company.com",
"-e",
"ATLASSIAN_TOKEN=your-api-token",
"ghcr.io/nguyenvanduocit/jira-mcp:latest"
]
}
}
}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.