Skip to main content
Glama

MCP Atlassian

PyPI Version PyPI - Downloads PePy - Total Downloads Run Tests License Docs

Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.

https://github.com/user-attachments/assets/35303504-14c6-4ae4-913b-7c25ea511c3e

https://github.com/user-attachments/assets/7fe9c488-ad0c-4876-9b54-120b666bb785

Quick Start

1. Get Your API Token

Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a token.

For Server/Data Center, use a Personal Access Token instead. See Authentication.

2. Configure Your IDE

Add to your Claude Desktop or Cursor MCP configuration:

{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "JIRA_URL": "https://your-company.atlassian.net",
        "JIRA_USERNAME": "your.email@company.com",
        "JIRA_API_TOKEN": "your_api_token",
        "CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "your.email@company.com",
        "CONFLUENCE_API_TOKEN": "your_api_token"
      }
    }
  }
}

Server/Data Center users: Use JIRA_PERSONAL_TOKEN (or JIRA_USERNAME + JIRA_PASSWORD), and CONFLUENCE_PERSONAL_TOKEN (or CONFLUENCE_USERNAME + CONFLUENCE_PASSWORD). See Authentication for details.

Autohand Code

Use the same uvx server with your Atlassian credentials:

autohand mcp add mcp-atlassian env \
  JIRA_URL=https://your-company.atlassian.net \
  JIRA_USERNAME=your.email@company.com \
  JIRA_API_TOKEN=your_api_token \
  CONFLUENCE_URL=https://your-company.atlassian.net/wiki \
  CONFLUENCE_USERNAME=your.email@company.com \
  CONFLUENCE_API_TOKEN=your_api_token \
  uvx mcp-atlassian

Add --scope project after add to keep the configuration in the current project. See Autohand Code for current installation and CLI details.

3. Start Using

Ask your AI assistant to:

  • "Find issues assigned to me in PROJ project"

  • "Search Confluence for onboarding docs"

  • "Create a bug ticket for the login issue"

  • "Update the status of PROJ-123 to Done"

Related MCP server: MCP Atlassian

Documentation

Full documentation is available at mcp-atlassian.soomiles.com.

Documentation is also available in llms.txt format, which LLMs can consume easily:

Topic

Description

Installation

uvx, Docker, pip, from source

Authentication

API tokens, PAT, OAuth 2.0

Configuration

IDE setup, environment variables

HTTP Transport

SSE, streamable-http, multi-user

Tools Reference

All Jira & Confluence tools

Troubleshooting

Common issues & debugging

Compatibility

Product

Deployment

Support

Confluence

Cloud

Fully supported

Confluence

Server/Data Center

Supported (v6.0+)

Jira

Cloud

Fully supported

Jira

Server/Data Center

Supported (v8.14+)

Key Tools

Jira

Confluence

jira_search - Search with JQL

confluence_search - Search with CQL

jira_get_issue - Get issue details

confluence_get_page - Get page content

jira_create_issue - Create issues

confluence_create_page - Create pages

jira_update_issue - Update issues

confluence_update_page - Update pages

jira_transition_issue - Change status

confluence_add_comment - Add comments

98 tools total — See Tools Reference for the complete list.

Agent Skills

Pre-configured workflows and skill packages for AI assistants (Antigravity, Claude, Cursor):

Skill

Description

Location

generate-status-report

Summarizes Jira sprint metrics and Confluence updates.

skills/generate-status-report

capture-tasks-from-meeting-notes

Parses action items from meeting notes to draft Jira issues.

skills/capture-tasks-from-meeting-notes

triage-issue

Classifies Jira issues, suggests priority/components/labels, and flags duplicates.

skills/triage-issue

Security

Never share API tokens. Keep .env files secure. See SECURITY.md.

Contributing

See CONTRIBUTING.md for development setup.

License

MIT - See LICENSE. Not an official Atlassian product.

Available Tools

98 tools
confluence_add_commentAdd CommentB

Add a comment to a Confluence page.

Inputs: body (required), page_id (required). Returns: result

confluence_add_inline_commentAdd Inline CommentA
Destructive

Add an inline comment anchored to a text selection on a page.

Inputs: body (required), page_id (required), text_selection (required), text_selection_match_count, +1 more. Returns: result

confluence_add_labelAdd LabelA

Add label to Confluence content (pages, blog posts, or attachments).

Useful for:

  • Categorizing attachments (e.g., 'screenshot', 'diagram', 'legal-doc')

  • Tracking status (e.g., 'approved', 'needs-review', 'archived')

  • Filtering content by topic or version

Inputs: name (required), page_id (required). Returns: result

confluence_check_content_permissionsCheck Content PermissionsA
Read-only

Check whether a user or group can perform an operation on specific content.

Wraps POST /wiki/rest/api/content/{id}/permission/check.

Note: This tool is only available for Confluence Cloud. Server/Data Center instances use different permission APIs.

Returns a JSON object with a 'hasPermission' boolean indicating whether the subject has the requested permission on the content.

Inputs: operation (required), content_id (required), user_identifier (required), subject_type. Returns: result

confluence_copy_pageCopy PageA
Destructive

Copy a Confluence page to a new location.

On Confluence Cloud the native copy endpoint is used. On Server/Data Center the page body is fetched and a new page is created manually (attachments are not copied in the Server/DC path).

Inputs: new_title (required), source_page_id (required), destination_space_key (required), copy_attachments, +1 more. Returns: result

confluence_create_pageCreate PageB

Create a new Confluence page.

Inputs: title (required), space_key (required), emoji, content, +8 more. Returns: result

confluence_create_page_from_templateCreate Page from TemplateA

Create a new Cloud page pre-populated with a template's body.

This operation is only available for Confluence Cloud. Fetches the named template and creates a page with its storage-format content. The page can be edited afterwards via confluence_update_page.

Inputs: title (required), space_key (required), template_id (required), parent_id. Returns: result

confluence_delete_attachmentDelete AttachmentA
Destructive

Permanently delete an attachment from Confluence.

Warning: This action cannot be undone! The attachment and ALL its versions will be permanently deleted.

Use this tool to:

  • Remove outdated or incorrect attachments

  • Clean up duplicate files

  • Delete sensitive information that was accidentally uploaded

Best practices:

  • Verify the attachment ID before deletion using get_attachments

  • Consider downloading the attachment first as a backup

  • Check with content owners before deleting shared attachments

Inputs: attachment_id (required). Returns: result

confluence_delete_pageDelete PageA
Destructive

Delete an existing Confluence page.

Inputs: page_id (required). Returns: result

confluence_download_attachmentDownload AttachmentA
Read-only

Download an attachment from Confluence as an embedded resource.

Returns the attachment content as a base64-encoded embedded resource so that it is available over the MCP protocol without requiring filesystem access on the server. Files larger than 50 MB are not downloaded inline; a descriptive error message is returned instead.

Inputs: attachment_id (required).

confluence_download_content_attachmentsDownload All Content AttachmentsA
Read-only

Download all attachments for a Confluence content item as embedded resources.

Returns attachment contents as base64-encoded embedded resources so that they are available over the MCP protocol without requiring filesystem access on the server. Files larger than 50 MB are skipped with an error entry in the summary.

Inputs: content_id (required).

confluence_get_attachmentsGet Content AttachmentsA
Read-only

List all attachments for a Confluence content item (page or blog post).

Returns metadata about attachments including:

  • Attachment ID, title, and file type

  • File size and download URL

  • Creation/modification dates

  • Version information

Important: Confluence API returns 'application/octet-stream' as the media type for most binary files (PNG, JPG, PDF) instead of specific types like 'image/png'. For filtering by file type, using the 'filename' parameter is more reliable (e.g., filename='*.png' pattern matching if supported, or exact filename).

Useful for:

  • Discovering what files are attached to a page

  • Getting attachment IDs for download operations

  • Checking if a specific file exists

  • Listing images/documents for processing

Inputs: content_id (required), limit, start, filename, +1 more. Returns: result

confluence_get_commentsGet CommentsC
Read-only

Get comments for a specific Confluence page.

Inputs: page_id (required). Returns: result

confluence_get_inline_commentsGet Inline CommentsB
Read-only

Get all inline comments for a Confluence page.

Inputs: page_id (required). Returns: result

confluence_get_labelsGet LabelsA
Read-only

Get labels for Confluence content (pages, blog posts, or attachments).

Inputs: page_id (required). Returns: result

confluence_get_pageGet PageA
Read-only

Get content of a specific Confluence page by its ID, or by its title and space key.

Inputs: title, page_id, space_key, include_metadata, +1 more. Returns: result

confluence_get_page_childrenGet Page ChildrenA
Read-only

Get child pages and folders of a specific Confluence page.

Inputs: parent_id (required), limit, start, expand, +3 more. Returns: result

confluence_get_page_diffGet Page Version DiffA
Read-only

Get a unified diff between two versions of a Confluence page.

Inputs: page_id (required), to_version (required), from_version (required). Returns: result

confluence_get_page_historyGet Page HistoryA
Read-only

Get a historical version of a specific Confluence page.

Inputs: page_id (required), version (required), convert_to_markdown. Returns: result

confluence_get_page_imagesGet Page ImagesA
Read-only

Get all images attached to a Confluence page 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 render directly. Non-image attachments are excluded.

Files with ambiguous MIME types (application/octet-stream) are detected by filename extension as a fallback. Images larger than 50 MB are skipped with an error entry in the summary.

Inputs: content_id (required).

confluence_get_page_restrictionsGet Page RestrictionsA
Read-only

Get view and edit restrictions for a Confluence page.

Returns the current restriction lists for the read (view) and update (edit) operations. An empty list means the page is unrestricted for that operation.

Inputs: page_id (required). Returns: result

confluence_get_page_templateGet Page TemplateA
Read-only

Get a Cloud page template by ID, including its storage-format body.

Inputs: template_id (required). Returns: result

confluence_get_page_viewsGet Page ViewsA
Read-only

Get view statistics for a Confluence page.

Note: This tool is only available for Confluence Cloud. Server/Data Center instances do not support the Analytics API.

Inputs: page_id (required), include_title. Returns: result

confluence_get_space_page_treeGet Space Page TreeA
Read-only

Get page hierarchy for a Confluence space as a flat list.

Returns pages with parent_id and depth attributes for token-efficient processing. Filter by depth to focus on relevant sections, or find pages by title. Much more efficient than rendering full ASCII trees.

Use this to understand space organization before creating/moving pages.

Inputs: space_key (required), limit. Returns: result

confluence_get_space_permissionsGet Space PermissionsA
Read-only

List all permission assignments for a Confluence space.

Wraps GET /wiki/api/v2/spaces/{id}/permissions.

Note: This tool is only available for Confluence Cloud. Server/Data Center instances use different permission APIs.

Returns a JSON object with a 'results' list of permission assignment objects. Each entry contains the principal (user or group), the operation permitted, and the target. Use this to audit who has access to a space.

Inputs: space_id (required), limit, cursor. Returns: result

confluence_list_page_templatesList Page TemplatesA
Read-only

List Confluence page content templates.

This operation is only available for Confluence Cloud. Returns template metadata (ID, name, description, type) without the full body. Use confluence_get_page_template to fetch a template's body.

Inputs: limit, space_key. Returns: result

confluence_move_pageMove PageB
Destructive

Move a Confluence page to a new parent or space.

Inputs: page_id (required), position, target_parent_id, target_space_key. Returns: result

confluence_reply_to_commentReply to CommentB

Reply to an existing comment thread on a Confluence page.

Inputs: body (required), comment_id (required). Returns: result

confluence_search_userSearch UserA
Read-only

Search Confluence users using CQL (Cloud) or group member API (Server/DC).

Inputs: query (required), limit, group_name. Returns: result

confluence_set_page_restrictionsSet Page RestrictionsA
Destructive

Set view and edit restrictions on a Confluence page.

Replaces all existing restrictions with the provided lists. Omitting all parameters (or passing empty lists) removes all restrictions.

Inputs: page_id (required), edit_users, read_users, edit_groups, +1 more. Returns: result

confluence_update_pageUpdate PageC
Destructive

Update an existing Confluence page.

Inputs: title (required), page_id (required), emoji, content, +9 more. Returns: result

confluence_update_page_sectionUpdate Page SectionA
Destructive

Update a single section of a Confluence page without affecting the rest.

Replaces only the content beneath a named heading, leaving all other sections, macros, layouts, and Confluence-specific elements completely intact. This avoids the data loss that occurs when a full page is downloaded as Markdown, edited, and re-uploaded.

Inputs: page_id (required), new_content (required), heading_text (required), is_minor_edit, +2 more. Returns: result

confluence_upload_attachmentUpload AttachmentA
Destructive

Upload an attachment to Confluence content (page or blog post).

Provide the file either as a server-readable path ('file_path') or as base64-encoded content ('content_base64' together with 'filename'). The base64 form is intended for remote or containerized servers that cannot read host file paths. Exactly one of the two must be supplied.

If the attachment already exists (same filename), a new version is created. This is useful for:

  • Attaching documents, images, or files to a page

  • Updating existing attachments with new versions

  • Adding supporting materials to documentation

Inputs: content_id (required), comment, filename, file_path, +2 more. Returns: result

confluence_upload_attachmentsUpload Multiple AttachmentsA
Destructive

Upload multiple attachments to Confluence content in a single operation.

More efficient than calling upload_attachment multiple times. If files with the same names exist, new versions are created automatically.

Useful for:

  • Bulk uploading documentation assets (diagrams, screenshots, etc.)

  • Adding multiple related files to a page at once

  • Batch updating existing attachments with new versions

Inputs: content_id (required), file_paths (required), comment, minor_edit. Returns: result

jira_add_commentAdd CommentB

Add a comment to a Jira issue.

Inputs: body (required), issue_key (required), public, visibility. Returns: result

jira_add_issues_to_sprintAdd Issues to SprintC
Destructive

Add issues to a Jira sprint.

Inputs: sprint_id (required), issue_keys (required). Returns: result

jira_add_watcherAdd Issue WatcherA

Add a user as a watcher to a Jira issue.

Inputs: issue_key (required), user_identifier (required). Returns: result

jira_add_worklogAdd WorklogA
Destructive

Add a worklog entry to a Jira issue.

Inputs: issue_key (required), time_spent (required), comment, started, +2 more. Returns: result

jira_assign_issueAssign IssueA

Assign a Jira issue to a user using the dedicated assignment endpoint.

This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.

On Jira Server/DC the following identifier forms are all accepted: login name, email address, display name, or JIRAUSER key. The resolution order is: key lookup → email search (with email-as-username fallback) → text search → assignable-user search scoped to the issue.

Inputs: issue_key (required), assignee. Returns: result

jira_batch_create_issuesBatch Create IssuesB

Create multiple Jira issues in a batch.

Inputs: issues (required), validate_only. Returns: result

jira_batch_create_versionsBatch Create VersionsA

Batch create multiple versions in a Jira project.

Inputs: versions (required), project_key (required). Returns: result

jira_batch_get_changelogsBatch Get ChangelogsA
Read-only

Get changelogs for multiple Jira issues (Cloud only).

Inputs: issue_ids_or_keys (required), limit, fields. Returns: result

jira_create_customer_requestCreate Customer RequestB
Destructive

Create a Jira Service Management customer request.

Inputs: request_type_id (required), service_desk_id (required), request_field_values (required), attachments, +3 more. Returns: result

jira_create_issueCreate IssueA

Create a new Jira issue with optional Epic link or parent for subtasks.

Inputs: summary (required), issue_type (required), project_key (required), assignee, +3 more. Returns: result

jira_create_sprintCreate SprintB

Create Jira sprint for a board.

Inputs: name (required), board_id (required), end_date (required), start_date (required), +1 more. Returns: result

jira_create_versionCreate VersionB

Create a new fix version in a Jira project.

Inputs: name (required), project_key (required), start_date, description, +1 more. Returns: result

jira_delete_issueDelete IssueB
Destructive

Delete an existing Jira issue.

Inputs: issue_key (required). Returns: result

jira_download_attachmentsDownload AttachmentsA
Read-only

Download attachments from a Jira issue.

Returns attachment contents as base64-encoded content so that they are available over the MCP protocol without requiring filesystem access on the server. Image attachments are returned as EmbeddedResource blobs; all other attachments (documents, archives, etc.) are returned as TextContent carrying a base64 payload, since many MCP clients only forward EmbeddedResource blobs for recognized image MIME types and otherwise drop the attachment (#1419).

Inputs: issue_key (required).

jira_edit_commentEdit CommentB
Destructive

Edit an existing comment on a Jira issue.

Inputs: body (required), issue_key (required), comment_id (required), visibility. Returns: result

jira_get_agile_boardsGet Agile BoardsA
Read-only

Get jira agile boards by name, project key, or type.

Inputs: limit, start_at, board_name, board_type, +1 more. Returns: result

jira_get_all_projectsGet All ProjectsA
Read-only

Get all Jira projects accessible to the current user.

Inputs: include_archived. Returns: result

jira_get_board_issuesGet Board IssuesA
Read-only

Get all issues linked to a specific board filtered by JQL.

Inputs: jql (required), board_id (required), limit, expand, +2 more. Returns: result

jira_get_create_fieldsGet Create FieldsA
Read-only

Get fields available for creating an issue of a specific type.

Returns all fields (required and optional) for the given project and issue type, including field names, IDs, whether they're required, and their schema. Use jira_get_field_options when a returned field needs its allowed values.

Inputs: project_key (required), issue_type_id (required). Returns: result

jira_get_cross_project_dependenciesGet Cross-Project DependenciesA
Read-only

Find all cross-project issue links for a project.

Scans issues in the project, extracts every issue link whose target belongs to a different project, and groups them by target project and link type. Useful for dependency analysis across multi-project Jira setups.

Inputs: project_key (required), max_issues. Returns: result

jira_get_field_optionsGet Field OptionsA
Read-only

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 API. If context_id is not provided, automatically resolves to the global context.

Server/DC: Uses createmeta to get allowedValues. Requires project_key and issue_type parameters.

Inputs: field_id (required), contains, context_id, issue_type, +3 more. Returns: result

jira_get_issueGet IssueA
Read-only

Get details of a specific Jira issue.

Includes Epic links and relationship information. Use the include parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs) so that separate tool calls are not needed.

Inputs: issue_key (required), expand, fields, include, +4 more. Returns: result

jira_get_issue_datesGet Issue DatesA
Read-only

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 analysis.

Inputs: issue_key (required), include_status_changes, include_status_summary. Returns: result

jira_get_issue_development_infoGet Issue Development InfoA
Read-only

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 source control systems like Bitbucket, GitHub, or GitLab.

Inputs: issue_key (required), data_type, application_type. Returns: result

jira_get_issue_imagesGet Issue ImagesA
Read-only

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 render directly. Non-image attachments are excluded.

Files with ambiguous MIME types (application/octet-stream) are detected by filename extension as a fallback. Images larger than 50 MB are skipped with an error entry in the summary.

Inputs: issue_key (required).

jira_get_issue_proforma_formsGet Issue FormsA
Read-only

Get all ProForma forms associated with a Jira issue.

Uses the new Jira Forms REST API. Form IDs are returned as UUIDs.

Inputs: issue_key (required). Returns: result

jira_get_issues_development_infoGet Issues Development InfoA
Read-only

Get development information for multiple Jira issues.

Batch retrieves development panel information (PRs, commits, branches) for multiple issues at once.

Inputs: issue_keys (required), data_type, application_type. Returns: result

jira_get_issue_slaGet Issue SLAA
Read-only

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 via environment variables:

  • JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false)

  • JIRA_SLA_WORKING_HOURS_START: Start time (e.g., "09:00")

  • JIRA_SLA_WORKING_HOURS_END: End time (e.g., "17:00")

  • JIRA_SLA_WORKING_DAYS: Working days (e.g., "1,2,3,4,5" for Mon-Fri)

  • JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., "America/New_York")

Inputs: issue_key (required), metrics, include_raw_dates, working_hours_only. Returns: result

jira_get_issue_watchersGet Issue WatchersA
Read-only

Get the list of watchers for a Jira issue.

Inputs: issue_key (required). Returns: result

jira_get_proforma_form_detailsGet Form DetailsA
Read-only

Get detailed information about a specific ProForma form.

Uses the new Jira Forms REST API. Returns form details including ADF design structure.

Inputs: form_id (required), issue_key (required). Returns: result

jira_get_project_componentsGet Project ComponentsA
Read-only

Get all components for a specific Jira project.

Inputs: project_key (required). Returns: result

jira_get_project_epic_hierarchyGet Project Epic HierarchyA
Read-only

Group a project's epics under their cross-project parent issues.

Fetches all epics in the project, detects their parent issue via the parent field or inward issue links, then groups them by parent. Epics with no detected parent appear under "Unlinked". Useful for understanding how a project's epics roll up to initiatives in another project.

Inputs: project_key (required), max_epics. Returns: result

jira_get_project_fieldsGet Project FieldsA
Read-only

Get the fields available on issues of a project (the create schema), deduplicated across the project's issue types — i.e. which fields tickets in this project have, regardless of whether they are filled.

Inputs: project_key (required). Returns: result

jira_get_project_issuesGet Project IssuesB
Read-only

Get all issues for a specific Jira project.

Inputs: project_key (required), limit, start_at. Returns: result

jira_get_project_issue_typesGet Project Issue TypesA
Read-only

Get available issue types for a Jira project.

Returns the list of issue types (Bug, Task, Story, Epic, etc.) that can be created in the specified project. Use the returned issue type IDs with get_create_fields to discover what fields each type requires.

Inputs: project_key (required). Returns: result

jira_get_project_versionsGet Project VersionsA
Read-only

Get all fix versions for a specific Jira project.

Inputs: project_key (required). Returns: result

jira_get_queue_issuesGet Queue IssuesA
Read-only

Get issues from a Jira Service Desk queue.

Server/Data Center only. Not available on Jira Cloud.

Inputs: queue_id (required), service_desk_id (required), limit, start_at. Returns: result

jira_get_request_type_fieldsGet Request Type FieldsA
Read-only

Get field definitions for a Jira Service Management request type.

Inputs: request_type_id (required), service_desk_id (required). Returns: result

jira_get_request_typesGet Request TypesA
Read-only

Get request types for a Jira Service Management service desk.

Inputs: service_desk_id (required), limit, start_at. Returns: result

jira_get_service_desk_for_projectGet Service Desk For ProjectA
Read-only

Get the Jira Service Desk associated with a project key.

Server/Data Center only. Not available on Jira Cloud.

Inputs: project_key (required). Returns: result

jira_get_service_desk_queuesGet Service Desk QueuesA
Read-only

Get queues for a Jira Service Desk.

Server/Data Center only. Not available on Jira Cloud.

Inputs: service_desk_id (required), limit, start_at. Returns: result

jira_get_sprint_issuesGet Sprint IssuesB
Read-only

Get jira issues from sprint.

Inputs: sprint_id (required), limit, fields, start_at. Returns: result

jira_get_sprints_from_boardGet Sprints from BoardB
Read-only

Get jira sprints from board by state.

Inputs: board_id (required), limit, state, start_at. Returns: result

jira_get_transitionsGet TransitionsA
Read-only

Get available status transitions for a Jira issue.

Inputs: issue_key (required). Returns: result

jira_get_user_profileGet User ProfileA
Read-only

Retrieve profile information for a specific Jira user.

Inputs: user_identifier (required). Returns: result

jira_get_worklogGet WorklogA
Read-only

Get worklog entries for a Jira issue.

Inputs: issue_key (required). Returns: result

jira_move_issueMove Issue to ProjectA
Destructive

Move a Jira issue to a different project (Jira Cloud only).

Uses Jira Cloud's bulk move API to perform a cross-project move. The issue keeps its current issue type and may be assigned a new key in the target project (e.g., OLDPROJ-123 becomes NEWPROJ-456).

The move is processed asynchronously on Jira's side; this tool polls until confirmed or times out after 30 seconds.

Inputs: issue_key (required), target_project_key (required). Returns: result

jira_move_issues_to_backlogMove Issues to BacklogA

Move issues to the backlog, removing them from any sprint.

Inputs: issue_keys (required). Returns: result

jira_remove_watcherRemove Issue WatcherA
Destructive

Remove a user from watching a Jira issue.

Inputs: issue_key (required), username, account_id. Returns: result

jira_search_assignable_usersSearch Assignable UsersA
Read-only

Search Jira users assignable in a given project or issue.

Use this when you have a display name / partial name / email fragment and need a concrete identifier (name / key for Server/DC, accountId for Cloud) to feed into assignee, reporter, watcher, etc.

Returns the full result set so the caller can disambiguate when several users match — get_user_profile only resolves one identifier and is not designed for human-name search.

Exactly one of project_key or issue_key must be provided — the underlying API (/user/assignable/search) requires a project or issue context and works without the global "Browse Users" permission that bot accounts in locked-down DC instances often lack.

Inputs: query (required), limit, issue_key, project_key. Returns: result

jira_search_fieldsSearch FieldsB
Read-only

Search Jira fields by keyword with fuzzy match.

Inputs: limit, keyword, refresh. Returns: result

jira_search_projectsSearch ProjectsA
Read-only

Search for Jira projects by name or key prefix.

Uses the projects picker endpoint to return a ranked list of matching projects without fetching every visible project on the instance.

Inputs: query (required), max_results, current_project_ids. Returns: result

jira_transition_issueTransition IssueC
Destructive

Transition a Jira issue to a new status.

Inputs: issue_key (required), transition_id (required), fields, comment. Returns: result

jira_update_issueUpdate IssueA
Destructive

Update an issue and optionally transition, comment, and log work.

Inputs: issue_key (required), fields, comment, worklog, +7 more. Returns: result

jira_update_proforma_form_answersUpdate Form AnswersA
Destructive

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 LIMITATION - DATETIME fields: The Jira Forms API does NOT properly preserve time components in DATETIME fields. Only the date portion is stored; times are reset to midnight (00:00:00).

Workaround for DATETIME fields: Use jira_update_issue to directly update the underlying custom fields instead:

  1. Get the custom field ID from the form details (question's "jiraField" property)

  2. Use jira_update_issue with fields like: {"customfield_XXXXX": "2026-01-09T11:50:00-08:00"}

Example:

# Instead of updating via form (loses time):
# jira_update_proforma_form_answers(issue_key, form_id, [{"questionId": "91", "type": "DATETIME", "value": "..."}])

# Use direct field update (preserves time):
jira_update_issue(issue_key, {"customfield_10542": "2026-01-09T11:50:00-08:00"})

Automatic DateTime Conversion: For DATE and DATETIME fields, you can provide values as:

  • ISO 8601 strings (e.g., "2024-12-17T19:00:00Z", "2024-12-17")

  • Unix timestamps in milliseconds (e.g., 1734465600000)

The tool automatically converts ISO 8601 strings to Unix timestamps.

Example answers: [ {"questionId": "q1", "type": "TEXT", "value": "Updated description"}, {"questionId": "q2", "type": "SELECT", "value": "Product A"}, {"questionId": "q3", "type": "NUMBER", "value": 42}, {"questionId": "q4", "type": "DATE", "value": "2024-12-17"} ]

Common answer types:

  • TEXT: String values

  • NUMBER: Numeric values

  • DATE: Date values (ISO 8601 string or Unix timestamp in ms)

  • DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE

  • SELECT: Single selection from options

  • MULTI_SELECT: Multiple selections (value as list)

  • CHECKBOX: Boolean values

Inputs: answers (required), form_id (required), issue_key (required). Returns: result

jira_update_sprintUpdate SprintB
Destructive

Update jira sprint.

Inputs: sprint_id (required), goal, name, state, +2 more. Returns: result

jira_update_versionUpdate VersionA
Destructive

Update an existing fix version in a Jira project.

Only fields explicitly provided are modified; other attributes of the version are left untouched. Useful for archiving/unarchiving versions, renaming, or shifting release dates without recreating them.

Inputs: version_id (required), name, archived, released, +3 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 98 tools

    Disambiguation3/5

    Most tools follow a clear resource+action pattern, but there are genuine overlaps: jira_update_issue can transition, comment, and log work alongside dedicated jira_transition_issue, jira_add_comment, and jira_add_worklog tools; jira_get_issue_dates and jira_get_issue_sla both analyze status/time; and multiple issue-listing variants (project, board, sprint, queue, JQL) require careful selection. The descriptions do a good job of clarifying scope, so the ambiguity is manageable but not eliminated.

    Naming Consistency5/5

    All tools consistently use snake_case with jira_/confluence_ prefixes and a clear verb_noun structure: get_, create_, update_, delete_, add_, remove_, search_. Batch variants follow the same pattern (batch_create, batch_get, upload_attachments), making the naming highly predictable across 98 tools.

    Tool Count1/5

    98 tools is far beyond even the 50+ extreme-mismatch threshold. While the server legitimately spans both Jira and Confluence with many subdomains, the sheer surface area creates a heavy navigation burden for agents and could benefit from consolidation or modular sub-servers.

    Completeness4/5

    The toolset provides remarkably comprehensive coverage: Jira issues, transitions, comments, worklogs, watchers, links, attachments, sprints, versions, projects, fields, forms, SLA/dev info, and Confluence pages, comments, labels, restrictions, permissions, attachments, templates, and history/diff. Minor gaps such as no Jira delete-comment, no Confluence delete-comment, and no remove-remote-link keep it from a 5, but agents can generally work around these.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Atlassian Jira and Confluence across Cloud and Server/Data Center environments. It supports tasks like searching and summarizing documentation, managing Jira issues, and creating content through natural language.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that integrates with Jira and Confluence to enable AI-powered issue management, content search, and document creation. It supports both Cloud and on-premise deployments, allowing users to automate workspace tasks through natural language.
      MIT