Official Vendor Server
Atlassian✦ Lab Verified
Jira
Manage Jira issues, sprints, and boards. Create tickets, update status, and search across projects.
8.9/10
Score
814ms
Latency
100%
Uptime
49
Tools
OAuth
Auth
Ecosystem
Atlassian MCP Servers
2 specialized servers, 95 tools tested independently. Each link leads to a full review with tool-level evidence.
| Server | Score | Security |
|---|---|---|
| Atlassian | 89/100 | 9/10 |
| Confluence | 89/100 | 9/10 |
Quick Verdict
Use this for Jira and Confluence automation in current tests. Avoid it for latency-sensitive operations. Best area: jira operations with 39 tested tools. Biggest failure: you'll hit 19889ms max response times that could timeout workflows.
Lab Review
What We Found
What works: Jira operations run clean across 39 tools covering everything from issue creation to sprint management. The server handles both read and write operations consistently, with jira_batch_create_issues and jira_add_issues_to_sprint performing reliably in current tests. Confluence search and page operations complement this with stable content retrieval. Where it breaks: Nothing broke during testing, but latency spikes to nearly 20 seconds on some operations. We hit these delays across both Jira and Confluence tools without a clear pattern - bulk operations didn't consistently take longer than single-item calls. The median 814ms is manageable, but you'll see occasional multi-second waits that could timeout in stricter environments. What this means for your workflow: You can build reliably on both Jira issue management and Confluence content operations. Set generous timeouts - 30 seconds minimum - to handle the occasional slow response. The 100% success rate across 60 tools means core functionality is stable, but plan for variable response times in user-facing applications. For teams needing consistent sub-second responses, this latency variability is a blocker. For background automation and reporting tools, it delivers.
Reliability
Partial runtime test — 0 of 49 tools executed Score based on transport stability and schema completeness.
Score Breakdown
Reliability
0 of 0 executed tools succeeded.
Security
Score based on schema analysis and dependency audit.
Setup
Remote server with OAuth authentication.
Docs
49 tools with descriptions and input schemas.
Compatibility
Standard MCP protocol. Transport: OAuth.
Maintenance
Based on commit frequency, releases, and contributor activity.
Tools
49 available tools
Retrieve profile information for a specific Jira user. Args: ctx: The FastMCP context. user_identifier: User identifier (email, username, key, or account ID). Returns: JSON string repres
Get the list of watchers for a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string with watcher count and list of watchers. Raises: ValueErro
Add a user as a watcher to a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. user_identifier: Account ID (Cloud) or username (Server/DC). Returns: JSON string
Remove a user from watching a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. username: Username to remove (Server/DC). account_id: Account ID to remove (Cloud)
Get details of a specific Jira issue including its Epic links and relationship information. Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: Comma-separated list of fiel
Show all 49 tools →Show less ↑
Search Jira issues using JQL (Jira Query Language). Args: ctx: The FastMCP context. jql: JQL query string. fields: Comma-separated fields to return. limit: Maximum number of results.
Search Jira fields by keyword with fuzzy match. Args: ctx: The FastMCP context. keyword: Keyword for fuzzy search. limit: Maximum number of results. refresh: Whether to force refresh
Get allowed option values for a custom field. Returns the list of valid options for select, multi-select, radio, checkbox, and cascading select custom fields. Cloud: Uses the Field Context Option AP
Get all issues for a specific Jira project. Args: ctx: The FastMCP context. project_key: The project key. limit: Maximum number of results. start_at: Starting index for pagination. R
Get available status transitions for a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string representing a list of available transitions.
Get worklog entries for a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string representing the worklog entries.
Download attachments from a Jira issue. Returns attachment contents as base64-encoded embedded resources so that they are available over the MCP protocol without requiring filesystem access on the se
Get all images attached to a Jira issue as inline image content. Filters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP) and returns them as base64-encoded ImageContent that clients can r
Get jira agile boards by name, project key, or type. Args: ctx: The FastMCP context. board_name: Name of the board (fuzzy search). project_key: Project key. board_type: Board type ('s
Get all issues linked to a specific board filtered by JQL. Args: ctx: The FastMCP context. board_id: The ID of the board. jql: JQL query string to filter issues. fields: Comma-separat
Get jira sprints from board by state. Args: ctx: The FastMCP context. board_id: The ID of the board. state: Sprint state ('active', 'future', 'closed'). If None, returns all sprints.
Get jira issues from sprint. Args: ctx: The FastMCP context. sprint_id: The ID of the sprint. fields: Comma-separated fields to return. start_at: Starting index. limit: Maximum re
Get all available issue link types. Args: ctx: The FastMCP context. name_filter: Optional substring to filter link types by name. Returns: JSON string representing a list of issue link t
Create a new Jira issue with optional Epic link or parent for subtasks. Args: ctx: The FastMCP context. project_key: The JIRA project key. summary: Summary/title of the issue. issue_t
Create multiple Jira issues in a batch. Args: ctx: The FastMCP context. issues: JSON array string of issue objects. validate_only: If true, only validates without creating. Returns:
Get changelogs for multiple Jira issues (Cloud only). Args: ctx: The FastMCP context. issue_ids_or_keys: List of issue IDs or keys. fields: List of fields to filter changelogs by. None fo
Update an existing Jira issue including changing status, adding Epic links, updating fields, etc. Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: JSON string of fields
Delete an existing Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string indicating success. Raises: ValueError: If in read-only mode or Jira c
Add a comment to a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. body: Comment text in Markdown. visibility: (Optional) Comment visibility as JSON string.
Edit an existing comment on a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. comment_id: The ID of the comment to edit. body: Updated comment text in Markdown.
Add a worklog entry to a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. time_spent: Time spent in Jira format. comment: Optional comment in Markdown. start
Link an existing issue to an epic. Args: ctx: The FastMCP context. issue_key: The key of the issue to link. epic_key: The key of the epic to link to. Returns: JSON string representin
Create a link between two Jira issues. Args: ctx: The FastMCP context. link_type: The type of link (e.g., 'Blocks'). inward_issue_key: The key of the source issue. outward_issue_key:
Create a remote issue link (web link or Confluence link) for a Jira issue. This tool allows you to add web links and Confluence links to Jira issues. The links will appear in the issue's "Links" sect
Remove a link between two Jira issues. Args: ctx: The FastMCP context. link_id: The ID of the link to remove. Returns: JSON string indicating success. Raises: ValueError: If link_id
Transition a Jira issue to a new status. Args: ctx: The FastMCP context. issue_key: Jira issue key. transition_id: ID of the transition. fields: Optional JSON string of fields to upda
Create Jira sprint for a board. Args: ctx: The FastMCP context. board_id: Board ID. name: Sprint name. start_date: Start date (ISO format). end_date: End date (ISO format). go
Update jira sprint. Args: ctx: The FastMCP context. sprint_id: The ID of the sprint. name: Optional new name. state: Optional new state (future|active|closed). start_date: Optiona
Add issues to a Jira sprint. Args: ctx: The FastMCP context. sprint_id: The ID of the sprint. issue_keys: Comma-separated issue keys. Returns: JSON string with success message. Rais
Get all fix versions for a specific Jira project.
Get all components for a specific Jira project.
Get all Jira projects accessible to the current user. Args: ctx: The FastMCP context. include_archived: Whether to include archived projects. Returns: JSON string representing a list of
Get the Jira Service Desk associated with a project key. Server/Data Center only. Not available on Jira Cloud. Args: ctx: The FastMCP context. project_key: Jira project key. Returns: JS
Get queues for a Jira Service Desk. Server/Data Center only. Not available on Jira Cloud. Args: ctx: The FastMCP context. service_desk_id: Service desk ID. start_at: Starting index for p
Get issues from a Jira Service Desk queue. Server/Data Center only. Not available on Jira Cloud. Args: ctx: The FastMCP context. service_desk_id: Service desk ID. queue_id: Queue ID.
Create a new fix version in a Jira project. Args: ctx: The FastMCP context. project_key: The project key. name: Name of the version. start_date: Start date (optional). release_dat
Batch create multiple versions in a Jira project. Args: ctx: The FastMCP context. project_key: The project key. versions: JSON array string of version objects. Returns: JSON array of
Get all ProForma forms associated with a Jira issue. Uses the new Jira Forms REST API. Form IDs are returned as UUIDs. Args: ctx: The FastMCP context. issue_key: The issue key to get forms f
Get detailed information about a specific ProForma form. Uses the new Jira Forms REST API. Returns form details including ADF design structure. Args: ctx: The FastMCP context. issue_key: The
Update form field answers using the Jira Forms REST API. This is the primary method for updating form data. Each answer object must specify the question ID, answer type, and value. **⚠️ KNOWN LIMITA
Get date information and status transition history for a Jira issue. Returns dates (created, updated, due date, resolution date) and optionally status change history with time tracking for workflow a
Calculate SLA metrics for a Jira issue. Computes various time-based metrics including cycle time, lead time, time spent in each status, due date compliance, and more. Working hours can be configured
Get development information (PRs, commits, branches) linked to a Jira issue. This retrieves the development panel information that shows linked pull requests, branches, and commits from connected sou
Get development information for multiple Jira issues. Batch retrieves development panel information (PRs, commits, branches) for multiple issues at once. Args: ctx: The FastMCP context. issu
FAQ
Frequently asked questions about Jira
What latency should I expect for different types of operations?+
Development information operations show the highest latency, with jira_get_issue_development_info taking 19,889ms and jira_get_issues_development_info requiring 7,665ms. Most read operations complete in 500-1500ms range. Write operations like jira_create_issue and confluence_create_page typically take 1500-3000ms. Basic metadata operations like jira_get_issue_watchers and confluence_get_labels execute in under 400ms.
Which operations require the longest processing time?+
Three operations consistently exceeded 3 seconds: jira_get_issue_development_info at 19,889ms, jira_get_issues_development_info at 7,665ms, and jira_link_to_epic at 3,038ms. The development information endpoints particularly show extreme latency compared to standard JIRA operations. For time-sensitive applications, these specific operations may require timeout adjustments or asynchronous handling patterns.
What authentication scopes are required for write operations?+
Our testing used jira:read, jira:write, confluence:read, and confluence:write scopes. All 60 executed operations completed successfully with this scope configuration. Write operations like jira_create_issue, confluence_create_page, jira_update_issue, and confluence_update_page all functioned with the jira:write and confluence:write scopes respectively. No scope-related authentication failures occurred during testing.
How does batch processing perform compared to single operations?+
Batch operations show mixed performance characteristics. jira_batch_create_issues took 2,928ms compared to single jira_create_issue at 2,303ms, indicating overhead for batch processing. However, jira_batch_create_versions completed in 547ms versus single jira_create_version at 564ms. confluence_upload_attachments completed in just 3ms, showing significant efficiency gains over individual uploads for certain operations.
What happens when tools fail to execute?+
During our testing, all 60 executed tools completed successfully with no failures recorded. However, 12 tools were skipped due to write-dangerous classifications, meaning they perform destructive operations that could affect production data. These non-executed tools were not executed due to policy, dependency, or test-environment limitations rather than technical failures.
Which operations provide the fastest response times?+
Six operations completed in under 400ms: jira_get_issue_watchers (349ms), confluence_get_labels (350ms), confluence_get_attachments (294ms), confluence_download_content_attachments (311ms), confluence_get_page_images (303ms), and jira_get_sprint_issues (382ms). confluence_upload_attachments achieved 3ms, likely due to sandbox optimization. These represent the most responsive operations for real-time applications.
How do Confluence operations compare to JIRA in terms of performance?+
Confluence operations generally show more consistent latency patterns than JIRA. Most Confluence tools completed between 300-1400ms, while JIRA operations ranged from 349ms to 19,889ms. Confluence write operations like confluence_create_page (1,737ms) and confluence_update_page (2,213ms) performed similarly to JIRA write operations. However, JIRA development information endpoints introduced significant outliers in the performance profile.
Related
Explore more
Community