Integrates JIRA directly into the Cursor IDE via the Model Context Protocol.
Most planning and project tracking work still happens through a UI a human drives. Jira MCP server moves it into the conversation instead. Integrates JIRA directly into the Cursor IDE via the Model Context Protocol.
A powerful Model Context Protocol (MCP) server that brings Atlassian JIRA integration directly to any editor or application that supports MCP
The server publishes 14 tools. What each one is for:
TypeScript — first toolingjira_get_assigned_issues — Retrieves all issues assigned to youjira_get_issue — Gets detailed information about a specific issuejira_get_issue_comments — Retrieves comments for a specific issue with configurable optionsjira_create_issue — Create new JIRA issues with comprehensive field supportjira_update_issue — Update existing issues with field changes and status transitionsjira_get_projects — Retrieve and browse JIRA projects with filtering optionsjira_get_boards — Get JIRA boards (Scrum/Kanban) with advanced filteringjira_get_sprints — Retrieve sprint information for agile project managementjira_add_worklog — Add time tracking entries to issuesjira_get_worklogs — Retrieve worklog entries for issues with date filteringjira_update_worklog — Update existing worklog entriesSetup 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.
Configuration is passed through the environment: JIRA_HOST, JIRA_USERNAME, 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.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Jira's toolset — TypeScript, jira_get_assigned_issues, jira_get_issue and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Dsazz; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| TypeScript | first tooling |
| jira_get_assigned_issues | Retrieves all issues assigned to you |
| jira_get_issue | Gets detailed information about a specific issue |
| jira_get_issue_comments | Retrieves comments for a specific issue with configurable options |
| jira_create_issue | Create new JIRA issues with comprehensive field support |
| jira_update_issue | Update existing issues with field changes and status transitions |
| jira_get_projects | Retrieve and browse JIRA projects with filtering options |
| jira_get_boards | Get JIRA boards (Scrum/Kanban) with advanced filtering |
| jira_get_sprints | Retrieve sprint information for agile project management |
| jira_add_worklog | Add time tracking entries to issues |
| jira_get_worklogs | Retrieve worklog entries for issues with date filtering |
| jira_update_worklog | Update existing worklog entries |
| jira_delete_worklog | Delete worklog entries from issues |
| jira_get_current_user | Get current authenticated user information |
{
"mcpServers": {
"JIRA Tools": {
"command": "bunx",
"args": ["-y", "@dsazz/mcp-jira@latest"],
"env": {
"JIRA_HOST": "https://your-domain.atlassian.net",
"JIRA_USERNAME": "your-email@example.com",
"JIRA_API_TOKEN": "your-jira-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_HOST | Endpoint or connection string the server talks to. | Optional |
| JIRA_USERNAME | 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.