MCP server for Jira Cloud — issues, search, comments, attachments, transitions.
MCP server for Jira Cloud — issues, search, comments, attachments, transitions. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Model Context Protocol (MCP) server for Jira API integration. Enables reading, writing, and managing Jira issues and projects directly from your MCP client (e.g., Claude Desktop).
The server publishes 4 tools. What each one is for:
Projects — The Projects tool exposed by this serverIssues — The Issues tool exposed by this serverComments — The Comments tool exposed by this serverTesting — The Testing tool exposed by this serverConfiguration is passed through the environment: JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as mcp-jira-stdio, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
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. MCP's toolset — Projects, Issues, Comments and 1 more — is a fair guide to whether it matches your workflow. It is maintained by freema; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Projects | The Projects tool exposed by this server. |
| Issues | The Issues tool exposed by this server. |
| Comments | The Comments tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
#### Alternative: Using npx
```json
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["mcp-jira-stdio"],
"env": {
"JIRA_BASE_URL": "https://your-instance.atlassian.net",
"JIRA_EMAIL": "your-email@example.com",
"JIRA_API_TOKEN": "your-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| JIRA_EMAIL | Configuration value read at startup. | Optional |
| 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.