bb_add_pr_comment

bb_add_pr_comment

Add Markdown-formatted comments to Bitbucket pull requests, reply to existing comments, or create inline code comments using file path and line number. Requires write permissions and Bitbucket credentials.

Instructions

Adds a comment to a specific pull request identified by prId within a repository (repoSlug). If workspaceSlug is not provided, the system will use your default workspace. The content parameter accepts Markdown-formatted text for the comment body. To reply to an existing comment, provide its ID in the parentId parameter. For inline code comments, provide both inline.path (file path) and inline.line (line number). Returns a success message as formatted Markdown. Requires Bitbucket credentials with write permissions to be configured.

Input Schema

Name	Required	Description
`content`	Yes	The content of the comment to add to the pull request in Markdown format. Bitbucket Cloud natively accepts Markdown - supports headings, lists, code blocks, links, and other standard Markdown syntax.
`inline`	No	Optional inline location for the comment. If provided, this will create a comment on a specific line in a file.
`parentId`	No	The ID of the parent comment to reply to. If not provided, the comment will be a top-level comment.
`prId`	Yes	Numeric ID of the pull request to add a comment to as a string. Must be a valid pull request ID in the specified repository. Example: "42"
`repoSlug`	Yes	Repository slug containing the pull request. This must be a valid repository in the specified workspace. Example: "project-api"
`workspaceSlug`	No	Workspace slug containing the repository. If not provided, the system will use your default workspace. Example: "myteam"

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "content": {
      "description": "The content of the comment to add to the pull request in Markdown format. Bitbucket Cloud natively accepts Markdown - supports headings, lists, code blocks, links, and other standard Markdown syntax.",
      "minLength": 1,
      "type": "string"
    },
    "inline": {
      "additionalProperties": false,
      "description": "Optional inline location for the comment. If provided, this will create a comment on a specific line in a file.",
      "properties": {
        "line": {
          "description": "The line number to add the comment to.",
          "exclusiveMinimum": 0,
          "type": "integer"
        },
        "path": {
          "description": "The file path to add the comment to.",
          "minLength": 1,
          "type": "string"
        }
      },
      "required": [
        "path",
        "line"
      ],
      "type": "object"
    },
    "parentId": {
      "description": "The ID of the parent comment to reply to. If not provided, the comment will be a top-level comment.",
      "type": "string"
    },
    "prId": {
      "description": "Numeric ID of the pull request to add a comment to as a string. Must be a valid pull request ID in the specified repository. Example: \"42\"",
      "minLength": 1,
      "type": "string"
    },
    "repoSlug": {
      "description": "Repository slug containing the pull request. This must be a valid repository in the specified workspace. Example: \"project-api\"",
      "minLength": 1,
      "type": "string"
    },
    "workspaceSlug": {
      "description": "Workspace slug containing the repository. If not provided, the system will use your default workspace. Example: \"myteam\"",
      "type": "string"
    }
  },
  "required": [
    "repoSlug",
    "prId",
    "content"
  ],
  "type": "object"
}

Atlassian Bitbucket MCP Server

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Atlassian Bitbucket MCP Server

Related Tools

MCP directory API