Comment on a Jira work item

Comment on a Jira work item

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

Note: On the API the comment body must be Atlassian Document Format, not plain text. On the CLI, --jql comments on every work item the query matches.

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.

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

Call the MCP tool addOrEditJiraIssueComment.

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

Note: Tools beyond the listed ones are found with discover and run with executeRead or executeWrite; some spend Rovo credits.

CLI (official)

Install the command and sign in with it, then confirm it runs.

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

Run acli jira workitem comment create.

Note: Sign in with acli jira auth login --web. The CLI covers Jira only.

API (official)

• Base URL: https://{site}.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/

Note: {site} is your Atlassian site name, as in acme.atlassian.net. ATLASSIAN_API_KEY holds the base64 of <email>:<api token>, and Confluence paths start with /wiki.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.