Skip to content
Agentmart
Submit a tool

Jira Cloud

MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields

Connector by aaronsb · GitHub account verified by the MCP Registry

IndexedLicense unknownLocal (stdio)★ 4
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/aaronsb-jira-cloud

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
1 read · 8 write · 1 delete
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 10

Read from the source code; the running server may list different tools.

Read 1 · Look things up without changing anything.

  • analyze_jira_issues

Write 8 · Create, change, send or run things.

  • manage_jira_board
  • manage_jira_filter
  • manage_jira_media
  • manage_jira_plan
  • manage_jira_project
  • manage_jira_sprint
  • manage_workspace
  • queue_jira_operations

Delete 1 · Delete, drop, revoke or wipe things.

  • manage_jira_issue

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • JIRA_API_TOKEN

Other settings (environment variables or headers).

  • JIRA_EMAIL
  • JIRA_HOST

Files it touches

  • Any path the agent passes to its tools

Tools (10)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • analyze_jira_issues

    Compute project metrics over issues selected by JQL or a saved filter. For counting and breakdown questions ("how many by status/assignee/priority"), use metrics: ["summary"] with groupBy — this gives exact counts with no issue cap. Use detail metrics (points, time, schedule, cycle, distribution) for per-issue analysis (capped at maxResults). Use flow for status transition patterns — how issues move through statuses, where they bounce, and how long they stay. Tip: save complex JQL as a filter with manage_jira_filter, then reuse the filterId here for repeated analysis. Read jira://analysis/reci…

  • manage_jira_board

    List boards or get board details and configuration

  • manage_jira_filter

    Search for issues using JQL queries, or manage saved filters. Returns issue details (title, status, description). For quantitative questions (counts, totals, overdue, workload), use analyze_jira_issues instead.

  • manage_jira_issue

    Get, create, update, delete, move, transition, comment on, link, log work on, or explore hierarchy of Jira issues. For custom-field writes, consult `jira://capabilities` (field routing) and `jira://custom-fields/{projectKey}/{issueType}` (what is settable here) — some fields need dedicated tools and others auto-resolve names to ids.

  • manage_jira_media

    Manage file attachments on Jira issues (remote). Operations here affect Jira — delete permanently removes an attachment from the issue for all users. Use manage_workspace for local file staging. Downloads copy from Jira to workspace; uploads copy from workspace to Jira.

  • manage_jira_plan

    Navigate and manage the strategic-to-execution hierarchy. Walks issue trees and Atlassian Goals via GraphQL. Read: analyze rollups (dates, points, progress, conflicts), discover goals (list_goals), get goal detail (get_goal). Write: create/update goals, post status updates, link/unlink Jira issues to goals. Results cached server-side. For flat-set metrics use analyze_jira_issues; for structure without rollups use manage_jira_issue hierarchy.

  • manage_jira_project

    List projects or get project configuration and metadata. For issue counts, workload, or cross-project comparison, use analyze_jira_issues with metrics: ["summary"] instead.

  • manage_jira_sprint

    Manage sprints: create, start, close, and assign issues to sprints

  • manage_workspace

    Manage files in the local workspace staging area (local only — no Jira impact). Files downloaded via manage_jira_media land here. Delete only removes the local copy. Use manage_jira_media to affect attachments on Jira issues.

  • queue_jira_operations

    Execute multiple Jira operations in a single call. Operations run sequentially with result references ($0.key) and per-operation error strategies (bail/continue). Powerful for analysis pipelines: create a filter, then run multiple analyze_jira_issues calls against $0.filterId with different groupBy/compute — all in one call.

Signals

Stars
4
Forks
0
Open issues
6
Weekly downloads
94
Last commit
Sep 22, 2026 (1 month ago)
Last release
Sep 22, 2026 (1 month ago)
Last package publish
Sep 22, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.aaronsb/jira-cloud
Version
0.11.3
Auth
API key
License
License unknown
First seen
Oct 24, 2026
Last checked
Oct 25, 2026

More from aaronsb

Cite this page

Jira Cloud MCP server. Agent Mart. https://agentmart.dev/connectors/aaronsb-jira-cloud (last updated 2026-10-25)