Searches for Jira users by name or email.

Args: query: Name, email, or username fragment to search for. max_results: Maximum number of results to return.

Lists Jira issues using JQL.

By default returns key, summary, status, priority, assignee. Use additional_fields to include extra Jira fields in the response.

Args: jql: JQL query string. next_page_token: Token for pagination (returned in previous response). max_results: Maximum number of results to return. additional_fields: Extra Jira field names to include, e.g. ["issuetype", "labels", "created", "updated", "duedate", "components", "fixVersions", "reporter", "resolution", "parent", "subtasks"].

Gets details of a specific Jira issue.

By default returns a compact set of fields. Use additional_fields to request more without bloating every response.

Args: issue_key: The issue key (e.g. "PROJ-123"). additional_fields: Extra Jira field names to include, e.g. ["components", "fixVersions", "duedate", "resolution", "parent", "subtasks", "issuetype", "customfield_XXXXX"].

Lists all available Jira fields (standard and custom).

Use this to discover field IDs you can pass as additional_fields to read_jira_issue, list_jira_issues, or jira_update_issue.

Adds a comment to a Jira issue.

Args: issue_key: The ID or key of the issue. comment: The comment content in markdown. Supports headings, bold, italic, strikethrough, links, code blocks, lists, tables, etc.

Mentioning users: To tag a user, first call jira_search_users to find their accountId, then use @[accountId] in the text (e.g. @[712020:abc123]). You can also use @username which auto-resolves if there is exactly one match, but will fail if ambiguous — prefer @[accountId].

Edits an existing comment on a Jira issue.

Args: issue_key: The ID or key of the issue. comment_id: The ID of the comment to edit (from jira_get_comments). comment: The new comment content in markdown. Supports headings, bold, italic, strikethrough, links, code blocks, lists, tables, etc.

Mentioning users: To tag a user, first call jira_search_users to find their accountId, then use @[accountId] in the text (e.g. @[712020:abc123]). You can also use @username which auto-resolves if there is exactly one match, but will fail if ambiguous -- prefer @[accountId].

Deletes a comment from a Jira issue.

Args: issue_key: The ID or key of the issue. comment_id: The ID of the comment to delete (from jira_get_comments).

Transitions a Jira issue to a new status using a transition ID. Use jira_get_transitions to find available transition IDs.

Gets available transitions for a Jira issue.

Updates fields on a Jira issue.

Args:
    issue_key: The issue key (e.g. "PROJ-123").
    summary: New summary text.
    description: New description in markdown. Supports headings, bold,
        italic, strikethrough, links, code blocks, lists, tables, etc.
    additional_fields: Dict of field_id -> value for simple fields
        (plain text, dates, numbers, selects).
        Use jira_list_fields to discover field IDs.
        Example: {"duedate": "2026-04-01", "labels": ["bug"]}
    rich_text_fields: Dict of field_id -> markdown string for rich text
        fields that need ADF conversion (e.g. Developer Notes,
        Deployment Info). These get converted to Atlassian Document
        Format automatically.
        Example: {"customfield_10402": "## Plan

• Step 1

• Step 2"}

  Mentioning users (in description and rich_text_fields): First call jira_search_users to find the accountId, then use @[accountId] in the text (e.g. @[712020:abc123]).

Creates a new Jira issue. For description, accepts a markdown string. Supports headings, bold, italic, strikethrough, links, code blocks, lists, tables, etc.

Mentioning users: To tag a user, first call jira_search_users to find their accountId, then use @[accountId] in the text (e.g. @[712020:abc123]). You can also use @username which auto-resolves if there is exactly one match, but will fail if ambiguous — prefer @[accountId].

Gets all comments for a Jira issue.

Downloads a Jira attachment by ID, saves it to a temp file, and returns the file path.

Lists Confluence pages in a space.

Gets the content of a Confluence page.

Updates a Confluence page. If version is not provided, it will be automatically incremented.

MERMAID DIAGRAMS: Confluence Cloud uses the Mermaid Diagrams plugin. You CANNOT create rendered diagrams programmatically. The mermaid-cloud macro only references diagram content in the plugin's internal storage (not accessible via API).

To include a Mermaid diagram, provide it as a code block for the user to manually convert: <ac:structured-macro ac:name="code" ac:schema-version="1"> <ac:parameter ac:name="language">text</ac:parameter> ac:plain-text-body</ac:plain-text-body> </ac:structured-macro>

The user can then convert this code block to a rendered diagram in the Confluence editor.

Creates a new Confluence page, optionally under a parent page.

Deletes a Confluence page.

Searches Confluence content using CQL (Confluence Query Language). Example: title ~ "meeting" AND label = "notes"

Gets all comments for a Confluence page.

Adds a comment to a Confluence page. Set parent_comment_id to reply to an existing comment.

Gets an image attachment on a Confluence page and returns it as an Image.