Connects to Jira Cloud to search and retrieve issue details for use with Model Context Protocol (MCP).
Connects to Jira Cloud to search and retrieve issue details for use with Model Context Protocol (MCP). Exposed over MCP by the jira mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Model Context Protocol (MCP) server for Jira Cloud products. This integration is designed specifically for Jira Cloud instances and does not support Jira Server or Data Center deployments.
Everything the assistant can do here goes through one of these:
jira_get_issue — Get details of a specific Jira issueInputs — - issue_key (string): Jira issue key (e.g., 'PROJ-123')Tools — The Tools tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Jira's toolset — jira_get_issue, Inputs, Tools — is a fair guide to whether it matches your workflow. It is maintained by vurtnec; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| jira_get_issue | Get details of a specific Jira issue |
| Inputs | - issue_key (string): Jira issue key (e.g., 'PROJ-123') |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"-y",
"/your/project/path/mcp-jira",
"--jira-url",
"https://your-domain.atlassian.net",
"--jira-username",
"your.email@domain.com",
"--jira-api-token",
"your_api_token"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
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.