MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields
Most planning and project tracking work still happens through a UI a human drives. Jira Cloud MCP server moves it into the conversation instead. MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields.
A Model Context Protocol server for interacting with Jira Cloud instances.
@aaronsb/jira-cloud-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 8 tools. What each one is for:
manage_jira_issue — Get, create, update, delete, move, transition, comment on, link, or traverse hierarchy of issuesmanage_jira_filter — Search for issues using JQL queries, or manage saved filtersmanage_jira_project — List projects or get project configuration and metadatamanage_jira_board — List boards or get board details and configurationmanage_jira_sprint — Manage sprints: create, start, close, and assign issues to sprintsqueue_jira_operations — Batch multiple operations with result references ($0.key) and error strategiesanalyze_jira_issues — Compute metrics, exact counts, and data cube analysis over issues selected by JQLCredentials — Generate an API token at Atlassian Account SettingsConfiguration is passed through the environment: JIRA_API_TOKEN, JIRA_EMAIL, JIRA_HOST. 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.
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 Cloud's toolset — manage_jira_issue, manage_jira_filter, manage_jira_project and 5 more — is a fair guide to whether it matches your workflow. It is maintained by aaronsb; 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 |
|---|---|
| manage_jira_issue | Get, create, update, delete, move, transition, comment on, link, or traverse hierarchy of issues |
| manage_jira_filter | Search for issues using JQL queries, or manage saved filters |
| manage_jira_project | List projects or get project configuration and metadata |
| manage_jira_board | List boards or get board details and configuration |
| manage_jira_sprint | Manage sprints: create, start, close, and assign issues to sprints |
| queue_jira_operations | Batch multiple operations with result references ($0.key) and error strategies |
| analyze_jira_issues | Compute metrics, exact counts, and data cube analysis over issues selected by JQL |
| Credentials | Generate an API token at [Atlassian Account Settings](https://id.atlassian.com/manage/api-tokens). |
### Manual (any MCP client)
```json
{
"mcpServers": {
"jira-cloud": {
"command": "npx",
"args": ["-y", "@aaronsb/jira-cloud-mcp"],
"env": {
"JIRA_API_TOKEN": "your-api-token",
"JIRA_EMAIL": "your-email",
"JIRA_HOST": "https://your-team.atlassian.net"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_EMAIL | Configuration value read at startup. | Optional |
| JIRA_HOST | Endpoint or connection string the server talks to. | Optional |
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.