{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_anderson-0-jira-cloud-mcp","slug":"anderson-0-jira-cloud-mcp","name":"jira-cloud-mcp","type":"mcp","url":"https://smithery.ai/servers/anderson-0/jira-cloud-mcp","page_url":"https://unfragile.ai/anderson-0-jira-cloud-mcp","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:anderson-0/jira-cloud-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_anderson-0-jira-cloud-mcp__cap_0","uri":"capability://tool.use.integration.jira.issue.crud.operations.via.mcp.protocol","name":"jira issue crud operations via mcp protocol","description":"Enables LLM agents and tools to create, read, update, and delete Jira issues through the Model Context Protocol, translating MCP tool calls into Jira Cloud REST API requests with automatic authentication via OAuth2 or API tokens. Implements request/response marshaling to convert between MCP's JSON-RPC 2.0 format and Jira's REST endpoint schemas, handling field mapping and validation.","intents":["I want my AI agent to create Jira tickets from natural language descriptions without manual formatting","I need to fetch issue details and metadata programmatically to feed into downstream LLM reasoning","I want to update issue status, assignee, or custom fields based on AI decisions","I need to delete or archive issues through an AI workflow without touching the Jira UI"],"best_for":["AI teams building autonomous issue management agents","DevOps engineers automating incident response workflows with LLMs","Product teams integrating Jira with multi-step AI reasoning pipelines"],"limitations":["Limited to Jira Cloud API capabilities — on-premise Jira Server not supported","Bulk operations require sequential API calls (no batch endpoint), adding latency for >10 issues","Custom field handling depends on Jira instance schema — requires pre-mapping of field IDs","No built-in retry logic for rate-limited requests (429 responses)"],"requires":["Jira Cloud instance with API access enabled","OAuth2 credentials or API token with issue management scopes","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Network access to api.atlassian.com"],"input_types":["JSON (MCP tool call parameters)","text (issue summary, description, comments)","structured data (field mappings, custom field values)"],"output_types":["JSON (issue objects with full metadata)","text (issue keys, summaries, status)","structured data (field values, timestamps, user references)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_1","uri":"capability://tool.use.integration.jira.project.and.board.discovery.via.mcp.resources","name":"jira project and board discovery via mcp resources","description":"Exposes Jira projects, boards, and issue hierarchies as MCP resources that LLM agents can query and traverse, implementing a resource-based discovery pattern where each project/board is addressable via a URI and returns structured metadata including board type (Scrum/Kanban), issue types, and custom fields. Uses Jira's REST API to enumerate and cache project/board listings.","intents":["I want my agent to understand the structure of my Jira workspace before creating or updating issues","I need to list all available projects and boards so the agent can route issues to the correct destination","I want to discover custom fields and issue types supported by a specific project","I need to fetch board configuration (columns, swimlanes) to map AI decisions to valid workflow states"],"best_for":["Multi-project organizations where agents need context-aware issue routing","Teams with complex Jira hierarchies (multiple boards per project, custom workflows)","AI systems that need to validate user input against available Jira structures"],"limitations":["Resource discovery is read-only — cannot modify project settings or board configuration through MCP","Caching strategy not specified — may return stale data if projects are modified outside the agent","No pagination support documented — may fail on instances with >100 projects","Custom field discovery depends on Jira instance permissions — some fields may be hidden from API token"],"requires":["Jira Cloud instance with at least read access to projects","API token or OAuth2 credentials with project read scope","MCP client with resource discovery support"],"input_types":["text (project key or board ID for filtering)","JSON (query parameters for filtering)"],"output_types":["JSON (project metadata, board configurations)","structured data (issue type schemas, field definitions)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_2","uri":"capability://search.retrieval.jira.search.and.filtering.via.jql.translation","name":"jira search and filtering via jql translation","description":"Translates natural language or structured filter parameters into Jira Query Language (JQL) and executes searches against the Jira Cloud API, returning paginated issue lists with full metadata. Implements a query builder pattern that maps common filter dimensions (assignee, status, project, date range) to JQL syntax and handles special characters/escaping.","intents":["I want my agent to find all open issues assigned to a specific person without writing JQL manually","I need to search for issues matching complex criteria (e.g., 'high priority bugs created in the last week')","I want to retrieve issues for a specific project or epic to feed into an AI analysis pipeline","I need to paginate through large result sets efficiently without loading all issues into memory"],"best_for":["AI agents that need to query Jira as part of decision-making workflows","Teams building issue analytics or reporting systems on top of Jira","Automation systems that need to find and act on issues matching dynamic criteria"],"limitations":["JQL translation is limited to common filters — complex custom JQL expressions may not be supported","Search results are limited to 50 issues per page by default; pagination requires multiple API calls","Full-text search performance depends on Jira instance indexing — may be slow on large instances","No support for saved filters or filter sharing — each search is stateless"],"requires":["Jira Cloud instance with search API enabled","API token or OAuth2 credentials with issue search scope","Understanding of Jira issue fields and statuses in the target instance"],"input_types":["text (natural language filter description)","JSON (structured filter parameters: assignee, status, project, date range, priority)","JQL (raw Jira Query Language for advanced searches)"],"output_types":["JSON (paginated issue list with full metadata)","text (issue summaries and keys)","structured data (field values, timestamps)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_3","uri":"capability://memory.knowledge.jira.issue.comment.and.activity.tracking","name":"jira issue comment and activity tracking","description":"Enables agents to read issue comments, activity history, and changelog entries through MCP tool calls, returning chronologically ordered comment threads with author metadata, timestamps, and edit history. Implements pagination for issues with many comments and supports filtering by date range or author.","intents":["I want my agent to read the full comment thread on an issue to understand context and decision history","I need to track who made changes to an issue and when, for audit or analysis purposes","I want to add comments to issues programmatically to document AI decisions or findings","I need to extract mentions or references from comments to link related issues or stakeholders"],"best_for":["AI systems that need to understand issue context before making decisions","Audit and compliance workflows that track issue modifications","Collaborative agents that document their reasoning in issue comments"],"limitations":["Comment editing history is limited — only current version and edit timestamp are returned","Attachment metadata is returned but file content is not accessible through MCP","Mentions and links in comments are not parsed — agents must extract them from raw text","Comment permissions are enforced by Jira — some comments may be hidden if token lacks access"],"requires":["Jira Cloud instance with comment API enabled","API token or OAuth2 credentials with issue read scope","Issue key or ID to fetch comments for"],"input_types":["text (issue key or ID)","JSON (pagination parameters, date range filters)"],"output_types":["JSON (comment objects with author, timestamp, body)","text (comment text content)","structured data (activity timeline, changelog entries)"],"categories":["memory-knowledge","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_4","uri":"capability://tool.use.integration.jira.user.and.team.resolution","name":"jira user and team resolution","description":"Resolves user mentions, team names, and assignee references to Jira user objects with full metadata (email, avatar, timezone, account ID), enabling agents to map natural language names to valid Jira user IDs for assignment operations. Implements a search-based resolution pattern that queries Jira's user directory and caches results.","intents":["I want my agent to assign issues to team members using their names instead of account IDs","I need to find the correct user ID for a person mentioned in natural language","I want to validate that a user exists in Jira before attempting to assign them an issue","I need to list team members for a project to enable intelligent issue routing"],"best_for":["Multi-user teams where agents need to map names to Jira accounts","Automation systems that parse user mentions from external sources (email, Slack, etc.)","AI agents that need to validate user existence before performing operations"],"limitations":["User search is limited by Jira's directory — external users or deactivated accounts may not be discoverable","Name matching is fuzzy and may return multiple candidates — agents must disambiguate","User metadata visibility depends on Jira permissions — some fields may be redacted","No group/team enumeration — only individual user lookup is supported"],"requires":["Jira Cloud instance with user directory enabled","API token or OAuth2 credentials with user read scope","User name or email to search for"],"input_types":["text (user name, email, or display name)","JSON (search parameters)"],"output_types":["JSON (user objects with account ID, email, avatar URL)","text (user names and emails)","structured data (user metadata)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_5","uri":"capability://automation.workflow.jira.workflow.state.transitions.with.validation","name":"jira workflow state transitions with validation","description":"Validates and executes issue status transitions through Jira's workflow engine, checking allowed transitions for the current issue state and enforcing required field values before moving to the next state. Implements a state machine pattern that queries Jira's workflow metadata to determine valid next states and required fields.","intents":["I want my agent to move issues through the workflow (e.g., 'In Progress' → 'Done') with automatic validation","I need to check what transitions are available for an issue before attempting to move it","I want to ensure required fields are populated before transitioning to a state that requires them","I need to handle workflow errors gracefully when a transition is not allowed"],"best_for":["Automation systems that need to respect Jira workflow rules","AI agents that manage issue lifecycle without manual intervention","Teams with complex workflows that require field validation before state changes"],"limitations":["Workflow validation is instance-specific — transitions vary by project and workflow","Required field detection depends on workflow configuration — may not catch all validation errors","Transition screens (custom fields required for specific transitions) are not fully exposed","No support for conditional workflows or approval gates — only standard state transitions"],"requires":["Jira Cloud instance with workflow engine enabled","API token or OAuth2 credentials with issue edit scope","Issue key and target transition name"],"input_types":["text (issue key, transition name)","JSON (field values required for transition)"],"output_types":["JSON (updated issue object, available transitions)","text (transition status, error messages)","structured data (required fields, validation errors)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_6","uri":"capability://data.processing.analysis.jira.custom.field.handling.and.schema.mapping","name":"jira custom field handling and schema mapping","description":"Discovers, validates, and maps custom fields defined in a Jira instance, translating between field names and field IDs and enforcing field type constraints (select lists, date fields, number fields, etc.). Implements a schema registry pattern that caches field definitions and provides type-aware field validation.","intents":["I want my agent to populate custom fields when creating or updating issues without knowing field IDs","I need to validate that a field value matches the expected type before sending it to Jira","I want to discover available options for select-list custom fields to enable intelligent field population","I need to handle custom field visibility rules (some fields only appear in certain projects)"],"best_for":["Organizations with complex custom field configurations","AI systems that need to create or update issues with custom fields","Teams that want agents to understand and respect field constraints"],"limitations":["Custom field discovery is project-specific — field availability varies by project","Field type validation is basic — complex field types (cascading selects, linked issues) may not be fully supported","Field options for select lists are not cached — each query requires an API call","No support for field-level permissions — agents cannot determine if they can edit a field"],"requires":["Jira Cloud instance with custom fields enabled","API token or OAuth2 credentials with field read scope","Project key to discover fields for"],"input_types":["text (field name or ID)","JSON (field value with type information)"],"output_types":["JSON (field schema with type, options, constraints)","text (field names and descriptions)","structured data (field type definitions, validation rules)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_7","uri":"capability://tool.use.integration.jira.issue.linking.and.dependency.tracking","name":"jira issue linking and dependency tracking","description":"Creates, reads, and manages issue links (relates to, blocks, duplicates, etc.) through MCP tool calls, enabling agents to establish relationships between issues and traverse dependency graphs. Implements link creation with validation of link types and bidirectional link management.","intents":["I want my agent to link related issues together to establish dependencies or relationships","I need to find all issues that block or depend on a specific issue","I want to detect and prevent duplicate issues by linking them","I need to traverse the dependency graph to understand issue impact and scope"],"best_for":["AI systems managing complex projects with many interdependent issues","Automation workflows that need to establish issue relationships","Teams that want agents to understand and respect issue dependencies"],"limitations":["Link types are instance-specific — available link types vary by Jira configuration","Circular dependency detection is not built-in — agents must implement their own cycle detection","Link traversal is not optimized for large graphs — deep dependency chains may require many API calls","No bulk link operations — each link must be created individually"],"requires":["Jira Cloud instance with issue linking enabled","API token or OAuth2 credentials with issue edit scope","Source and target issue keys"],"input_types":["text (issue key, link type)","JSON (link metadata)"],"output_types":["JSON (link objects with type and target issue)","text (issue keys and link types)","structured data (dependency graph)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_anderson-0-jira-cloud-mcp__cap_8","uri":"capability://automation.workflow.jira.sprint.and.release.planning.integration","name":"jira sprint and release planning integration","description":"Integrates with Jira's sprint and release management features, enabling agents to query sprint status, move issues between sprints, and track release progress. Implements sprint-aware issue operations that respect sprint boundaries and active sprint constraints.","intents":["I want my agent to understand which sprint an issue belongs to and move it between sprints","I need to query sprint status and progress to feed into AI-driven planning decisions","I want to automatically move issues to the next sprint based on priority or status","I need to track release progress and identify at-risk issues"],"best_for":["Agile teams using Scrum with automated sprint management","AI systems that need to understand sprint context for issue prioritization","Release managers that want agents to track and report on release progress"],"limitations":["Sprint operations are only available for Scrum boards — Kanban boards have no sprint concept","Active sprint constraints may prevent moving issues — agents must handle sprint closure rules","Sprint capacity and velocity data are not exposed — agents cannot predict sprint feasibility","Release planning is limited to issue-level tracking — no support for release-level planning features"],"requires":["Jira Cloud instance with Scrum board enabled","API token or OAuth2 credentials with sprint edit scope","Board ID and sprint ID"],"input_types":["text (issue key, sprint name)","JSON (sprint parameters)"],"output_types":["JSON (sprint metadata, issue list, progress metrics)","text (sprint status, issue counts)","structured data (sprint velocity, burndown data)"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["Jira Cloud instance with API access enabled","OAuth2 credentials or API token with issue management scopes","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Network access to api.atlassian.com","Jira Cloud instance with at least read access to projects","API token or OAuth2 credentials with project read scope","MCP client with resource discovery support","Jira Cloud instance with search API enabled","API token or OAuth2 credentials with issue search scope","Understanding of Jira issue fields and statuses in the target instance"],"failure_modes":["Limited to Jira Cloud API capabilities — on-premise Jira Server not supported","Bulk operations require sequential API calls (no batch endpoint), adding latency for >10 issues","Custom field handling depends on Jira instance schema — requires pre-mapping of field IDs","No built-in retry logic for rate-limited requests (429 responses)","Resource discovery is read-only — cannot modify project settings or board configuration through MCP","Caching strategy not specified — may return stale data if projects are modified outside the agent","No pagination support documented — may fail on instances with >100 projects","Custom field discovery depends on Jira instance permissions — some fields may be hidden from API token","JQL translation is limited to common filters — complex custom JQL expressions may not be supported","Search results are limited to 50 issues per page by default; pagination requires multiple API calls","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.28,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.635Z","last_scraped_at":"2026-05-03T15:19:09.932Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=anderson-0-jira-cloud-mcp","compare_url":"https://unfragile.ai/compare?artifact=anderson-0-jira-cloud-mcp"}},"signature":"T7sSf/2nJZ3xQDpQ1BzrvmMW/u1xX3H4qem83sO+WO4cV6wLqCjR7+SfeFlkd6mzWLnAhbl+O1W0XzHeARJOBA==","signedAt":"2026-06-21T22:27:57.525Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/anderson-0-jira-cloud-mcp","artifact":"https://unfragile.ai/anderson-0-jira-cloud-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=anderson-0-jira-cloud-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}