@stubbedev/atlassian-mcp 0.5.13 → 0.5.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -36,8 +36,8 @@ A [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for **s
|
|
|
36
36
|
|---|---|
|
|
37
37
|
| `bitbucket_search` | Discover resources: `pull_requests` (default), `repos`, `branches`, or `users` via `resource` param; `mine=true` for your inbox, narrowed with `role=author` / `reviewer` / `participant` |
|
|
38
38
|
| `bitbucket_get_pr` | Full PR details: metadata, commits, comments, blockers, build status, optional diff, and any attachments referenced from the description or comments |
|
|
39
|
-
| `bitbucket_mutate` | Create/update a PR, or perform lifecycle actions: `approve`, `unapprove`, `needs_work`, `merge`, `decline`. Reviewer names are verified against Bitbucket, and an update that would drop existing reviewers needs `update.replaceReviewers=true` |
|
|
40
|
-
| `bitbucket_comment` | Add, update, or delete a PR comment; for code changes use `suggestion` so Bitbucket shows Apply suggestion. Enforced here: one reply per thread, no new top-level comment on your own PR (`asAuthor=true` to override), `#123` references rewritten as links. `pending=true` posts an unpublished draft-review comment |
|
|
39
|
+
| `bitbucket_mutate` | Create/update a PR, or perform lifecycle actions: `approve`, `unapprove`, `needs_work`, `merge`, `decline`. Reviewer names are verified against Bitbucket, and an update that would drop existing reviewers needs `update.replaceReviewers=true`. `create.attachments` / `update.attachments` upload local files (screenshots, logs) to the repo and reference them from the description |
|
|
40
|
+
| `bitbucket_comment` | Add, update, or delete a PR comment; for code changes use `suggestion` so Bitbucket shows Apply suggestion. Enforced here: one reply per thread, no new top-level comment on your own PR (`asAuthor=true` to override), `#123` references rewritten as links. `pending=true` posts an unpublished draft-review comment. `attachments` uploads local files and references them from the comment |
|
|
41
41
|
| `bitbucket_get_file` | Raw file content at a branch, tag, or commit — or pass `prId` to read the PR source branch. Every response names the path and ref it came from, and pages via `maxChars`/`charOffset` |
|
|
42
42
|
| `bitbucket_pr_tasks` | Manage PR tasks (checklist items): `list`, `create`, `resolve`, `reopen`, `delete` |
|
|
43
43
|
|
|
@@ -95,7 +95,11 @@ cannot get them wrong, and they need no prompting:
|
|
|
95
95
|
components and fix versions, and Bitbucket reviewers are checked first; a bad
|
|
96
96
|
one comes back with the valid options instead of an opaque 400.
|
|
97
97
|
- **Markdown is converted to Jira wiki markup** on every Jira write (comments,
|
|
98
|
-
descriptions, worklogs)
|
|
98
|
+
descriptions, environments, worklogs): fenced code blocks in any style
|
|
99
|
+
(```` ``` ````/```` ```` ````/`~~~`, any info string), inline code, headings,
|
|
100
|
+
bold/bold-italic, strikethrough, links, autolinks and images, blockquotes
|
|
101
|
+
(`bq.`/`{quote}`), tables, and bullet or ordered lists (`-`/`*`/`+` and
|
|
102
|
+
`1.`/`1)`). Text that is already wiki markup is left alone.
|
|
99
103
|
- **PR comment hygiene:** one reply per thread per author, no duplicate of a
|
|
100
104
|
comment you already posted, no new top-level comment on a PR you authored
|
|
101
105
|
(`asAuthor=true` to override), no tasks via `severity`, no emoji, and bare
|