@stubbedev/atlassian-mcp 0.3.6 → 0.3.8

package/dist/bitbucket.js

@@ -1021,6 +1021,16 @@ export class BitbucketClient {
                 || args.toHash !== undefined)) {
             throw new Error('Replies must target an existing comment thread only. Omit filePath/line and other anchor fields when replying.');
         }
+        if (replyToCommentId !== undefined) {
+            const parent = await this.request('GET', `${this.rp(projectKey, repoSlug)}/pull-requests/${args.prId}/comments/${replyToCommentId}`).catch(() => null);
+            if (parent) {
+                const me = await this.getCurrentUsername();
+                const existingReply = (parent.comments ?? []).find((r) => !r.deleted && r.author?.name === me);
+                if (existingReply) {
+                    throw new Error(`You already replied to comment #${replyToCommentId} (your reply is #${existingReply.id}). Never post a second reply on the same thread — update your existing reply instead: action=update commentId=${existingReply.id}.`);
+                }
+            }
+        }
         if (args.text === undefined && args.suggestion === undefined) {
             throw new Error('Either text or suggestion is required when adding a comment.');
         }

package/dist/index.js

@@ -443,7 +443,7 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
             },
             {
                 name: 'bitbucket_comment',
-                description: `Add, update, or delete a PR comment. action defaults to "add". For code changes, ALWAYS use inline comments with suggestion when exact replacement code is available. Keep any explanatory text before the suggestion block only (never after), or Bitbucket may hide Apply suggestion. Replies MUST use commentId. Keep comments concise, no emojis. Only call proactively (without being asked) when you are a reviewer on the PR (i.e. "Viewing as" says "you are a reviewer") — never post unsolicited comments on PRs you authored. For inline comments: ALWAYS pass fromHash + toHash matching the commit you actually reviewed (read from bitbucket_pr_diff or bitbucket_get_pr output). Without them the anchor falls back to current PR head, and if the branch advanced between review and post the line number will point at unrelated code.`,
+                description: `Add, update, or delete a PR comment. action defaults to "add". For code changes, ALWAYS use inline comments with suggestion when exact replacement code is available. Keep any explanatory text before the suggestion block only (never after), or Bitbucket may hide Apply suggestion. Replies MUST use commentId. Only one reply per thread per author: if you already replied to a comment, update your existing reply (action=update commentId=<your-reply-id>) instead of posting a second one. The server enforces this and will reject the second add. Keep comments concise, no emojis. Only call proactively (without being asked) when you are a reviewer on the PR (i.e. "Viewing as" says "you are a reviewer") — never post unsolicited comments on PRs you authored. For inline comments: ALWAYS pass fromHash + toHash matching the commit you actually reviewed (read from bitbucket_pr_diff or bitbucket_get_pr output). Without them the anchor falls back to current PR head, and if the branch advanced between review and post the line number will point at unrelated code. When the comment body references another comment by id, render it as a markdown hyperlink \`[#<id>](<baseUrl>/projects/<PROJECT>/repos/<REPO>/pull-requests/<prId>/overview?commentId=<id>)\` — never a bare \`#<id>\`, which is unclickable in Bitbucket's renderer.`,
                 inputSchema: {
                     type: 'object',
                     properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stubbedev/atlassian-mcp",
-  "version": "0.3.6",
+  "version": "0.3.8",
   "description": "MCP server for self-hosted Jira and Bitbucket",
   "license": "MIT",
   "type": "module",