- Category: model context protocol
- Auth: DCR_OAUTH
- Composio-managed OAuth available? No
- Tools: 213
- Triggers: 0
- Slug:
ATLASSIAN_MCP - Version: 20261026_00
Tools
Addconfluencecontentpermissions
Addconfluencecontentpermissions
ATLASSIAN_MCP_ADD_CONFLUENCE_CONTENT_PERMISSIONSAdds one or more content-level permission grants to a single Confluence content entity. Existing grants for other principals are preserved; to replace the full set, use replaceConfluenceContentPermissions instead.These are Specific access grants: operation read = Can view; update = Can edit and already includes view. A principal has exactly ONE level, so assigning read to a principal who currently has update is a downgrade to view-only. Never include the same principal under both operations. Adding a grant does NOT restrict others, make content private, or change General access; use setConfluenceContentRestrictionState for that baseline. Private creation already gives the creator update. Do not add read for that creator, because update already includes view. Existing-state and self-lockout rules are enforced by the Confluence monolith.Each grant pairs an operation with a list of principals. Pass the grants via the permissions input, an array of objects shaped exactly like: [ { “operation”: “read”, “principals”: [ { “principalType”: “user”, “principalId”: “<atlassian-account-id>” }, { “principalType”: “group”, “principalId”: “<group-id>” } ] } ] Enums: operation is one of read | update; principalType is one of user | group. For a user, principalId is the Atlassian account ID; for a group, principalId is the group ID.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.operation (read | update) and a principals array. Each principal has a principalType (user | group) and a principalId (Atlassian account ID for a user, group ID for a group). A principal must appear under only one operation across the entire request. Example: [{ “operation”: “read”, “principals”: [{ “principalType”: “user”, “principalId”: “5b10a…” }] }].Addconfluencereaction
Addconfluencereaction
ATLASSIAN_MCP_ADD_CONFLUENCE_REACTIONAdd emoji reaction to Confluence contentInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Addconnectionstogoals
Addconnectionstogoals
ATLASSIAN_MCP_ADD_CONNECTIONS_TO_GOALSAdd one type of connection to one or more Atlassian Goals.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Addconnectionstoprojects
Addconnectionstoprojects
ATLASSIAN_MCP_ADD_CONNECTIONS_TO_PROJECTSAdd one type of connection to one or more Atlassian Projects.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Addgraphcontext
Addgraphcontext
ATLASSIAN_MCP_ADD_GRAPH_CONTEXTAdds a relationship between two entities in the Teamwork Graph (e.g. linking two Jira work items, marking one as blocking another, attaching a remote link, or connecting a Jira work item to an Atlas project or goal).Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Addlabelstoconfluencecontent
Addlabelstoconfluencecontent
ATLASSIAN_MCP_ADD_LABELS_TO_CONFLUENCE_CONTENTAdd labels to any Confluence content (page, blogpost, attachment, custom content)Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Addoreditjiraissuecomment
Addoreditjiraissuecomment
ATLASSIAN_MCP_ADD_OR_EDIT_JIRA_ISSUE_COMMENTAdd a comment to a Jira issue, or edit an existing one: omit commentId to add, or pass one from listJiraIssueComments to edit. Returns the commentId, needed to edit or delete it later. When no file was appended through inlineFileId, it also returns the echoed body and its format (appliedContentFormat).Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.{"type":"group"|"role","value":"<name>"}. Role and group names are site-specific, so do not reuse a name from another site. On JSM this does not make a comment internal — a restricted comment stays customer-visible (jsdPublic: true). Use jsmCommentType: "internalNote" for that.Addoreditjiraissueworklog
Addoreditjiraissueworklog
ATLASSIAN_MCP_ADD_OR_EDIT_JIRA_ISSUE_WORKLOGLog time spent on a Jira issue, or edit an existing worklog: omit worklogId to add, or pass one from listJiraIssueWorklogs to edit, which changes only the fields you pass. A new worklog is always logged as the calling user; an edit keeps its original author. Jira reduces the issue’s remaining estimate by the time logged (by the difference on an edit). To change the estimate itself, use editJiraIssue. Returns the worklog’s id, needed to edit it later, with the stored timeSpent and started.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.{"type":"group"|"role","value":"<name>"}. Examples: {"type":"role","value":"Administrators"}, {"type":"group","value":"jira-software-users"}. When omitted, the worklog is visible to everyone who can view the issue.Approvejsmrequestresolverplans
Approvejsmrequestresolverplans
ATLASSIAN_MCP_APPROVE_JSM_REQUEST_RESOLVER_PLANSApprove the current Request Resolver plans for explicitly selected JSM issue keys after the user has reviewed their plans with getJsmRequestResolverPlans and confirmed approval. Approval applies to each request’s current plan at execution time, which may have changed since retrieval. The caller must be the request’s human assignee or delegator. Returns one result per input in order; approved means approval was accepted, not that execution is complete. Output fields include requests[].issueKey, requests[].status, and approver.displayName; use these paths when selecting responseFields. Duplicate keys for the same request are submitted once per call. This is not idempotent across calls. For an unknown outcome, refresh the plan before any further approval; never automatically retry approval. Use getJsmRequestResolverPlans to check subsequent execution status. Does not decide customer-portal approvals.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Archiveconfluencecontent
Archiveconfluencecontent
ATLASSIAN_MCP_ARCHIVE_CONFLUENCE_CONTENTArchive a single Confluence content entityInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Atlassianuserinfo
Atlassianuserinfo
ATLASSIAN_MCP_ATLASSIAN_USER_INFOReturns the accountId of the current userCompleteconfluencetask
Completeconfluencetask
ATLASSIAN_MCP_COMPLETE_CONFLUENCE_TASKMark a Confluence inline task as completeInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Convertconfluencecontentmode
Convertconfluencecontentmode
ATLASSIAN_MCP_CONVERT_CONFLUENCE_CONTENT_MODEConvert a Confluence page or live doc between classic page mode and live-doc modeInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Convertjiraissuehierarchy
Convertjiraissuehierarchy
ATLASSIAN_MCP_CONVERT_JIRA_ISSUE_HIERARCHYConvert an existing Jira issue across hierarchy levels: a standard issue (Task, Bug, Story) into a sub-task under a parent, or a sub-task back into a standard issue. Mirrors Jira’s Move / Convert-to-sub-task wizard: preview destination compatibility (mode=preview_step1), preview field retain/remap/drop (mode=preview_step2), then execute (mode=confirm). Do not use this for same-level type edits such as Bug → Story — use editJiraIssue for those. Task → Sub-task: always ask the user for parentIssueKey before calling. Do not search for, infer, or pick a parent. If they did not name a parent, ask them instead of calling this tool. The parent must be a standard issue. If this result has CHILD_ISSUES_WILL_REPARENT, those children will get the same new parent — ask the user to accept that, then confirm with acknowledgeChildReparent=true. If this result has SOURCE_HAS_SUBTASKS, the convert is blocked; tell the user that. If this result has MOVE_PERMISSION_REQUIRED, the user lacks Jira Bulk change or Move permission — tell them to convert in the Jira UI. Do not retry. Do not mention another project style. If preview execution.method is bulk-move, or confirm returns MOVE_CONFIRMATION_REQUIRED, this is Jira’s Move wizard: list the destination project, statusMapping, and fieldPlan.dropped to the user and ask them to accept that status change and that those fields will be dropped. Do not convert until they accept, then retry with mode=confirm and acknowledgeMove=true. If they decline, stop. Sub-task → Task: no parent needed; confirm clears the parent. After convert, reply with this issue’s key, new type, and parent. If appliedChanges.dropped is present, also name those dropped fields. If appliedChanges.status is present, also name that status change. Do not mention bulk-move permissions or project-style notes unless this result has MOVE_PERMISSION_REQUIRED.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Copyconfluencecontent
Copyconfluencecontent
ATLASSIAN_MCP_COPY_CONFLUENCE_CONTENTCopy a Confluence page, whiteboard, database, folder, or embed to a new parentInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createartifactsupload
Createartifactsupload
ATLASSIAN_MCP_CREATE_ARTIFACTS_UPLOADStep 1 of 2 for uploading a new artifact or a new version of an existing artifact. Creates an upload and returns a pre-signed URL and instructions for transferring the file’s bytes directly. After the upload completes, call publishArtifact (step 2) with the returned completionPayload.contentId and artifact metadata to finalize and get the share URL. This does not publish the artifact by itself. Requires code execution and HTTP upload capability.Input Parameters
wc -c < "$file"; never estimate. Equivalent Python, Node, or browser code is valid; encode text as UTF-8 before counting and hashing.execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.openssl dgst -sha256 -binary "$file" | openssl base64 -A or shasum -a 256 < "$file" | awk '{print $1}' | xxd -r -p | base64. Equivalent Python, Node, or browser code is valid. Hash the same unchanged bytes used for length and the subsequent upload.Createartifactthumbnailupload
Createartifactthumbnailupload
ATLASSIAN_MCP_CREATE_ARTIFACT_THUMBNAIL_UPLOADCreate a thumbnail for an artifact using an image generated locally or supplied by the user. Use only when the user explicitly requests a thumbnail. Requires artifact ownership and applies to the latest version. Creates a thumbnail only when none exists for that version. Overwriting, replacing, or regenerating an existing thumbnail is not supported. For HTML and PDF, use a static 672-by-400 PNG (1.68:1), capturing rendered HTML and a representative animation frame, or the first PDF page. Returns a pre-signed URL and instructions for uploading the image. No publishArtifact call is needed.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createcapacityplannonprojectwork
Createcapacityplannonprojectwork
ATLASSIAN_MCP_CREATE_CAPACITY_PLAN_NON_PROJECT_WORKCreate a non-project work item in Individual Capacity Planning. “Non-project work” is a bucket of time that is not a Jira issue or an Atlas project, such as Leave, Run the Business (RtB), on-call, or training. USE WHEN the user asks to create a new non-project work item, or a category of work that does not already exist as a Jira issue or Atlas project. Search first with listCapacityPlanNonProjectWork to avoid creating a duplicate - the match is on name and is case-insensitive. Non-project work is owned by Capacity Planning and exists nowhere else in Atlassian, so it can only be created through this tool. A contributor must be supplied: the new work item is created together with a work association for that person, so it is immediately allocatable to them. Allocate additional people or set the effort per period afterwards with updateCapacityPlanAllocations, using the ARI returned here as workId. On success, nonProjectWork contains the created item’s name and ari - use that ari as workId for updateCapacityPlanAllocations rather than fabricating one.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createconfluenceattachment
Createconfluenceattachment
ATLASSIAN_MCP_CREATE_CONFLUENCE_ATTACHMENTPrepare a Confluence attachment upload and return a local curl commandInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createconfluencecomment
Createconfluencecomment
ATLASSIAN_MCP_CREATE_CONFLUENCE_COMMENTCreate or reply to a comment on a Confluence page or blog postInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createconfluencecontent
Createconfluencecontent
ATLASSIAN_MCP_CREATE_CONFLUENCE_CONTENTCreate a new Confluence page, blog post, live doc, whiteboard, database, embed, smart link, or folder.Before choosing body.format or authoring a body, call getContentFormatGuide through execute with name=getContentFormatGuide and inputs={toolName}. Use createConfluencePage for pages, blog posts, and live docs; createConfluenceWhiteboard for whiteboards; or createConfluenceDatabase for databases.Space instructions describe how to author content in a Confluence space. Apply relevant guidance to the content you create or update. Follow this decision rule:- Before authoring, call getConfluenceSpace for the target space unless getConfluenceContent returned metadata.hasSpaceInstructions=false for content in that space. If getConfluenceSpace already returned for the same cloudId and space during the current task, reuse its spaceInstructions and do not call it again.
- When the value is true or unknown and instructions have not been loaded, you must call getConfluenceSpace once before authoring through execute with name=getConfluenceSpace, top-level cloudId, and inputs={spaceIdOrKey}.
- Apply any returned spaceInstructions. If a successful response omits them, no instructions are configured; author with defaults and do not block.
Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createconfluenceinfographicforpage
Createconfluenceinfographicforpage
ATLASSIAN_MCP_CREATE_CONFLUENCE_INFOGRAPHIC_FOR_PAGECreate an infographic in a page workflow. Use only when a Confluence page creation or editing skill or guided workflow selects it; never as a standalone tool. Returns a media reference for embedding, which may sync later. Before prompting, reuse the shared Remix guide (headed ## Remix embeds) if its text is in your current context. Only if missing, call getContentFormatGuide with toolName=createConfluenceInfographicForPage and follow its Remix guidance. Generation and billing finish asynchronously; typical cost is 15–30 Rovo credits. Download detailed billing data for final usage; match any returned correlationId and usageUniqueId.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createconfluencemauiapp
Createconfluencemauiapp
ATLASSIAN_MCP_CREATE_CONFLUENCE_MAUI_APPCreate a Maui app in a page workflow. Use only when a Confluence page creation or editing skill or guided workflow selects it; never as a standalone tool. Returns a reserved app ID and embed URL for the owning page. Before prompting, reuse the shared Remix guide (headed ## Remix embeds) if its text is in your current context. Only if missing, call getContentFormatGuide with toolName=createConfluenceMauiApp and follow its Remix guidance. Generation and billing finish asynchronously; typical cost is 15–30 Rovo credits. Download detailed billing data for final usage; match any returned correlationId and usageUniqueId.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createconfluencespace
Createconfluencespace
ATLASSIAN_MCP_CREATE_CONFLUENCE_SPACECreate a Confluence space. Successful responses include id, key, and homepageId (the homepage / sidebar root content ID).Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createfocusarea
Createfocusarea
ATLASSIAN_MCP_CREATE_FOCUS_AREACreate a new Focus area in a workspace. Call getFocusAreaTypes first and use an enabled type UUID for focusAreaTypeId — do not fabricate it. Optionally set parentFocusAreaIdentifier (UUID, ARI, or Focus page URL); if set, the parent’s type must be a higher hierarchy level than the type being created. Optionally set startDate and targetDate as { date, confidence } where date is YYYY-MM-DDTHH:mm (e.g. 2026-08-10T00:00; bare dates are not accepted) and confidence is DAY, MONTH, or QUARTER. Omit owner to default to the creating user. Returns the created focus area (identifiers, type, owner, parent, dates, status, health, timestamps). Use getFocusArea for expansions such as aboutContent, statusUpdates, or subFocusAreas. When passing both cloudId and a parent ARI, they must refer to the same site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createfocusareastatusupdate
Createfocusareastatusupdate
ATLASSIAN_MCP_CREATE_FOCUS_AREA_STATUS_UPDATECreate a status update on a focus area, or save it as a draft. A status update is a change to one or more of status, health, summary, target date. Changing status needs an id discovered first with getFocusArea and include.statusTransitions; health does not. Passing only focusAreaIdentifier still posts a visible, empty update when publishing, so never call this tool speculatively. Field-level behavior for status, health, summary, target date, and draft constraints is documented on the inputs.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Creategoal
Creategoal
ATLASSIAN_MCP_CREATE_GOALCreate an Atlassian Goal or Success Measure using an enabled Goal Type.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Creategoalupdate
Creategoalupdate
ATLASSIAN_MCP_CREATE_GOAL_UPDATECreate a progress update for an existing Atlassian Goal.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createjiraboard
Createjiraboard
ATLASSIAN_MCP_CREATE_JIRA_BOARDCreate a new company-managed Jira Software board (scrum or kanban) from an existing filter. Requires a filter ID the user can view. When location is omitted, the board is filed in the single company-managed project from the filter’s JQL. Team-managed (TMP) locations are always rejected: TMP projects are 1:1 project to board (one built-in board at project creation, no way to add another). User locations are also rejected. The response includes a url that opens the board. The filter decides which issues the board shows; location only decides where the board is filed in navigation.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createjiraissue
Createjiraissue
ATLASSIAN_MCP_CREATE_JIRA_ISSUECreate a new Jira issue. Custom fields go in additional_fields: keyed by field name, values are resolved automatically, so no field lookup is needed first (user fields take accountIds); keyed by customfield_* ID, pass the value in Jira’s format. A rejected create returns a repairHint and names the field at fault where there is one, with its allowedValues when known, so retry from that. If sprint assignment fails, the response still has the new issue’s key and sprintAssignment.assigned: false — do not create it again.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createjiraissuelink
Createjiraissuelink
ATLASSIAN_MCP_CREATE_JIRA_ISSUE_LINKCreate a link between two existing issues — blocks, duplicates, clones, relates. Hierarchy is not a link: a parent or epic is the issue’s parent field. To link an issue to anything outside Jira — a page, a document, any URL — use createJiraIssueRemoteIssueLink.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createjiraissueremoteissuelink
Createjiraissueremoteissuelink
ATLASSIAN_MCP_CREATE_JIRA_ISSUE_REMOTE_ISSUE_LINKCreate a native web link in a Jira issue’s Web links section for a Confluence page or external HTTP(S) URL. Not a URL custom field; for an issue-to-issue dependency use createJiraIssueLink.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createjsmrequest
Createjsmrequest
ATLASSIAN_MCP_CREATE_JSM_REQUESTCreate a Jira Service Management customer-request work item using an explicit JSM service desk ID, JSM request type ID, and request field values. Do not use Jira issue type IDs or generic Jira create-issue workflows. First use getJsmRequestCreationOptions to select a JSM request type, then getJsmRequestTypeFields to build requestFieldValues.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createloomfolder
Createloomfolder
ATLASSIAN_MCP_CREATE_LOOM_FOLDERCreate a new folder in the current Loom workspace, optionally nested under a parent folder or placed in a space. Returns the new folder’s id, which you can pass to moveLoomVideoToFolder. To list existing folders instead of creating one, use listLoomFolders.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createloomvideocomment
Createloomvideocomment
ATLASSIAN_MCP_CREATE_LOOM_VIDEO_COMMENTPost a comment on a Loom video, anchored to a specific point in the video. The timestamp is in SECONDS (for example 90 for the 1:30 mark). Use this to leave feedback or a note at a moment in the recording. To read existing comments use getLoomVideo with expand: [“comments”]; to add an emoji reaction instead of a text comment use createLoomVideoReaction. Identify the video by ARI or share URL. NOTE: the returned timestamp is remapped onto the video’s current (post-trim) timeline, so for a video with trimmed/edited ranges the echoed value can come back up to 1 second lower than the value sent (never higher); for videos with no trims it always matches exactly.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createloomvideoreaction
Createloomvideoreaction
ATLASSIAN_MCP_CREATE_LOOM_VIDEO_REACTIONAdd an emoji reaction to a Loom video, anchored to a specific point in the video. The timestamp is in SECONDS (for example 90 for the 1:30 mark), the same unit as createLoomVideoComment. Use a Loom-native reaction name (joy, love, wow, nervous, yay, up, down) or an extended emoji slug. To leave a text comment instead, use createLoomVideoComment. Identify the video by ARI or share URL.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createloomvideoupload
Createloomvideoupload
ATLASSIAN_MCP_CREATE_LOOM_VIDEO_UPLOADStep 1 of 2 for uploading a new video to Loom. Creates an upload and returns a ready-to-run local script (plus raw upload endpoints) that transfers the file’s bytes. After the script reports the upload is complete, call publishLoomVideo (step 2) with the returned completionPayload to finalize and get the share URL. This does not publish the video by itself.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createproject
Createproject
ATLASSIAN_MCP_CREATE_PROJECTCreate an Atlassian Project.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createprojectupdate
Createprojectupdate
ATLASSIAN_MCP_CREATE_PROJECT_UPDATEPost a progress update on an existing Atlassian Project, or save it as an unposted draft with isDraft. Posting is immediately visible on the Project and notifies its followers, so only post when the user asked to; use isDraft to leave it for them to review and post themselves. The response carries isDraft so you can tell which happened, and a draft returns fewer fields than a posted update.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Createteam
Createteam
ATLASSIAN_MCP_CREATE_TEAMCreate an Atlassian team with a bounded name, optional description, MEMBER_INVITE or OPEN membership settings, and up to 50 initial account IDs. Tenant and organization are derived by the server.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Decidejsmrequestapproval
Decidejsmrequestapproval
ATLASSIAN_MCP_DECIDE_JSM_REQUEST_APPROVALApprove or decline a pending approval on an existing Jira Service Management request. Provide the request issue ID/key and an explicit decision of approve or decline. approvalId is optional; when omitted, the tool discovers pending request approvals and proceeds only when exactly one answerable approval is unambiguous. Use this for approval decisions, not workflow transitions, field edits, or comments.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Diffconfluencecontentversions
Diffconfluencecontentversions
ATLASSIAN_MCP_DIFF_CONFLUENCE_CONTENT_VERSIONSCompute a unified diff between two versions of a Confluence page, live doc, or blog postInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Disableconfluencepubliclink
Disableconfluencepubliclink
ATLASSIAN_MCP_DISABLE_CONFLUENCE_PUBLIC_LINKDisable the external public link (anonymous share) for a Confluence pageInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Downloadconfluenceattachment
Downloadconfluenceattachment
ATLASSIAN_MCP_DOWNLOAD_CONFLUENCE_ATTACHMENTGet a Confluence attachment download URL and return a local curl commandInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Downloadjiraissueattachment
Downloadjiraissueattachment
ATLASSIAN_MCP_DOWNLOAD_JIRA_ISSUE_ATTACHMENTGet a short-lived download URL for a Jira attachment and return a local downloadCommand. Run it from your shell to save the file.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Editconfluenceinfographicforpage
Editconfluenceinfographicforpage
ATLASSIAN_MCP_EDIT_CONFLUENCE_INFOGRAPHIC_FOR_PAGEEdit an infographic in a page workflow. Use only when a Confluence page editing skill or guided workflow selects it; never as a standalone tool. Regenerates the existing infographic and returns a new placeholder media reference for embedding. Before prompting, reuse the shared Remix guide (headed ## Remix embeds) if its text is in your current context. Only if missing, call getContentFormatGuide with toolName=editConfluenceInfographicForPage and follow its Remix guidance. Generation and billing finish asynchronously; typical cost is 15–30 Rovo credits. Download detailed billing data for final usage; match any returned correlationId and usageUniqueId.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Editconfluencemauiapp
Editconfluencemauiapp
ATLASSIAN_MCP_EDIT_CONFLUENCE_MAUI_APPEdit a Maui app in a page workflow. Use only when a Confluence page editing skill or guided workflow selects it; never as a standalone tool. Regenerates the existing app and returns a new placeholder Maui ID and embed URL. Before prompting, reuse the shared Remix guide (headed ## Remix embeds) if its text is in your current context. Only if missing, call getContentFormatGuide with toolName=editConfluenceMauiApp and follow its Remix guidance. Generation and billing finish asynchronously; typical cost is 15–30 Rovo credits. Download detailed billing data for final usage; match any returned correlationId and usageUniqueId.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Editjiraentityproperty
Editjiraentityproperty
ATLASSIAN_MCP_EDIT_JIRA_ENTITY_PROPERTYSets a single property (technical key/value store) on a specific Jira entity (issue, issueComment, issueWorklog, dashboardItem, user), creating or overwriting it. Returns {key, entityType, status}, status being “created” or “updated”; the value you wrote is not returned — read it back with getJiraEntityProperty.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Editjiraissue
Editjiraissue
ATLASSIAN_MCP_EDIT_JIRA_ISSUEEdit an existing Jira issue. Custom fields go in additional_fields: keyed by field name, values are resolved automatically (user fields take accountIds); keyed by customfield_* ID, pass the value in Jira’s format. Every field is set, not appended: send the full list for labels, components and other multi-value fields. Change status or move to a sprint with transitionJiraIssue, and convert Task↔Sub-task with convertJiraIssueHierarchy. Empty description or environment with "". When editing a body that holds inline media, use contentFormat: html, or the media is dropped. Reorder on a board with rankBeforeIssue or rankAfterIssue; fields are saved first, so a failed reorder leaves the edit applied and returns ranking.ranked: false. The response shows only getJiraIssue’s default fields, so other fields you set are not echoed back.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Enableconfluencepubliclink
Enableconfluencepubliclink
ATLASSIAN_MCP_ENABLE_CONFLUENCE_PUBLIC_LINKEnable the external public link (anonymous share) for a Confluence pageInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Exportconfluencecontent
Exportconfluencecontent
ATLASSIAN_MCP_EXPORT_CONFLUENCE_CONTENTExport Confluence content as PDF or Word and return a download linkInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getaccessibleatlassianresources
Getaccessibleatlassianresources
ATLASSIAN_MCP_GET_ACCESSIBLE_ATLASSIAN_RESOURCESReturns the cloudId(s) available to the current userGetartifact
Getartifact
ATLASSIAN_MCP_GET_ARTIFACTGet metadata for an artifact by ID.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getassetsobject
Getassetsobject
ATLASSIAN_MCP_GET_ASSETS_OBJECTGet an Assets object by ID from the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getassetsobjectsbyid
Getassetsobjectsbyid
ATLASSIAN_MCP_GET_ASSETS_OBJECTS_BY_IDGet one or more Assets objects by ID from the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getassetsobjectschema
Getassetsobjectschema
ATLASSIAN_MCP_GET_ASSETS_OBJECT_SCHEMAGet one or more Assets object schemas by ID from the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getassetsobjecttype
Getassetsobjecttype
ATLASSIAN_MCP_GET_ASSETS_OBJECT_TYPEGet one or more Assets object types by ID from the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getassetsserviceobjectsbyid
Getassetsserviceobjectsbyid
ATLASSIAN_MCP_GET_ASSETS_SERVICE_OBJECTS_BY_IDGet one or more Assets service objects by ID from the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getcapacityplanallocations
Getcapacityplanallocations
ATLASSIAN_MCP_GET_CAPACITY_PLAN_ALLOCATIONSFind who is allocated to what work in Individual Capacity Planning, across ALL capacity plans - not scoped to a single plan. USE WHEN the user asks what someone is working on, who is working on an issue or project, whether a contributor is on a given work item, how loaded or available someone is, or how staffed a work item is. People are contributors, not assignees: allocation is independent of the Jira assignee field - use the Jira tools for assignees. Pass contributorDataIds for the work those people are allocated to, workDataIds for who is allocated to those items, or both to check one contributor against one item. At least one is required; resolve non-project work ARIs with listCapacityPlanNonProjectWork rather than fabricating them. Returns contributor-work associations with contributor and work names/keys. expand adds ‘contributions’ (allocated value per period), ‘contributorAggregations’ (a contributor’s total contribution AND availability across all plans - “how loaded is X”) and ‘workAggregations’ (total effort across all contributors on an item - “how staffed is PROJ-42”); both aggregations come back as separate top-level objects, and all three can be combined. IMPORTANT: contributionStartDate and contributionEndDate do NOT filter which associations are returned - they only set the window for the contribution and aggregation figures. To check whether a contributor is allocated during a period, request contributions for that window and see whether any come back. A baseline 40-hour working week means 5 days, 40 hours and 100 percent are the same amount - say so when reporting days or percentages. PAGINATION - YOU MUST CHECK THIS: results come back one page at a time. When the response has pageInfo.hasNextPage = true the allocations list is INCOMPLETE - more contributor-work associations exist that are not in this response. Do NOT draw conclusions (totals, counts, “that’s the whole team”, “nobody else is allocated”) from a single page when hasNextPage is true. To get the rest, call again with after set to pageInfo.endCursor and repeat until hasNextPage = false, then combine every page before answering. For a broad “everyone’s allocations for this range” request, keep paging until hasNextPage = false.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getcodefile
Getcodefile
ATLASSIAN_MCP_GET_CODE_FILERead the full contents of a single file in a connected source-control repository at a specific commit. Use this to inspect a file surfaced by searchCode: pass matchedFiles[].workspace, repo, path, and version (as commitHash) from that result. Returns the file’s text and a link to it.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluenceapproval
Getconfluenceapproval
ATLASSIAN_MCP_GET_CONFLUENCE_APPROVALGet Confluence page approval availability, approval status, reviewers, and optional progress or history. Omit contentId to list the pages awaiting the current user’s approval decision. For a general page status request, also call getConfluenceContentStatus; for approval status, use this tool only.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluenceattachment
Getconfluenceattachment
ATLASSIAN_MCP_GET_CONFLUENCE_ATTACHMENTGet Confluence attachment metadata by attachment IDInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecomment
Getconfluencecomment
ATLASSIAN_MCP_GET_CONFLUENCE_COMMENTGet a single Confluence comment by IDInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontent
Getconfluencecontent
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENTREQUIRED: Supply at least one content locator: content_id or content_url. Read any Confluence content (page, blog, live doc, comment, whiteboard, embed, database, folder).Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentanalytics
Getconfluencecontentanalytics
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_ANALYTICSReturn per-user Confluence viewer rows for one supported content item (page, live doc, or blog post), including each viewer’s engagement category, the latest version viewed, and last viewed time. Always present results as a horizontal table, even for one viewer, with exactly these columns in this order: People and agents, Engagement, Latest version viewed, Last viewed, Views. When dates are omitted, Confluence uses the same default range as the Viewers table. Use the relative last-viewed value, such as “7 minutes ago”, instead of the exact timestamp. For an AGENT row with both names, present People and agents as “<displayName> with <relatedUserDisplayName>”. Keep the Engagement column; if engagement is missing, put ”-” rather than inventing another category.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentancestors
Getconfluencecontentancestors
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_ANCESTORSList the ancestor chain (parent, grandparent, …) of a Confluence content entityInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentdescendants
Getconfluencecontentdescendants
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_DESCENDANTSList descendants of a Confluence content entity (page, folder, whiteboard, database, embed, or slide)Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentpermissions
Getconfluencecontentpermissions
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_PERMISSIONSLists the explicit content-level permission grants on a single Confluence content entity. Each grant pairs an operation (read or update) with a principal (a user or a group). Optionally filter by operation, principal-type, or principal-id, and paginate with cursor and limit.Use this to audit who has been granted read or update access before adding, replacing, or removing grants. To read the higher-level restriction state (OPEN / EDIT_RESTRICTED / VIEW_RESTRICTED), use getConfluenceContentRestrictionState instead.Specific access rows: read = Can view and update = Can edit (which already includes view). Each principal has one level: read, update, or none. These grants add principal access; they do not restrict other people or change General access. General access is controlled by the restriction state, not direct grants.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentrestrictionstate
Getconfluencecontentrestrictionstate
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_RESTRICTION_STATEReads General access for a single Confluence content entity. The restriction states are: OPEN — “Open, Anyone in this space can edit”. EDIT_RESTRICTED — “Open, Anyone in this space can view”; only Specific access update principals can edit. VIEW_RESTRICTED — “Restricted, Only specific people can view or edit”; Specific access read/update grants determine access.Use this for a quick read of the overall restriction posture; use getConfluenceContentPermissions to enumerate the individual user/group grants.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentstatus
Getconfluencecontentstatus
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_STATUSRead the content state (status) of a Confluence page or blog postInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencecontentversion
Getconfluencecontentversion
ATLASSIAN_MCP_GET_CONFLUENCE_CONTENT_VERSIONGet one historical version of a Confluence page, live doc, or blog postInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencemauiapp
Getconfluencemauiapp
ATLASSIAN_MCP_GET_CONFLUENCE_MAUI_APPRetrieve the source and metadata for a Maui app owned by a Confluence page.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencepersonalspace
Getconfluencepersonalspace
ATLASSIAN_MCP_GET_CONFLUENCE_PERSONAL_SPACEGet the current user’s Confluence personal spaceInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencepubliclinkstatus
Getconfluencepubliclinkstatus
ATLASSIAN_MCP_GET_CONFLUENCE_PUBLIC_LINK_STATUSGet the external public-link (anonymous share) status of a Confluence pageInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencereactions
Getconfluencereactions
ATLASSIAN_MCP_GET_CONFLUENCE_REACTIONSGet emoji reactions on Confluence contentInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencespace
Getconfluencespace
ATLASSIAN_MCP_GET_CONFLUENCE_SPACEGet one Confluence space by id or key, including enabled content types, optional labels, and instructions when configured. Reuse the result for the same cloudId and space during the current task instead of reading the space before every write. If spaceInstructions is omitted, no instructions are configured; normal authoring does not require a separate getConfluenceSpaceInstructions call.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencespaceinstructions
Getconfluencespaceinstructions
ATLASSIAN_MCP_GET_CONFLUENCE_SPACE_INSTRUCTIONSGet the space instructions for a Confluence spaceInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencetask
Getconfluencetask
ATLASSIAN_MCP_GET_CONFLUENCE_TASKGet a single Confluence inline task by its IDInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getconfluencetemplate
Getconfluencetemplate
ATLASSIAN_MCP_GET_CONFLUENCE_TEMPLATEGet a Confluence template bodyInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getcontentformatguide
Getcontentformatguide
ATLASSIAN_MCP_GET_CONTENT_FORMAT_GUIDEGet the content-format guide for authoring a rich content body or constructing a Confluence Remix prompt. Pass toolName to receive the canonical guidance for that operation. For generic Confluence content writes, pass the content-specific key (for example createConfluencePage, not createConfluenceContent). For Remix, pass the exact create/edit operation you are about to call. Use this before authoring or editing rich Confluence content, constructing a Remix generation/edit prompt, or writing a Jira issue/comment body in HTML. First call with only toolName; if the returned guidance references follow-up documents, call this operation again with the same toolName and reference set to a single referenced path to load that additional guidance. Fetch one document per call.Input Parameters
whiteboard. For generic Confluence content authoring/editing, this is NOT createConfluenceContent or updateConfluenceContent; use the create/update key for the target content type: createConfluencePage/updateConfluencePage (pages, blog posts, live docs), createConfluenceWhiteboard/updateConfluenceWhiteboard, or createConfluenceDatabase/updateConfluenceDatabase, or addConfluenceContentSuggestions for content suggestions. For Remix prompt construction, use the exact operation: createConfluenceInfographicForPage, editConfluenceInfographicForPage, createConfluenceMauiApp, or editConfluenceMauiApp. For authoring Jira issue/comment bodies in HTML (contentFormat: html) the value is editJiraIssue or addOrEditJiraIssueComment. The response lists the supported values if an unknown one is passed.Getfocusarea
Getfocusarea
ATLASSIAN_MCP_GET_FOCUS_AREAGet a focus area by identifier, with optional expansions. Use when the exact focus area UUID, ARI, or page URL is known. For text search or listing, use searchFocusAreas instead. Optional include expansions cover about content, the current user’s latest draft status update, status updates, sub-focus areas, linked goals, linked work, and custom field values.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getfocusareatypes
Getfocusareatypes
ATLASSIAN_MCP_GET_FOCUS_AREA_TYPESGet the configured Focus area type hierarchy for a workspace. USE WHEN the user needs the valid Focus area types for a site — for example before creating a Focus area, or to understand hierarchy levels and parent type relationships. Returns each type with identifiers, hierarchy level, parent hierarchy references, and associated Focus area counts.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getgoal
Getgoal
ATLASSIAN_MCP_GET_GOALRetrieve one Atlassian Goal by its exact Goal ARI or key, with optional related details.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getgoaltypes
Getgoaltypes
ATLASSIAN_MCP_GET_GOAL_TYPESGet the Goal Types available in an Atlassian site for creating Goals and Success Measures.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getgoalupdate
Getgoalupdate
ATLASSIAN_MCP_GET_GOAL_UPDATERetrieve one Atlassian Goal update by its exact Goal Update ARI, with optional related details.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getgraphcontext
Getgraphcontext
ATLASSIAN_MCP_GET_GRAPH_CONTEXTRetrieves connected context from Teamwork Graph for any Atlassian entity. Returns all relationships and linked objects within one traversal – including cross-product and third-party connections. Use when the answer requires connections between entities, not just a single entity’s fields.Supported entry points:Jira: issues, projects, sprints, versions, commentsConfluence: pages, blogposts, whiteboards, databases, spacesGoals, Projects, Focus Areas, Tags and updatesPeople: users, teams, organisationsDevOps: PRs, repos, deployments, services, builds, designsLoom: videos, meetingsCompass: componentsAssets: objectsIncidents, conversations, calendar events, external documentsAfter calling this tool, call getGraphObject on returned ARIs to get full content.The utilisation of this tool may consume up to 10 Rovo Credits. If the user or organization does not have any Rovo Credits available, the tool call will fail.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getgraphobject
Getgraphobject
ATLASSIAN_MCP_GET_GRAPH_OBJECTFetches the entire available data for one or more objects (Atlassian or third-party) using their ARIs or URLs. Use for the objects gathered from getGraphContext tool.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiraboardconfig
Getjiraboardconfig
ATLASSIAN_MCP_GET_JIRA_BOARD_CONFIGReturns the configuration for a Jira board; filter, column layout, and each column’s mapped statuses with their id, name and category. For the issues on the board, use getJiraBoardIssueData.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiraboardissuedata
Getjiraboardissuedata
ATLASSIAN_MCP_GET_JIRA_BOARD_ISSUE_DATAGet the issues on a Jira board, its backlog, or all of them, with optional count and JQL filtering. For an issue search that is not scoped to a board, use searchJiraIssuesUsingJql. For one sprint’s issues with progress metrics, use getJiraBoardSprintData — on a Scrum board dataset “board” spans current and future sprints, not just the active one.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiraboardsprintdata
Getjiraboardsprintdata
ATLASSIAN_MCP_GET_JIRA_BOARD_SPRINT_DATAResolve a Jira board plus its sprint data in one call. Supports board lookup by name, sprint lookup by name, and defaults to the active sprint when sprintId and sprintName are omitted. Returns the board, the resolved sprint, all sprint metadata on that board, and — unless includeIssues is false — the sprint’s issues with computed focus and progress slices such as assigned-to-me and at-risk items. If the requested sprint name or ID is not found, the tool returns the resolved board plus the available sprint names to help the agent repair the request. To only list a board’s sprints or filter them by state, use listJiraBoardSprints. For board or backlog issues that are not scoped to a single sprint, use getJiraBoardIssueData.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiracurrentuser
Getjiracurrentuser
ATLASSIAN_MCP_GET_JIRA_CURRENT_USERGet the calling user’s own Jira profile. Use it to turn “me” or “my” into an accountId, and to read the user’s time zone before resolving relative dates. For a JQL search, skip this tool and write assignee = currentUser() in the query instead. For anyone else use lookupJiraAccountId or getJiraUser.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiraentityproperty
Getjiraentityproperty
ATLASSIAN_MCP_GET_JIRA_ENTITY_PROPERTYReturns a single property (technical key/value store) from a specific Jira entity (issue, issueComment, issueWorklog, dashboardItem, user), or lists all its property keys when propertyKey is omitted. With propertyKey it returns {key, value} with the stored JSON, null-valued fields generally dropped except assignee; without one, {keys: […]} — key names only, no values.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiraissue
Getjiraissue
ATLASSIAN_MCP_GET_JIRA_ISSUEGet a Jira or JSM issue by key or ID. Use for one known issue; use searchJiraIssuesUsingJql to find or list many issues. Reports how many comments an issue has, not the comments themselves — for those use listJiraIssueComments. View “evidence” also returns the issue’s links to other issues.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.properties query param, repeated per key). Omit unless you rely on app-specific issue properties.fields is interpreted as a Jira field key (e.g. “summary”, “description”) instead of a field id. Matches the Jira REST fieldsByKeys query parameter. Ignored when fields is omitted (default field list uses ids).Getjiraissuetypemetawithfields
Getjiraissuetypemetawithfields
ATLASSIAN_MCP_GET_JIRA_ISSUE_TYPE_META_WITH_FIELDSReturns the schema and field metadata for a specific issue type in a project, useful for creating issues with correct fields. Get issueTypeId from listJiraProjectIssueTypesMetadata first. Each entry in fields gives the fieldId, its name, whether it is required, schema.type — with schema.items naming the element type on arrays — and allowedValues on fields whose value must come from a predefined list. Only required fields are returned unless you pass requiredFieldsOnly: false.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjiraprojectversions
Getjiraprojectversions
ATLASSIAN_MCP_GET_JIRA_PROJECT_VERSIONSList a Jira project’s releases/versions (pass projectIdOrKey), or fetch a single version (pass versionId) — provide exactly one. Results come back in a paginated envelope (values[]); in single-version mode the list-only inputs (startAt, maxResults, query, status, orderBy) are ignored. Optionally set include to add the “driver” and/or “approvers” to every version returned, but leave it unset unless the user explicitly asks for them. To create, update, or release a version, use manageJiraProjectVersion instead.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjirauser
Getjirauser
ATLASSIAN_MCP_GET_JIRA_USERGet a Jira user’s profile by account ID, including time zone, locale and active status, plus groups and application roles when asked for via expand. If you do not have the accountId, use lookupJiraAccountId or listJiraIssueAssignableUsers first. For the calling user’s own profile use getJiraCurrentUser instead.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmagentavailability
Getjsmagentavailability
ATLASSIAN_MCP_GET_JSM_AGENT_AVAILABILITYRead Jira Service Management Workforce Management availability for agents in a service project. Workforce Management uses agent availability alongside capacity, skills, and shift coverage when routing work. Returns project-level availability counts by default. Set includeSelf to read the authenticated agent’s project-scoped status, or set includeAgents to true to list individual agents, statuses, teams, or paginated results. This is read-only; it does not assign work or change availability. Output fields include summary for project counts, agents[] for individual agents, and myAvailability for includeSelf; use those names when selecting responseFields.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmopsalerts
Getjsmopsalerts
ATLASSIAN_MCP_GET_JSM_OPS_ALERTSGet one Jira Service Management Operations alert by ID or alias, or list and search alerts with optional query, time window, and pagination. If multiple selectors are supplied, id takes precedence, then alias, otherwise list/search inputs are used.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmopsscheduleinfo
Getjsmopsscheduleinfo
ATLASSIAN_MCP_GET_JSM_OPS_SCHEDULE_INFOGet Jira Service Management Operations schedule information: list schedules, get a specific schedule by ID, or retrieve current or next on-call responders for a schedule. Use action=“schedule” to list schedules or get schedule details. Use action=“oncall” with scheduleId to get on-call responders.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmopsteaminfo
Getjsmopsteaminfo
ATLASSIAN_MCP_GET_JSM_OPS_TEAM_INFOGet Jira Service Management Operations team information: list all teams or get escalation policies for a specific team. Use action=“teams” to retrieve a list of all teams based on the user’s role. Use action=“escalations” to list escalation policies for a team and obtain escalationId values used by updateJsmOpsAlert.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmrequest
Getjsmrequest
ATLASSIAN_MCP_GET_JSM_REQUESTGet details and the current customer-facing state of an existing Jira Service Management (JSM) customer request by issue key or ID. Returns requestType (request type), serviceDesk (service desk), reporter (requester), requestParticipants (participants), requestFields (request fields), status, agentUrl (request link), and nextActions. Use these exact output names when selecting responseFields. Supports summary and detail views. For editable fields on the underlying Jira issue, call getJiraIssue with includeEditableFields=true. Use this read-only tool to understand a request; use request action-metadata tools for transitions, editable fields, and valid options. Approvals are returned only when explicitly requested.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmrequestactionmetadata
Getjsmrequestactionmetadata
ATLASSIAN_MCP_GET_JSM_REQUEST_ACTION_METADATADiscover customer-visible request-portal actions for an existing Jira Service Management request before a follow-up write. Returns compact customer transitions by default and can explicitly include request type fields metadata or approvals. Uses JSM customer transitions, not Jira workflow transitions, and never mutates the request. The output field is customerTransitions (an array of id, name, and description); select customerTransitions, not transitions.*, when using responseFields.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmrequestcreationoptions
Getjsmrequestcreationoptions
ATLASSIAN_MCP_GET_JSM_REQUEST_CREATION_OPTIONSPrepare creation of a Jira Service Management customer-request work item for a project. Use this first to return its service desk and available request types. Select a request type, then use getJsmRequestTypeFields before createJsmRequest. Requires projectKey, the key of an accessible JSM service desk project (for example ITSM), not a numeric project ID. JSM request types are not Jira issue types.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmrequestresolverplans
Getjsmrequestresolverplans
ATLASSIAN_MCP_GET_JSM_REQUEST_RESOLVER_PLANSRetrieve a concise snapshot of Request Resolver plans for selected Jira Service Management requests by issue key or ID. Returns one result per distinct input in first-selection order, containing loading state, plan status, readable steps, runbook links or an error. Ready plans remain available when other requests are loading or fail. Excludes internal IDs, sources and reasoning. isLoading can mean generating or executing; a missing plan alone does not imply loading. Requires Jira read access to resolve ticket and project IDs. Does not approve or execute plans.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getjsmrequesttypefields
Getjsmrequesttypefields
ATLASSIAN_MCP_GET_JSM_REQUEST_TYPE_FIELDSGet field IDs, required flags, and allowed values for selected Jira Service Management work-item request type. Use getJsmRequestCreationOptions first, then build createJsmRequest.requestFieldValues from these fields.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getloomvideo
Getloomvideo
ATLASSIAN_MCP_GET_LOOM_VIDEOReads a Loom video’s core metadata and optionally its transcript, comments, AI agent briefs, AI-extracted meeting action items, or attached links in one call via the expand input. USE WHEN the user asks about a specific Loom video — its title, description, duration, owner, view/comment/reaction counts, what was said in it (pass expand: [“transcript”]), what feedback or comments people left on it (pass expand: [“comments”]), what the AI summarised as key points (pass expand: [“agentBriefs”]), or what follow-up tasks or action items the AI extracted from a meeting recording (pass expand: [“meetingActionItems”]), or which links are attached to it (pass expand: [“links”]). DO NOT USE to get the downloadable MP4 file — use getLoomVideoDownloadUrl for that. To find a video’s ARI first, use listLoomVideos or listLoomVideosSharedWithMe.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getloomvideodownloadurl
Getloomvideodownloadurl
ATLASSIAN_MCP_GET_LOOM_VIDEO_DOWNLOAD_URLGet a time-limited signed URL to download the actual MP4 file of a Loom video. This is the tool to use when the user wants the video file itself (to download, re-upload, or process), not its transcript or metadata (use getLoomVideo for those). MP4 generation is asynchronous: the response includes a status and, when not yet ready, a retryAfterSeconds hint — poll this tool until status is READY, then use the returned url before expiresAt. Identify the video by ARI or share URL.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getmywork
Getmywork
ATLASSIAN_MCP_GET_MY_WORKRead the signed-in user’s recent Jira, Confluence, Goals, Projects and Loom activity on one site. Returns things worked on or viewed, newest activity first, with titles, URLs and activity timestamps. Uses Activity Platform with no enriched graph-context or Cypher calls. Assigned work is not part of this feed. The lookback is configurable and defaults to 90 days.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getproject
Getproject
ATLASSIAN_MCP_GET_PROJECTRetrieve one Atlassian Project by its exact Project ARI or key, with optional related details.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getprojectupdate
Getprojectupdate
ATLASSIAN_MCP_GET_PROJECT_UPDATERetrieve one Atlassian Project update by its exact Project Update ARI, with optional related details.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Gettalentfields
Gettalentfields
ATLASSIAN_MCP_GET_TALENT_FIELDSDiscover the workspace’s queryable Talent fields, or resolve the valid filter values for a specific field. Call BEFORE authoring RQL: with no fieldId it lists the available field IDs (including custom fields), grouped by what they describe (position, worker, team, skill, focus area, focus area type, proposal, proposed movement and view fields), excluding hidden fields; with a fieldId it returns that field’s valid values, paginated. Field IDs and values are workspace-specific and must not be guessed.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Gettalentgroupmetrics
Gettalentgroupmetrics
ATLASSIAN_MCP_GET_TALENT_GROUP_METRICSAggregate Talent positions into COUNTS grouped by one to four position field IDs — headcount by country, by status, by level, by job family, by manager, or any nesting of those. Returns only the grouped counts and their field values, never the positions themselves: when the underlying list is wanted use searchTalentPositions, and when the breakdown is by reporting line or focus area use getTalentPositionsByEntity, which groups by entity rather than by field. Grouping field IDs are workspace-specific, must be groupable, and must not be guessed — call getTalentFields to resolve them. The common built-ins are positionCountry, positionStatus, positionLevel, positionRole, positionJobFamily, positionJobTitle, positionEmploymentType, positionManager and team.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Gettalentposition
Gettalentposition
ATLASSIAN_MCP_GET_TALENT_POSITIONRead a single Talent position by its ARI, returning its selected position field values and, optionally, field values for the worker filling it. Use this only when you already have the position ARI: take it from a searchTalentPositions result’s id, or from a getTalentPositionsByEntity result’s entityId — NOT that tool’s id, which is a connection node identifier and is not accepted here. To FIND a position rather than read a known one, use searchTalentPositions. To identify the worker filling the position, request positionWorker in positionFieldIdIsIn — that yields the worker’s id, name and accountId. Do not rely on workerFieldIdIsIn for more than that: the backing action accepts it but does not currently return the requested worker field values, so attributes like skills or email will not come back here. Field IDs are workspace-specific and must not be guessed — call getTalentFields to resolve them. Common position built-ins are positionJobTitle, positionCountry, positionLevel, positionStatus, positionManager and positionWorker.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Gettalentpositionsbyentity
Gettalentpositionsbyentity
ATLASSIAN_MCP_GET_TALENT_POSITIONS_BY_ENTITYList the Talent positions attached to an entity — the direct reports of a manager position (entity=position with that manager’s ARI as fieldValue), or the positions rolled up to a focus area (entity=focusArea). This is the tool for walking the org chart and for breaking staffing down across focus areas or reporting lines, because it is the only one that can scope to those entities; it returns the underlying positions, paginated forward with after + endCursor. The two entities are scoped by DIFFERENT inputs: entity=position scopes with fieldValue, entity=focusArea scopes with rql. fieldValue is ignored when entity=focusArea, so a focus area passed there returns every row unfiltered — use rql “focusArea = ‘<focus area ARI>’” for that one area, or rql “focusAreaParent = ‘<focus area ARI>’” for its direct children. Use getTalentGroupMetrics INSTEAD when you want counts grouped by a position FIELD and not the positions themselves, and searchTalentPositions INSTEAD for a flat attribute filter that is not entity-scoped. Each returned position carries both an entityId and an id: entityId is the position identifier to pass to getTalentPosition, while id identifies the row within this connection and is NOT accepted as a position ARI. Field IDs and RQL values are workspace-specific and must not be guessed — resolve them with getTalentFields; focusArea and focusAreaParent are standard field IDs and are safe to use exactly as written. Useful built-ins are positionWorker, team, positionJobTitle, positionRole, positionStatus, aiMonthlyUsageCostSelfTotal and aiMonthlyUsageTokenSelfTotal.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Gettalentuser
Gettalentuser
ATLASSIAN_MCP_GET_TALENT_USERResolve the calling user’s own place in the Talent workspace: their position entity ID, their manager’s position entity ID, and their role. Call this FIRST to anchor any self-referential request (“my team”, “my reports”, “who do I report to”) before using the other Talent tools. Note this returns entity IDs, not position ARIs — to get a position ARI for getTalentPosition or getTalentPositionsByEntity, look the position up with searchTalentPositions.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Getteam
Getteam
ATLASSIAN_MCP_GET_TEAMGet core metadata for one Atlassian team. Optionally expand any unique subset of members and hierarchy; each expansion supports its own cursor.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Linktofocusarea
Linktofocusarea
ATLASSIAN_MCP_LINK_TO_FOCUS_AREALink one of either goals, work items, or sub-focus areas to a focus area. Add exactly one connection type per call. Prefer identifiers from a prior lookup, or call a lookup to get them; do not fabricate ARIs. Useful lookup helpers: getGoal for goal ARIs, getJiraIssue for Jira work ARIs, and getProject for Atlassian project ARIs. In this tool, WORK_ITEM means one of the supported work ARI families: Jira/JPD issues or Atlassian projects. focusAreaIdentifier accepts a focus area UUID, ARI, or page URL. Linking GOAL or WORK_ITEM requires focusAreaIdentifier to be a focus area ARI; if only a UUID or URL is known, call getFocusArea and pass the returned ari. connection must specify exactly one type: GOAL with goalAris, WORK_ITEM with workAris, or FOCUS_AREA with focusAreaIdentifiers.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listartifacts
Listartifacts
ATLASSIAN_MCP_LIST_ARTIFACTSList artifacts created by the current user using cursor pagination.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listassetsobjectschemas
Listassetsobjectschemas
ATLASSIAN_MCP_LIST_ASSETS_OBJECT_SCHEMASList all Assets object schemas in the selected site’s workspace.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listassetsobjecttypeattributes
Listassetsobjecttypeattributes
ATLASSIAN_MCP_LIST_ASSETS_OBJECT_TYPE_ATTRIBUTESList attributes for one or more Assets object types in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listcapacityplannonprojectwork
Listcapacityplannonprojectwork
ATLASSIAN_MCP_LIST_CAPACITY_PLAN_NON_PROJECT_WORKSearch the non-project work items on a site. “Non-project work” is the user-facing name for a custom contribution target - the buckets of time that are not a Jira issue or an Atlas project, such as Leave, Run the Business (RtB), on-call, or training. Non-project work is an entity that belongs to Capacity Planning: it is defined and stored in Capacity Planning itself, and exists nowhere else in Atlassian. Capacity can be allocated to three kinds of work item - Jira issues, Atlas projects, and non-project work - and only the third is owned by Capacity Planning, so it can only be found through this tool. There is no Jira or Confluence equivalent to look up instead. USE WHEN you need the ARI of a non-project work item before allocating someone to it, or when the user asks what non-project work categories exist. The returned ari is what feeds workId on updateCapacityPlanAllocations and workDataIds on getCapacityPlanAllocations - resolve it here rather than fabricating one. The query is case-insensitive and matches on name; omit it to list everything. Paginate with first/after or last/before.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listcodedirectory
Listcodedirectory
ATLASSIAN_MCP_LIST_CODE_DIRECTORYList the files and subdirectories under a path in a connected source-control repository at a specific commit. Paginated — pass the returned nextPage cursor to fetch the next page. Use it to browse a repository’s structure discovered via searchCode.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluenceattachments
Listconfluenceattachments
ATLASSIAN_MCP_LIST_CONFLUENCE_ATTACHMENTSList attachment metadata for a Confluence content itemInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluencecomments
Listconfluencecomments
ATLASSIAN_MCP_LIST_CONFLUENCE_COMMENTSList comments on a Confluence page or blog postInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluencecontent
Listconfluencecontent
ATLASSIAN_MCP_LIST_CONFLUENCE_CONTENTList Confluence content of one type within a single space (page, blog post, live doc, whiteboard, database, embed, smart link, folder, slide)Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluencecontentversions
Listconfluencecontentversions
ATLASSIAN_MCP_LIST_CONFLUENCE_CONTENT_VERSIONSList version history for a Confluence page, live doc, or blog post, newest firstInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluencespaces
Listconfluencespaces
ATLASSIAN_MCP_LIST_CONFLUENCE_SPACESList Confluence spaces accessible to the callerInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluencetasks
Listconfluencetasks
ATLASSIAN_MCP_LIST_CONFLUENCE_TASKSList Confluence inline tasks, optionally scoped to a page or blog post and filtered by statusInput Parameters
complete, incomplete. Omit to include both.execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listconfluencetemplates
Listconfluencetemplates
ATLASSIAN_MCP_LIST_CONFLUENCE_TEMPLATESList Confluence templates and blueprintsInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraboards
Listjiraboards
ATLASSIAN_MCP_LIST_JIRA_BOARDSList Jira boards visible to the current user. Use it to get board IDs for getJiraBoardIssueData, getJiraBoardConfig and listJiraBoardSprints; getJiraBoardSprintData can resolve a board by name directly. Returns each board’s ID, name, type, edit/privacy/favourite flags and location. Page with startAt until isLast is true. projectKeyOrId matches boards whose JQL references that project, not boards located in it. includePrivate appends private boards, but Jira omits their name and type.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraboardsprints
Listjiraboardsprints
ATLASSIAN_MCP_LIST_JIRA_BOARD_SPRINTSList a board’s sprints — past, active or upcoming — or resolve a sprint name to the numeric sprintId that transitionJiraIssue and manageJiraSprint take. Not needed before createJiraIssue, whose assignToSprint accepts a sprint name or “active” directly. For the active sprint plus its issues and progress in one call, use getJiraBoardSprintData.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiradashboards
Listjiradashboards
ATLASSIAN_MCP_LIST_JIRA_DASHBOARDSReturns Jira dashboards visible to the current user for discovery and linking workflows. Use this to find dashboard IDs, names, and links that can be shared or opened. This tool is intentionally lightweight and does not fetch dashboard gadget data. Page with startAt until isLast is true.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjirafilters
Listjirafilters
ATLASSIAN_MCP_LIST_JIRA_FILTERSSearch saved Jira filters visible to the current user, returning their IDs and JQL. To get the matching issues, run a filter’s jql through searchJiraIssuesUsingJql; to build a board, pass its id as createJiraBoard’s filterId. projectId finds filters shared with that project, not filters whose JQL mentions it.Input Parameters
id=10000&id=10001).execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissueassignableusers
Listjiraissueassignableusers
ATLASSIAN_MCP_LIST_JIRA_ISSUE_ASSIGNABLE_USERSList the users who can actually be assigned work in a project or on an issue. Filters by assign permission, which a plain name search does not, so prefer it when choosing an assignee for editJiraIssue or createJiraIssue.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissuechangelogs
Listjiraissuechangelogs
ATLASSIAN_MCP_LIST_JIRA_ISSUE_CHANGELOGSGet a Jira issue’s field-change history — field edits only — paginated oldest-first with no ordering options. For the current value or most recent change, read total (which counts entries, not items) and request startAt = max(0, total - your page size); for counts or patterns across the history, page from startAt 0. A field’s original value is in the first item that changed it; fields never changed leave no trace, and the log starts at the first edit, not at creation. On an item, from/to are IDs or raw values and are absent on text and array fields; fromString/toString are display text, and on array fields like labels each side is the complete set (space-joined, sorted) — diff the two sides, never read one as a delta. Jira omits from and fromString together when the field had no previous value, and to and toString together when it was cleared (so an assignee item with no to/toString is an unassignment). Match items on field, not position: order within an entry varies. Do not infer automation from author.accountType — a script running under a person’s token reads “atlassian”.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissuecomments
Listjiraissuecomments
ATLASSIAN_MCP_LIST_JIRA_ISSUE_COMMENTSGet a paginated list of comments for a Jira issue. Use this instead of getJiraIssue when an issue has many comments — getJiraIssue embeds at most 20 and cannot page them. Page with startAt until isLast is true; total is the full comment count. Each comment reports any visibility restriction on it and, on JSM, whether it is internal (jsdPublic: false) — check both before quoting or summarising a comment. Comments are returned as a flat list: a non-null parentId means the comment is a reply, and parentId identifies its root/parent comment. Group comments by parentId to reconstruct threads. Set reactionDetail when emoji reaction data is needed. For the issue’s own fields, use getJiraIssue.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissuelinktypes
Listjiraissuelinktypes
ATLASSIAN_MCP_LIST_JIRA_ISSUE_LINK_TYPESList the issue link types configured on this site, each with its name and its inward and outward wording (name “Blocks”, inward “is blocked by”, outward “blocks”). Call it before createJiraIssueLink, which takes the name, when the user has described a link by its inward/outward wording. Issue linking must be enabled site-wide; where it is turned off this operation and createJiraIssueLink both fail.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissueremoteissuelinks
Listjiraissueremoteissuelinks
ATLASSIAN_MCP_LIST_JIRA_ISSUE_REMOTE_ISSUE_LINKSList the Confluence pages and external URLs linked from an issue’s Web links section. These are not issue-to-issue links: for those call getJiraIssue with view “evidence”, which returns fields.issuelinks. Check here before calling createJiraIssueRemoteIssueLink: the same URL added twice becomes two separate links, and no operation removes one.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissuetransitions
Listjiraissuetransitions
ATLASSIAN_MCP_LIST_JIRA_ISSUE_TRANSITIONSList the workflow transitions this issue can take right now, for the calling user. Pass a transition’s id to transitionJiraIssue. A transition’s name and the status it leads to are separate fields: when the user names a target status, match the status a transition leads to, not the transition’s name. For every status a project defines, rather than this issue’s currently valid moves, use listJiraStatuses.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraissueworklogs
Listjiraissueworklogs
ATLASSIAN_MCP_LIST_JIRA_ISSUE_WORKLOGSGet a paginated list of worklogs (logged time) for a Jira issue. Ordered by worklog creation time, not by when the work started — so the last page is not the most recent work. To find recent work, filter with startedAfter/startedBefore, or read every page and sort by started.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraprojectcomponents
Listjiraprojectcomponents
ATLASSIAN_MCP_LIST_JIRA_PROJECT_COMPONENTSList a Jira project’s components with their ids, names, lead and assignee settings, and issueCount — 0 means no issues use a Jira component; Compass results list only components already linked to issues. realAssignee is who actually receives issues when the configured assignee cannot be used. Use it to find a valid component name before setting components on createJiraIssue or editJiraIssue.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraprojectissuetypesmetadata
Listjiraprojectissuetypesmetadata
ATLASSIAN_MCP_LIST_JIRA_PROJECT_ISSUE_TYPES_METADATAReturns all issue types available in a Jira project, useful for knowing which issue types can be created. Each entry gives the issue type’s id, name, description and subtask flag; pass that id as issueTypeId to getJiraIssueTypeMetaWithFields to get the type’s create fields. Page with startAt until it covers total.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjiraprojects
Listjiraprojects
ATLASSIAN_MCP_LIST_JIRA_PROJECTSFind the Jira projects the calling user can see — use it to resolve the projectKey that createJiraIssue requires, or the project a JQL search filters on. For a project’s releases use getJiraProjectVersions; for its statuses, use listJiraStatuses.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listjirastatuses
Listjirastatuses
ATLASSIAN_MCP_LIST_JIRA_STATUSESList the statuses a Jira issue can be in — for a project (per work type), for one status looked up by ID or name, or across the whole site by name or category. Takes a PROJECT key (or project ID), not an issue key. For what a specific issue can do right now, use listJiraIssueTransitions instead; a status existing in a project does not mean a given issue can move to it.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listloomfolders
Listloomfolders
ATLASSIAN_MCP_LIST_LOOM_FOLDERSList the folders in the current Loom workspace that a video can be moved into, returning each folder’s id, name, and parent space. Use this to discover a destination folder id before calling moveLoomVideoToFolder, or to pick a folderId for createLoomVideoUpload / publishLoomVideo. Pass query to filter folders by name; omit it to list all folders.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Listloomvideos
Listloomvideos
ATLASSIAN_MCP_LIST_LOOM_VIDEOSList the Loom videos you own (that you created), most recent first. This is a primary entry point for finding a video: it returns each video’s ARI, name, and description, which you can pass to getLoomVideo, getLoomVideoDownloadUrl, or any video action. Always scoped to the current user — there is no user parameter. Optionally filter by the video’s creation date with the ISO-8601 createdAtFrom / createdAtTo bounds, and paginate with limit / offset. To find videos other people shared with you, use listLoomVideosSharedWithMe.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Lookupjiraaccountid
Lookupjiraaccountid
ATLASSIAN_MCP_LOOKUP_JIRA_ACCOUNT_IDLook up a Jira user account ID by display name or email — skip it if you already have the accountId. Returns only accountId, displayName and active, plus emailAddress when profile visibility allows it; for time zone, locale, groups, or application roles, pass the accountId on to getJiraUser. To choose an assignee use listJiraIssueAssignableUsers instead, which returns only users who can be assigned.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Manageconfluenceapproval
Manageconfluenceapproval
ATLASSIAN_MCP_MANAGE_CONFLUENCE_APPROVALRequest, decide, cancel, clear, or update a Confluence page approval. Approvals support pages only, not live docs or blog posts.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Managejiraprojectversion
Managejiraprojectversion
ATLASSIAN_MCP_MANAGE_JIRA_PROJECT_VERSIONCreate, update, release, or archive a Jira project version (release or fix version). create returns the version id the other actions need. If release uses moveUnfixedIssuesTo, setting released: false later does not move those issues back. Otherwise release and archive change only the version, not its issues, and update can reverse either. To view or list versions, or read their release driver and approvers, use getJiraProjectVersions.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Managejirasprint
Managejirasprint
ATLASSIAN_MCP_MANAGE_JIRA_SPRINTCreate, add issues to, start, update, or close a Jira sprint; get a sprintId from listJiraBoardSprints. create returns the new sprint’s id, which every later action needs. update rewrites the whole sprint, so any of name, goal, startDate or endDate you omit is cleared — resend the ones to keep; start and close keep them. Closing is one-way. addIssues returns movedIssues, as does start when given issueIdsOrKeys; both add estimatedIssues, with the field each estimate was written to, when storyPoints are passed.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Moveconfluencecontent
Moveconfluencecontent
ATLASSIAN_MCP_MOVE_CONFLUENCE_CONTENTMove a Confluence page, whiteboard, database, folder, or embed to a new parent or sibling positionInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.targetId. One of: append (under targetId as a child), before (immediately before targetId as a sibling), after (immediately after targetId as a sibling).Moveloomvideotofolder
Moveloomvideotofolder
ATLASSIAN_MCP_MOVE_LOOM_VIDEO_TO_FOLDERMove a Loom video into a folder in the current workspace. Get a destination folder id from listLoomFolders (or createLoomFolder). Identify the video by ARI or share URL.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Publishartifact
Publishartifact
ATLASSIAN_MCP_PUBLISH_ARTIFACTStep 2 of 2 for uploading an artifact. Finalizes content whose bytes were already transferred via createArtifactsUpload (step 1), using the contentId from that step’s completionPayload. Only call after the upload has completed. Creates a new artifact, or publishes a new version by supplying an existing artifact ID. Save, preserve, or store AI-generated analysis, reports, dashboards, charts, visualizations, and HTML slide decks durably behind a persistent link. Returns that link, which does not by itself grant anyone access: use shareArtifact to let named users, groups, or teams open it.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Publishloomvideo
Publishloomvideo
ATLASSIAN_MCP_PUBLISH_LOOM_VIDEOStep 2 of 2 for uploading a new video to Loom. Finalizes a video whose bytes were already transferred via createLoomVideoUpload (step 1), using the keyPath and fileName from that step’s completionPayload. Only call this after the upload has completed. Returns the user-facing Loom share URL. Optionally place the video in a folder or space.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Queryassetsobjects
Queryassetsobjects
ATLASSIAN_MCP_QUERY_ASSETS_OBJECTSQuery Assets objects with generated AQL for one object type in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Queryassetsobjectschemaattributes
Queryassetsobjectschemaattributes
ATLASSIAN_MCP_QUERY_ASSETS_OBJECT_SCHEMA_ATTRIBUTESQuery attributes for one or more Assets object schemas in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Queryassetsobjectsusingaql
Queryassetsobjectsusingaql
ATLASSIAN_MCP_QUERY_ASSETS_OBJECTS_USING_AQLQuery Assets objects with raw or generated AQL in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Queryassetsobjecttypes
Queryassetsobjecttypes
ATLASSIAN_MCP_QUERY_ASSETS_OBJECT_TYPESQuery Assets object types by schema in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Queryassetsreferencetypes
Queryassetsreferencetypes
ATLASSIAN_MCP_QUERY_ASSETS_REFERENCE_TYPESQuery global or schema-scoped Assets reference types in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Recoverloomvideo
Recoverloomvideo
ATLASSIAN_MCP_RECOVER_LOOM_VIDEORecover a Loom video that failed to process, by initiating a recovery job to re-process it. Use this when a video is stuck or errored (for example isComplete is false in getLoomVideo). Identify the video by ARI or share URL.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Removeconfluencecontentpermissions
Removeconfluencecontentpermissions
ATLASSIAN_MCP_REMOVE_CONFLUENCE_CONTENT_PERMISSIONSRemoves content-level permission grants from a single Confluence content entity. Optionally narrow what is removed by operation, principal-type, and/or principal-id. Omitting all three filters clears ALL Specific access grants on the content. This does not change General access.This can revoke access. The server protects against the current user locking themselves out of their own content.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Reopenconfluencetask
Reopenconfluencetask
ATLASSIAN_MCP_REOPEN_CONFLUENCE_TASKReopen a completed Confluence inline task (mark it incomplete)Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Replaceconfluencecontentpermissions
Replaceconfluencecontentpermissions
ATLASSIAN_MCP_REPLACE_CONFLUENCE_CONTENT_PERMISSIONSReplaces ALL content-level permission grants on a single Confluence content entity with the supplied set. Grants not present in the request are removed, so this can revoke access — prefer addConfluenceContentPermissions when you only intend to add grants.Pass the full desired grant set via the permissions input, an array of objects shaped exactly like: [ { “operation”: “update”, “principals”: [ { “principalType”: “user”, “principalId”: “<atlassian-account-id>” }, { “principalType”: “group”, “principalId”: “<group-id>” } ] } ] Enums: operation is one of read | update; principalType is one of user | group. For a user, principalId is the Atlassian account ID; for a group, principalId is the group ID.operation read = can view, update = can edit (edit includes view). A principal has only ONE effective level, so listing a principal under read when they should keep editing leaves them view-only — list them under update to preserve edit. Never list the same principal under both operations. Replacing Specific access does not change General access. Because this REPLACES the whole set, always include yourself with update if the content is (or is becoming) EDIT_RESTRICTED / VIEW_RESTRICTED. The server protects against locking the current user out of their own content.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.operation (read | update) and a principals array. Each principal has a principalType (user | group) and a principalId (Atlassian account ID for a user, group ID for a group). Grants not listed here are removed. A principal must appear under only one operation across the entire request. Example: [{ “operation”: “update”, “principals”: [{ “principalType”: “group”, “principalId”: “<group-id>” }] }].Resolveconfluencecontentmacros
Resolveconfluencecontentmacros
ATLASSIAN_MCP_RESOLVE_CONFLUENCE_CONTENT_MACROSResolve supported Confluence macro wrappers into per-macro HTML displayed in Confluence web. Use after getConfluenceContent when a full document read returns wrappers instead of visible content, especially for Include Page, Excerpt Include, and Jira macros. Use the returned HTML bodies to supplement the base document; this operation does not reconstruct the full page.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Restoreconfluencecontentversion
Restoreconfluencecontentversion
ATLASSIAN_MCP_RESTORE_CONFLUENCE_CONTENT_VERSIONRestore an earlier version of a Confluence page, live doc, or blog post as a new latest versionInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Scancoderepo
Scancoderepo
ATLASSIAN_MCP_SCAN_CODE_REPOList the file paths in a connected source-control repository at a specific commit, optionally filtered by a glob or restricted to a subtree. Returns paths only, no file contents. Paginated — pass the returned nextCursor to fetch the next page.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Search
Search
ATLASSIAN_MCP_SEARCHSemantically search Jira, Confluence, and connected third-party content using Rovo Search. ALWAYS use this tool to search for Jira and Confluence content unless CQL or JQL is specified. The utilisation of this tool may consume up to 10 Rovo Credits. If the user or organization does not have any Rovo Credits available, the tool call will fail.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchassetsobjects
Searchassetsobjects
ATLASSIAN_MCP_SEARCH_ASSETS_OBJECTSSearch Assets objects by name or query-builder filters in the selected site.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchcode
Searchcode
ATLASSIAN_MCP_SEARCH_CODESearch source code across connected source-control providers using semantic, lexical, or hybrid matching. Returns matching files along with the specific code spans that matched.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchconfluence
Searchconfluence
ATLASSIAN_MCP_SEARCH_CONFLUENCESearch Confluence content with CQLInput Parameters
type = page AND space = "DEV", title ~ "onboarding" AND lastmodified > "2025-01-01", creator = currentUser() AND type IN (page, blogpost) ORDER BY lastmodified DESC.space, version, body.view, metadata.labels, ancestors. Use sparingly to avoid large responses.execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchfocusareas
Searchfocusareas
ATLASSIAN_MCP_SEARCH_FOCUS_AREASSearch focus areas using text and structured filters with optional pagination and sorting. Omitting query and filters lists/browses focus areas. Exact lookup by ARI, UUID, or URL should use getFocusArea instead. getFocusArea also returns more detail per focus area than search results do — startDate, archived/draft/starred/watching flags, created and updated timestamps, and direct child focus areas — so follow up with it once a specific focus area is identified. Set include.aboutContent to true to fetch about content, and/or pass include.statusUpdates for latest status updates per result. Paginate with first/after using pageInfo.endCursor. Custom field filtering is supported through filters.customFields (resolve field searchKeys and select option UUIDs with getFocusAreaCustomFields first); filtering for focus areas where a custom field has no value is not supported — do not retry with other operators to express it.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchgoals
Searchgoals
ATLASSIAN_MCP_SEARCH_GOALSFind Atlassian Goals by text and structured filters.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchjiraissuesusingjql
Searchjiraissuesusingjql
ATLASSIAN_MCP_SEARCH_JIRA_ISSUES_USING_JQLSearch for Jira issues using JQL, with an optional approximate count. Use view: “evidence” to fetch and map custom fields. Page with nextPageToken until isLast is true. For one known issue, use getJiraIssue. JQL only returns issues; inferring anything else from issue rows is silently incomplete. Use the purpose-built operation for sprints, boards, board config, field history, worklogs, releases, accountIds, issue types, projects and statuses.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchjsmrequests
Searchjsmrequests
ATLASSIAN_MCP_SEARCH_JSM_REQUESTSSearch one bounded page of caller-visible Jira Service Management requests. Use JQL for project, request type, assignee, status, approval, text, due-date, and ordering filters. Use this tool when JSM requests, issues, or work items need your attention, when you need urgency signals from SLA state or sentiment, or when you need to identify auto-resolvable work items after approval. Returns summary, status, assignee, request type, sentiment, SLA state, card display data (issue-type icon, status category, assignee and requester avatars), URLs, and compact resolver-plan availability. This tool does not return full request details or plan steps. When the upstream request search ranks rows, it preserves the total score, each score component, and evidence so clients can render and explain urgency consistently.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchprojects
Searchprojects
ATLASSIAN_MCP_SEARCH_PROJECTSFind Atlassian Projects by text and structured filters.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchtalentpositions
Searchtalentpositions
ATLASSIAN_MCP_SEARCH_TALENT_POSITIONSSearch Talent positions by their own attributes using an RQL filter, returning a paginated list of positions with their requested field values (each position’s ARI is the id, so this is how you obtain ARIs for getTalentPosition). Use this for flat attribute filters — job title, country, level, status, job family, tenure. Use getTalentPositionsByEntity INSTEAD when scoping to a reporting line or a focus area, and getTalentGroupMetrics INSTEAD when you only need counts rather than the positions themselves. RQL field IDs and their valid values are workspace-specific and must not be guessed — call getTalentFields to resolve them. The common built-ins are positionJobTitle, positionCountry, positionLevel, positionStatus, positionRole, positionManager, positionTenure, positionJobFamily, positionEmploymentType, positionWorker and team; for anything else, or for a field’s valid values, go through getTalentFields. If a filter returns nothing, suspect the field ID or its value and check it with getTalentFields rather than adding more filters.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Searchteams
Searchteams
ATLASSIAN_MCP_SEARCH_TEAMSSearch Atlassian teams by name with cursor pagination. Core team fields are returned by default; pass expand [“members”] to include a separately paginated member summary for each team.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Setconfluencecontentrestrictionstate
Setconfluencecontentrestrictionstate
ATLASSIAN_MCP_SET_CONFLUENCE_CONTENT_RESTRICTION_STATESets the high-level restriction state for a single Confluence content entity. Provide state as one of: OPEN — “Open, Anyone in this space can edit”: everyone with space access can VIEW and EDIT. EDIT_RESTRICTED — “Open, Anyone in this space can view”: everyone with space access can VIEW; only Specific access update principals can edit. VIEW_RESTRICTED — “Restricted, Only specific people can view or edit”: only Specific access read/update principals can VIEW; only update principals can edit.HOW GENERAL AND SPECIFIC ACCESS WORK TOGETHER: the state is the General access baseline. Moving away from OPEN removes broad access. Permission grants are Specific access exceptions that add access for individual users or groups; they do not remove General access or make content private by themselves. A principal has exactly ONE Specific access level — update, read, or none — and update includes read/view. Changing the state does not create or modify Specific access grants.SELF-LOCKOUT: when leaving OPEN, the caller must retain update; read is not sufficient for editing. Private creation already performs the safe VIEW_RESTRICTED + creator update setup. Existing-state and self-lockout validation belongs to the Confluence monolith, and this tool never disables it.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Setconfluencecontentstatus
Setconfluencecontentstatus
ATLASSIAN_MCP_SET_CONFLUENCE_CONTENT_STATUSSet the content state (status) of a Confluence page or blog postInput Parameters
color. Ignored when id is provided.#FF8B00). Sent together with name. Ignored when id is provided.execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Setconfluencespaceinstructions
Setconfluencespaceinstructions
ATLASSIAN_MCP_SET_CONFLUENCE_SPACE_INSTRUCTIONSSet the space instructions for a Confluence spaceInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Setjsmagentavailability
Setjsmagentavailability
ATLASSIAN_MCP_SET_JSM_AGENT_AVAILABILITYSet one Jira Service Management Workforce Management agent’s availability for a service project. Use this for “set me available”, “set me on break”, or an explicitly supplied agentAccountId when you are authorized to update that agent. Status accepts AVAILABLE or ON_BREAK and TWG-compatible aliases available, active, online, away, on-break, or unavailable. This is not for reading availability, bulk team updates, project defaults, assignment, or Live Chat status.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Starconfluencecontent
Starconfluencecontent
ATLASSIAN_MCP_STAR_CONFLUENCE_CONTENTStar a Confluence content item for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Starconfluencespace
Starconfluencespace
ATLASSIAN_MCP_STAR_CONFLUENCE_SPACEStar a Confluence space for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Transitionjiraissue
Transitionjiraissue
ATLASSIAN_MCP_TRANSITION_JIRA_ISSUEMove a Jira issue through its workflow and/or into a sprint or the backlog — at least one is required. Take transitionId from listJiraIssueTransitions; transitionName is the transition’s own name, not the target status. Returns the status the issue actually landed in, so no read-back is needed. If the sprint/backlog move fails after the status change succeeds, the status change stays — retry the move alone, not the whole call.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Transitionjsmrequest
Transitionjsmrequest
ATLASSIAN_MCP_TRANSITION_JSM_REQUESTPerform one customer/request-portal-visible Jira Service Management request transition selected from getJsmRequestActionMetadata. This is for help-seeker/customer portal transitions, not agent-side queue or generic Jira workflow transitions. It returns compact execution metadata only; use getJsmRequest afterwards when refreshed request state is needed.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Unarchiveconfluencecontent
Unarchiveconfluencecontent
ATLASSIAN_MCP_UNARCHIVE_CONFLUENCE_CONTENTUnarchive (restore) a single Confluence content entityInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Unstarconfluencecontent
Unstarconfluencecontent
ATLASSIAN_MCP_UNSTAR_CONFLUENCE_CONTENTRemove a star from a Confluence content item for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Unstarconfluencespace
Unstarconfluencespace
ATLASSIAN_MCP_UNSTAR_CONFLUENCE_SPACERemove a star from a Confluence space for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Unwatchconfluencecontent
Unwatchconfluencecontent
ATLASSIAN_MCP_UNWATCH_CONFLUENCE_CONTENTStop watching a Confluence content item for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Unwatchconfluencelabel
Unwatchconfluencelabel
ATLASSIAN_MCP_UNWATCH_CONFLUENCE_LABELStop watching a Confluence label for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Unwatchconfluencespace
Unwatchconfluencespace
ATLASSIAN_MCP_UNWATCH_CONFLUENCE_SPACEStop watching a Confluence space for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updatecapacityplanallocations
Updatecapacityplanallocations
ATLASSIAN_MCP_UPDATE_CAPACITY_PLAN_ALLOCATIONSAllocate people to a single work item over one or more time periods in Individual Capacity Planning. USE WHEN the user asks to put someone on a work item for a period, to change how much of their time it takes, to book leave, or to clear an allocation. Every person in contributorDataIds is assigned to the work item automatically, so it does not need to be assigned to them first, and every allocation is applied to every person - the number of writes is contributorDataIds x allocations, which must not exceed 100. Only one work item per call. Resolve a non-project work ARI with listCapacityPlanNonProjectWork rather than fabricating one. Each allocation covers a period and carries the TOTAL effort for that period, of any length. To express a RATE, send one allocation per interval: “2 days a week for three weeks” is three allocations of 2, NOT one allocation of 2 spanning three weeks. A single allocation spanning all of September means “this much effort across September”, which the plan spreads over the weeks in it. Re-running the same periods REPLACES those allocations rather than adding to them, so the call is safe to repeat; set value to 0 to clear a period. Because value is the TOTAL for the period and re-running replaces it, any RELATIVE change - “add a day”, “bump Chris to 3 days”, “halve it” - needs the current figure first. Call getCapacityPlanAllocations with the same contributorDataIds and workDataIds, the same date window, and expand: [“contributions”], then send the new total. Writing the relative amount directly overwrites the existing allocation instead of adding to it. An absolute request (“put Chris on PROJ-42 at 50% in September”) needs no prior read. This does NOT add anyone to a capacity plan and cannot create work items - contributors and work items are global, so an allocation written here shows up on every plan they belong to, matching the UI. Add ‘contributions’ to expand to return the value written per period and confirm what landed, ‘contributorAggregations’ for each person’s total contribution and availability across ALL their work in the allocated window (use this to report whether the change has pushed someone over capacity), and ‘workAggregations’ for the work item’s total effort across ALL contributors. Both aggregations come back as separate top-level objects. Omit expand when a simple confirmation is enough - each value costs extra work upstream. Capacity plans assume a baseline 40-hour working week, so 5 DAYS, 40 HOURS, and 100 PERCENTAGE are all the same amount - say so when reporting days or percentages.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updatecapacityplannonprojectwork
Updatecapacityplannonprojectwork
ATLASSIAN_MCP_UPDATE_CAPACITY_PLAN_NON_PROJECT_WORKRename an existing non-project work item in Individual Capacity Planning. “Non-project work” is a bucket of time that is not a Jira issue or an Atlas project, such as Leave, Run the Business (RtB), on-call, or training. USE WHEN the user asks to rename an existing non-project work item. This only changes the item’s name; it does not move allocations, add contributors, or delete anything. To change who is allocated or how much effort a period carries, use updateCapacityPlanAllocations instead. Resolve the item’s id first with listCapacityPlanNonProjectWork rather than fabricating one. Returns whether the update succeeded and any errors.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updateconfluencecomment
Updateconfluencecomment
ATLASSIAN_MCP_UPDATE_CONFLUENCE_COMMENTUpdate an existing Confluence footer or inline comment on a page or blog postInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updateconfluencecommentresolution
Updateconfluencecommentresolution
ATLASSIAN_MCP_UPDATE_CONFLUENCE_COMMENT_RESOLUTIONResolve or reopen a Confluence footer or inline commentInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updateconfluencecontent
Updateconfluencecontent
ATLASSIAN_MCP_UPDATE_CONFLUENCE_CONTENTUpdate Confluence docs, whiteboards, or databases.Before choosing body.format or authoring an edit, call getContentFormatGuide through execute with name=getContentFormatGuide and inputs={toolName}. Use updateConfluencePage for pages, blog posts, and live docs; updateConfluenceWhiteboard for whiteboards; or updateConfluenceDatabase for databases.Space instructions describe how to author content in a Confluence space. Apply relevant guidance to the content you create or update. Follow this decision rule:- Before authoring, call getConfluenceSpace for the target space unless getConfluenceContent returned metadata.hasSpaceInstructions=false for content in that space. If getConfluenceSpace already returned for the same cloudId and space during the current task, reuse its spaceInstructions and do not call it again.
- When the value is true or unknown and instructions have not been loaded, you must call getConfluenceSpace once before authoring through execute with name=getConfluenceSpace, top-level cloudId, and inputs={spaceIdOrKey}.
- Apply any returned spaceInstructions. If a successful response omits them, no instructions are configured; author with defaults and do not block.
Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updatefocusarea
Updatefocusarea
ATLASSIAN_MCP_UPDATE_FOCUS_AREAUpdate one or more fields on an existing Focus area. Provide at least one of name, owner, startDate, or description — identifier-only calls fail upstream. Omitted fields are unchanged. Use createFocusAreaStatusUpdate for status, health, target date, or status summary changes. Multiple fields become separate mutations — a later failure can leave earlier fields already applied.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updatejsmopsalert
Updatejsmopsalert
ATLASSIAN_MCP_UPDATE_JSM_OPS_ALERTUpdate one Jira Service Management Operations alert by acknowledging, unacknowledging, closing, or escalating it. Escalation requires an escalation responder ID assigned to that alert. Optionally poll the asynchronous request status once.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updateloomvideopermissions
Updateloomvideopermissions
ATLASSIAN_MCP_UPDATE_LOOM_VIDEO_PERMISSIONSChange who can access a Loom video by setting its visibility to OWNER (only you), WORKSPACE (anyone in your workspace), or PUBLIC (anyone with the link). The change is immediate and permanent. To notify specific people about a video instead of changing its visibility, use shareLoomVideo. Identify the video by ARI or share URL. Returns id, name, visibility, url, and updatedAt. Omit responseFields to keep these defaults; videoUrl and videoAri are inputs, not response field names.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updateloomvideotitle
Updateloomvideotitle
ATLASSIAN_MCP_UPDATE_LOOM_VIDEO_TITLERename a Loom video. The change is immediate and visible to all viewers. Identify the video by ARI or share URL. To change who can access the video instead of its title, use updateLoomVideoPermissions.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updatetalentpositionfocusareamappings
Updatetalentpositionfocusareamappings
ATLASSIAN_MCP_UPDATE_TALENT_POSITION_FOCUS_AREA_MAPPINGSAllocate Talent positions to focus areas, or clear the focus area a position is allocated to. Each mapping sets the focus area of ONE position and REPLACES the focus area that position is allocated to now — a position is allocated to one focus area at a time, so this is not additive and it cannot add a second focus area to a position. Omit focusAreaId in a mapping to clear the allocation and leave that position unallocated. Every mapping is applied as a single all-or-nothing change, so one rejected ARI fails the whole call — keep batches small. Do not guess either ARI: take a position ARI from a searchTalentPositions result’s id or a getTalentPositionsByEntity result’s entityId, and take a focus area ARI from getTalentFields for the focus area field, or from searchFocusAreas. To see which positions a focus area is staffed by before or after the change, call getTalentPositionsByEntity with entity=focusArea.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Updateteam
Updateteam
ATLASSIAN_MCP_UPDATE_TEAMUpdate one Atlassian team through exactly one operation. Use update_details with displayName, description, or membershipSettings; add_members with accountIds and/or add-only emails; or remove_members with accountIds. Metadata and membership changes cannot be mixed. Removing members can remove access.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Uploadattachmenttojiraissue
Uploadattachmenttojiraissue
ATLASSIAN_MCP_UPLOAD_ATTACHMENT_TO_JIRA_ISSUEAttach a single local file to a Jira issue. Two phases: (1) call with filePath only to get a local uploadCommand; run it from your shell to upload the bytes and obtain a fileId; (2) call again with that fileId to attach the file to the issue. To instead embed the uploaded file inline in a body, stop after phase 1 and pass the fileId (with its collection) to editJiraIssue/addOrEditJiraIssueComment via inlineFileId (appends at the end) or an HTML body media node (for positional placement) — do not also run phase 2 for the same file.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Watchconfluencecontent
Watchconfluencecontent
ATLASSIAN_MCP_WATCH_CONFLUENCE_CONTENTStart watching a Confluence content item for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Watchconfluencelabel
Watchconfluencelabel
ATLASSIAN_MCP_WATCH_CONFLUENCE_LABELStart watching a Confluence label for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Watchconfluencespace
Watchconfluencespace
ATLASSIAN_MCP_WATCH_CONFLUENCE_SPACEStart watching a Confluence space for the current userInput Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.Watchjiraissue
Watchjiraissue
ATLASSIAN_MCP_WATCH_JIRA_ISSUEAdd or remove the calling user as a watcher on a Jira issue. Always acts on you — it cannot add or remove another person, and it does not list who is watching. Watching only subscribes you to notifications about the issue; it does not assign it to you. To do that, set the issue’s assignee field with editJiraIssue.Input Parameters
execute and its read/write/destructive variants strictly require it for cloudId-scoped operations and fail without it. Not needed for cloudId-less operations (e.g. Bitbucket), which ignore this field.