---
ref: tool:atlassian/comment-on-jira-work-item
name: Comment on a Jira work item
company: company:atlassian
workflows: []
access: [mcp, cli, api]
tags: [capability:manage-tasks, category:project-management, has:api, has:cli, has:mcp]
docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-comments/#api-rest-api-3-issue-issueidorkey-comment-post
updated: 2026-09-27
---

# Comment on a Jira work item

Adds a comment to a Jira work item and returns the new comment.

On the API the comment `body` is Atlassian Document Format; the CLI takes
`--key` and a plain-text or ADF `--body`, and can comment on every work item a
`--jql` query matches. `addOrEditJiraIssueComment` also edits an existing
comment.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v2/mcp" } } }
```

Call the MCP tool `addOrEditJiraIssueComment`.

Server URL: https://mcp.atlassian.com/v2/mcp

### CLI (official)

Install the command, then confirm it runs.

```sh
brew tap atlassian/homebrew-acli && brew install acli
acli --version
```

Run `acli jira workitem comment create`.

### API (official)

- Base URL: https://{your-domain}.atlassian.net
- Endpoint: `POST /rest/api/3/issue/{issueIdOrKey}/comment`
- Auth: send the header `Authorization: Basic $ATLASSIAN_API_KEY`
- Get a key: https://id.atlassian.com/manage-profile/security/api-tokens
- Docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.