The most robust Jira MCP safe for internal corporate use.
The most robust Jira MCP safe for internal corporate use. Exposed over MCP by the jira mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Financial support from private and corporate sponsors ensures the tool's continued development.
Installation goes through your MCP client rather than a global install: point it at ghcr.io/ankitpokhrel/jira-cli on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Everything the assistant can do here goes through one of these:
Navigation — The lists are displayed in an interactive UI by default. - Use arrow keys or j, k, h, l characters to navigate through the list. - Use g and G toResources — The Resources tool exposed by this serverIssue — Issues are displayed in an interactive table view by default. You can output the results in a plain view using the --plain flagList — The list command lets you search and navigate the issues. The issues are sorted by created field in descending order by defaultCreate — The Create tool exposed by this serverEdit — The Edit tool exposed by this serverAssign — The Assign tool exposed by this serverView — The view command lets you see issue details in a terminal. Atlassian document is roughly converted to Markdown and is nicely displayed in theLink — The Link tool exposed by this serverUnlink — The Unlink tool exposed by this serverClone — The clone command lets you clone an issue. You can update fields like summary, priority, assignee, labels, and components when cloning the issue. TheDelete — The Delete tool exposed by this serverYou will need one environment variable: JIRA_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jira MCP's toolset — Navigation, Resources, Issue and 10 more — is a fair guide to whether it matches your workflow.
This entry was verified against Jira MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Navigation | The lists are displayed in an interactive UI by default. - Use arrow keys or j, k, h, l characters to navigate through the list. - Use g and G to quickly navigate to the top and bottom respectively. - Use CTRL + f to scr |
| Resources | The Resources tool exposed by this server. |
| Issue | Issues are displayed in an interactive table view by default. You can output the results in a plain view using the --plain flag. |
| List | The list command lets you search and navigate the issues. The issues are sorted by created field in descending order by default. |
| Create | The Create tool exposed by this server. |
| Edit | The Edit tool exposed by this server. |
| Assign | The Assign tool exposed by this server. |
| View | The view command lets you see issue details in a terminal. Atlassian document is roughly converted to Markdown and is nicely displayed in the terminal. |
| Link | The Link tool exposed by this server. |
| Unlink | The Unlink tool exposed by this server. |
| Clone | The clone command lets you clone an issue. You can update fields like summary, priority, assignee, labels, and components when cloning the issue. The command also allows you to replace a part of the string (case-sensitiv |
| Delete | The Delete tool exposed by this server. |
| Comment | The comment command provides a list of sub-commands to manage issue comments. |
{
"mcpServers": {
"jira-xaviercollantes-dev": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/ankitpokhrel/jira-cli"],
"env": {
"JIRA_API_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
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.