{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-jira-mcp-server","slug":"jira-mcp-server","name":"Jira MCP Server","type":"mcp","url":"https://github.com/ahmetbarut/jira-mcp","page_url":"https://unfragile.ai/jira-mcp-server","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-jira-mcp-server__cap_0","uri":"capability://tool.use.integration.jira.board.state.querying.with.mcp.protocol.binding","name":"jira board state querying with mcp protocol binding","description":"Exposes Jira Cloud board data (sprints, columns, swimlanes, board settings) through MCP tool endpoints that serialize board state into structured JSON. Uses Jira REST API v3 under the hood with MCP's request-response pattern to translate tool calls into authenticated API requests, returning board metadata and configuration without polling overhead.","intents":["Fetch current sprint board layout to understand team capacity and workflow state","Query board configuration (columns, issue types, custom fields) for AI agents to understand Jira schema","Retrieve board ID and project context for downstream issue operations"],"best_for":["AI agents and LLM-based automation systems needing real-time Jira state","Teams building custom Jira dashboards or reporting integrations via Claude/LLM","Developers prototyping Jira-aware chatbots or task management bots"],"limitations":["Requires Jira Cloud instance (Server/Data Center not supported by Atlassian REST API v3)","Board query returns only metadata; does not stream real-time updates or webhooks","No built-in caching — each board query hits Jira API, risking rate limits under high-frequency agent calls"],"requires":["Jira Cloud instance with API access enabled","Valid Jira API token (generated from account settings)","MCP client capable of calling tool endpoints (e.g., Claude Desktop, custom MCP host)"],"input_types":["board_id (string identifier)","project_key (string, optional for filtering)"],"output_types":["JSON object with board metadata, columns, sprint info, custom fields"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_1","uri":"capability://search.retrieval.issue.search.and.filtering.with.jql.translation","name":"issue search and filtering with jql translation","description":"Translates natural language or structured filter parameters into Jira Query Language (JQL) and executes searches against Jira Cloud, returning paginated issue results with full issue details (fields, history, transitions). Uses MCP tool endpoints to expose search as a callable function, handling JQL syntax generation and result pagination internally.","intents":["Search for issues matching criteria (assignee, status, priority, labels) without writing JQL manually","Retrieve issues for a specific sprint or board to feed into agent decision-making","Paginate large result sets efficiently for bulk operations or reporting"],"best_for":["Agents needing to filter issues by multiple criteria (status, assignee, date range)","Automation workflows that must find and act on issues matching dynamic conditions","Teams building Jira-aware chatbots that answer 'show me all open bugs assigned to Alice'"],"limitations":["JQL generation is manual or requires caller to provide JQL string; no natural language → JQL parser built-in","Pagination requires explicit offset/limit parameters; no automatic cursor-based iteration","Complex JQL queries (nested conditions, custom field logic) may require caller expertise","Result set limited by Jira API pagination (typically 50-100 issues per request)"],"requires":["Jira Cloud instance with API token","Understanding of JQL syntax or ability to construct filter parameters","MCP client with tool-calling capability"],"input_types":["jql (string, JQL query)","max_results (integer, optional, default 50)","start_at (integer, optional, for pagination)"],"output_types":["JSON array of issue objects with fields: key, summary, status, assignee, priority, created, updated, description, custom fields"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_10","uri":"capability://tool.use.integration.webhook.event.subscription.and.event.streaming.if.supported","name":"webhook event subscription and event streaming (if supported)","description":"unknown — insufficient data. The repository description does not specify whether the MCP server supports webhook subscriptions or event streaming. If implemented, this would likely use Jira Cloud webhooks to stream issue events (created, updated, transitioned) to MCP clients via server-sent events or similar streaming mechanism.","intents":["Subscribe to issue events for real-time agent reactions","Stream issue updates to multiple clients without polling","Trigger automation workflows based on Jira events"],"best_for":["Agents that need real-time visibility into Jira changes","Automation systems that react to issue events","Teams building Jira-aware bots with event-driven architecture"],"limitations":["unknown — insufficient data"],"requires":["unknown — insufficient data"],"input_types":["unknown — insufficient data"],"output_types":["unknown — insufficient data"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_2","uri":"capability://tool.use.integration.issue.creation.with.field.validation.and.custom.field.mapping","name":"issue creation with field validation and custom field mapping","description":"Creates new Jira issues via MCP tool endpoint, accepting issue type, summary, description, and optional custom fields. Validates required fields against Jira project schema before submission, maps caller-provided field names to Jira internal field IDs, and returns the created issue key and URL. Uses Jira REST API v3 issue creation endpoint with pre-flight schema validation.","intents":["Programmatically create issues from agent decisions or external events (e.g., 'create a bug ticket for this error')","Populate custom fields during issue creation without manual field ID lookup","Validate field requirements before submission to avoid API errors"],"best_for":["Automation agents that generate tasks or bugs based on external signals","Integration pipelines converting external events (alerts, form submissions) into Jira issues","Teams building Jira-aware chatbots that can create issues on-demand"],"limitations":["Custom field mapping must be pre-configured; no dynamic field discovery at issue creation time","Bulk issue creation not supported — each issue requires a separate API call","No support for issue linking or epic association at creation time (requires separate update call)","Field validation is schema-based but does not enforce business rules (e.g., 'Story Points must be > 0')"],"requires":["Jira Cloud instance with API token","Project key and issue type ID for the target project","Custom field IDs pre-mapped in MCP server configuration (if using custom fields)","Appropriate Jira permissions (Create Issues)"],"input_types":["project_key (string)","issue_type (string, e.g., 'Bug', 'Task', 'Story')","summary (string, required)","description (string, optional)","assignee (string, optional, username or email)","priority (string, optional)","custom_fields (object, optional, field_name → value mapping)"],"output_types":["JSON object with created issue key, issue ID, and issue URL"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_3","uri":"capability://tool.use.integration.issue.update.and.transition.with.workflow.state.management","name":"issue update and transition with workflow state management","description":"Updates existing Jira issues via MCP tool endpoint, supporting field updates (summary, description, assignee, priority, custom fields) and workflow transitions (status changes). Queries available transitions for the current issue state, validates the requested transition is legal, and applies the transition with optional comment. Uses Jira REST API v3 issue update and transition endpoints.","intents":["Change issue status (e.g., 'move this issue to In Progress') as part of agent workflow","Update issue fields (assignee, priority, custom fields) without full issue replacement","Transition issues through workflow states with validation to prevent illegal state changes"],"best_for":["Agents managing issue lifecycle (creation → in progress → review → done)","Automation workflows that respond to external events by updating issue state","Teams building Jira-aware bots that can reassign or reprioritize issues"],"limitations":["Transition validation requires querying available transitions first; no pre-cached workflow schema","Bulk updates not supported — each issue update is a separate API call","No support for bulk field updates across multiple issues","Workflow transitions are project-specific; no cross-project transition logic"],"requires":["Jira Cloud instance with API token","Issue key (e.g., 'PROJ-123')","Appropriate Jira permissions (Edit Issues, Transition Issues)","Valid transition name or ID for the target workflow state"],"input_types":["issue_key (string)","fields (object, optional, field updates)","transition (string, optional, transition name or ID)","comment (string, optional, comment to add during transition)"],"output_types":["JSON object confirming update success, updated issue state, or error details"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_4","uri":"capability://search.retrieval.user.and.team.member.querying.with.permission.context","name":"user and team member querying with permission context","description":"Queries Jira Cloud user directory via MCP tool endpoint, returning user details (name, email, avatar, active status) and optionally filtering by project or board membership. Uses Jira REST API v3 user search endpoint with optional permission filters to identify assignable users for a given project. Caches user list in memory to reduce API calls for repeated queries.","intents":["Retrieve list of assignable users for a project to populate agent decision-making","Look up user details (email, avatar) for display or notification purposes","Find users with specific permissions (e.g., 'who can create issues in this project')"],"best_for":["Agents that need to assign issues to team members and require user list for validation","Automation workflows that notify users and need email addresses or user IDs","Teams building Jira-aware chatbots that can answer 'who is assigned to this issue'"],"limitations":["User list is cached in memory; changes to user permissions or team membership may not reflect immediately","No built-in filtering by team or group; requires caller to filter results","Permission context is project-specific; no cross-project user queries","User search is limited to active users by default; deactivated users not returned"],"requires":["Jira Cloud instance with API token","Project key (optional, for permission-scoped queries)","Appropriate Jira permissions (Browse Users)"],"input_types":["project_key (string, optional)","query (string, optional, search by name or email)"],"output_types":["JSON array of user objects with fields: account_id, display_name, email, avatar_url, active"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_5","uri":"capability://tool.use.integration.comment.creation.and.retrieval.with.thread.context","name":"comment creation and retrieval with thread context","description":"Creates comments on Jira issues and retrieves existing comments via MCP tool endpoints. Comment creation supports plain text and optional Jira markup formatting. Comment retrieval returns paginated comment history with author, timestamp, and edit history. Uses Jira REST API v3 comment endpoints with optional visibility restrictions (public vs. restricted to specific groups).","intents":["Add agent-generated comments to issues for audit trails or status updates","Retrieve issue comment history to provide context for agent decision-making","Create restricted comments visible only to specific groups (e.g., 'internal notes')"],"best_for":["Agents that need to document decisions or status changes via issue comments","Automation workflows that add comments as part of issue lifecycle management","Teams building Jira-aware bots that can read and respond to issue discussions"],"limitations":["Comment formatting is limited to Jira markup; no HTML or rich text support","Bulk comment operations not supported — each comment requires separate API call","Comment visibility restrictions are group-based; no fine-grained user-level restrictions","Comment editing is not supported; only creation and retrieval"],"requires":["Jira Cloud instance with API token","Issue key for comment operations","Appropriate Jira permissions (Add Comments, View Comments)"],"input_types":["issue_key (string)","body (string, comment text in Jira markup)","visibility (object, optional, restrict to group or role)"],"output_types":["JSON object with comment ID, author, timestamp, body, or JSON array of comments for retrieval"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_6","uri":"capability://tool.use.integration.sprint.management.and.issue.assignment.to.sprints","name":"sprint management and issue assignment to sprints","description":"Queries active and future sprints for a board, and assigns or moves issues between sprints via MCP tool endpoints. Sprint queries return sprint metadata (name, state, start/end dates, goal). Issue assignment uses Jira REST API v3 sprint endpoints to move issues atomically. Supports bulk sprint operations (move multiple issues to sprint in single call if Jira API supports it).","intents":["Retrieve active sprint to understand current team capacity and planned work","Assign newly created issues to the current or upcoming sprint","Move issues between sprints as part of backlog grooming or re-prioritization workflows"],"best_for":["Agents managing sprint planning and backlog refinement","Automation workflows that assign issues to sprints based on priority or team capacity","Teams building Jira-aware bots that can answer 'what's in the current sprint'"],"limitations":["Sprint queries are board-specific; no cross-board sprint visibility","Bulk sprint assignment may require multiple API calls depending on Jira API limits","No support for sprint creation or deletion via MCP (read-only for sprint metadata)","Sprint state transitions (start, close) not supported; only issue assignment"],"requires":["Jira Cloud instance with API token","Board ID for sprint queries","Appropriate Jira permissions (Edit Sprint, Manage Sprints)"],"input_types":["board_id (string)","issue_key (string)","sprint_id (integer)"],"output_types":["JSON array of sprint objects with fields: id, name, state, start_date, end_date, goal, or confirmation of issue assignment"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_7","uri":"capability://tool.use.integration.issue.attachment.upload.and.metadata.retrieval","name":"issue attachment upload and metadata retrieval","description":"Uploads files as attachments to Jira issues and retrieves attachment metadata (filename, size, author, timestamp, download URL) via MCP tool endpoints. Supports common file types (images, documents, logs) with size validation. Uses Jira REST API v3 attachment endpoints with multipart form data for uploads. Attachment metadata includes direct download URLs for agent access.","intents":["Attach generated reports, logs, or screenshots to issues for documentation","Retrieve attachment metadata to understand issue artifacts without downloading","Link external files (error logs, performance traces) to issues for context"],"best_for":["Agents that generate reports or logs and need to attach them to issues","Automation workflows that collect and archive issue artifacts","Teams building Jira-aware bots that can retrieve and display issue attachments"],"limitations":["File size limits enforced by Jira (typically 20MB per file)","No support for bulk attachment operations — each file requires separate upload","Attachment deletion not supported; only upload and metadata retrieval","Download URLs are temporary and may expire; no permanent file storage"],"requires":["Jira Cloud instance with API token","Issue key for attachment operations","File content (binary or text) for upload","Appropriate Jira permissions (Add Attachments)"],"input_types":["issue_key (string)","file (binary or base64-encoded string)","filename (string)"],"output_types":["JSON object with attachment ID, filename, size, author, created timestamp, download URL, or JSON array of attachment metadata"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_8","uri":"capability://tool.use.integration.issue.link.creation.and.dependency.tracking","name":"issue link creation and dependency tracking","description":"Creates links between Jira issues (e.g., 'blocks', 'relates to', 'duplicates') via MCP tool endpoint, enabling agents to model issue dependencies and relationships. Queries available link types for a project and validates link creation before submission. Uses Jira REST API v3 issue link endpoints. Supports bidirectional link creation (A blocks B automatically creates B is blocked by A).","intents":["Create dependency links between issues to model blocking relationships","Link duplicate issues to consolidate related work","Create 'relates to' links for cross-cutting concerns or shared context"],"best_for":["Agents managing complex project dependencies and critical path analysis","Automation workflows that detect and link related issues","Teams building Jira-aware bots that can answer 'what issues are blocked by this one'"],"limitations":["Link types are project-specific; no cross-project link type discovery","Bulk link creation not supported — each link requires separate API call","Link deletion not supported; only creation and querying","Circular dependency detection is not built-in; caller must validate"],"requires":["Jira Cloud instance with API token","Source and target issue keys","Valid link type name (e.g., 'blocks', 'relates to')","Appropriate Jira permissions (Link Issues)"],"input_types":["source_issue_key (string)","target_issue_key (string)","link_type (string, e.g., 'blocks', 'relates to', 'duplicates')"],"output_types":["JSON object confirming link creation with link ID and direction, or error details"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jira-mcp-server__cap_9","uri":"capability://search.retrieval.project.and.board.discovery.with.schema.introspection","name":"project and board discovery with schema introspection","description":"Queries available Jira projects and boards accessible to the authenticated user via MCP tool endpoints, returning project metadata (key, name, type, category) and board configuration (columns, swimlanes, issue types). Introspects project schema to discover custom fields, issue types, and available transitions. Uses Jira REST API v3 project and board endpoints with caching for schema data.","intents":["Discover available projects and boards to initialize agent context","Introspect project schema (issue types, custom fields) for dynamic tool generation","Validate project key and board ID before attempting operations"],"best_for":["Agents that need to discover Jira configuration dynamically at runtime","Automation systems that must adapt to different project schemas","Teams building Jira-aware bots that support multiple projects without hardcoding"],"limitations":["Schema introspection is cached in memory; changes to project configuration may not reflect immediately","Custom field discovery is limited to fields visible to the authenticated user","No support for project creation or deletion via MCP (read-only discovery)","Board discovery is limited to boards the user has access to"],"requires":["Jira Cloud instance with API token","Appropriate Jira permissions (Browse Projects, View Boards)"],"input_types":["project_key (string, optional, for specific project introspection)"],"output_types":["JSON array of project objects with fields: key, name, type, category, or JSON object with project schema (issue types, custom fields, transitions)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":31,"verified":false,"data_access_risk":"high","permissions":["Jira Cloud instance with API access enabled","Valid Jira API token (generated from account settings)","MCP client capable of calling tool endpoints (e.g., Claude Desktop, custom MCP host)","Jira Cloud instance with API token","Understanding of JQL syntax or ability to construct filter parameters","MCP client with tool-calling capability","unknown — insufficient data","Project key and issue type ID for the target project","Custom field IDs pre-mapped in MCP server configuration (if using custom fields)","Appropriate Jira permissions (Create Issues)"],"failure_modes":["Requires Jira Cloud instance (Server/Data Center not supported by Atlassian REST API v3)","Board query returns only metadata; does not stream real-time updates or webhooks","No built-in caching — each board query hits Jira API, risking rate limits under high-frequency agent calls","JQL generation is manual or requires caller to provide JQL string; no natural language → JQL parser built-in","Pagination requires explicit offset/limit parameters; no automatic cursor-based iteration","Complex JQL queries (nested conditions, custom field logic) may require caller expertise","Result set limited by Jira API pagination (typically 50-100 issues per request)","unknown — insufficient data","Custom field mapping must be pre-configured; no dynamic field discovery at issue creation time","Bulk issue creation not supported — each issue requires a separate API call","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.47,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"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-06-17T09:51:03.577Z","last_scraped_at":"2026-05-03T14:00:15.503Z","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=jira-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=jira-mcp-server"}},"signature":"vIoSgo0hTy1Q1XUNDLiXIhAh+fBX8L2K6+kLgswxQ9/WBuTha5QzWIDnPeiHADWfYhpgjsfbKknDht9P8mfTDw==","signedAt":"2026-06-21T07:20:43.394Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/jira-mcp-server","artifact":"https://unfragile.ai/jira-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=jira-mcp-server","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"}}