← คู่มือทั้งหมด
คู่มือ Playbook · ฟรี

Work in Your Bitbucket Repositories, Pull Requests, and Pipelines Through Your Muse

ยืนยันแล้ว 2026-11-19

Through an AnythingMCP custom connector, your muse can work in Bitbucket Cloud: browse repositories, branches, commits, and files, review pull requests with diffs and comments, and check pipeline runs and deployments.

What it does

Bitbucket Cloud is where many software teams keep their code. Connected this way, the muse gets 25 tools. It lists your workspaces and repositories, reads branches, commits, and files, and lists deployments. For reviews, it lists pull requests, reads one in full with its reviewers and approval state, shows the diffstat and full diff, and reads its commits and comments. With your approval and right token scopes, it can open a pull request, post a comment, approve, merge, and start a pipeline run. No tool deletes a repository, branch, or comment.

How to use it

  1. In your Atlassian account, open Security, then API tokens, and create a scoped token for the Bitbucket app, checking the read scopes for workspace, repository, pull request, and pipeline.
  2. Add the write scopes for pull requests and pipelines only if you want the muse to comment, approve, merge, or start runs. Without them the token stays read-only.
  3. Copy the token into the Bitbucket connector in AnythingMCP, with no prefix in front of it.
  4. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in and approve.
  5. Ask in plain words: which pull requests in this repository are still open, and which have no approval yet?

What you need

  • A Muse account that can add custom connectors
  • An AnythingMCP workspace, on Cloud or self-hosted
  • A Bitbucket Cloud account, and an Atlassian API token with scopes

What to watch for

  • Old Bitbucket app passwords no longer work. Use a scoped API token. A repository or workspace access token works too, but it acts as a bot limited to that scope.
  • A merge changes the destination branch for the whole team and can start deployment pipelines, and a pipeline run uses build minutes. The muse names the repository, branches, and merge strategy and waits for your yes.
  • Diffs, files, and step logs are cut at 200 KB. For a long failing log, ask the muse to read the end of it, where the error usually sits.
  • Bitbucket no longer has a built-in issue tracker or wiki, so this connector has no tools for them.
  • This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.

ลองคู่มือนี้แล้วหรือยัง?

บอกเมืองว่าเป็นอย่างไร หรือขอความช่วยเหลือเพื่อให้ใช้งานได้

พูดคุยเรื่องนี้บน MuseFM →

Playbook Pro

อยากข้ามบทเรียนไหม?

ช่วยเอเจนต์ของคุณเรียนรู้ทุกอย่างในคราวเดียว 1,015 ทักษะ พาสเดียว $49 สำหรับ 90 วัน

รับ Pro Pass
คู่มือเพิ่มเติม →