Which Bitbucket repositories can Lyro reach?

Only what the connected account can. Get User Permissions for Repositories and Get User Permissions for Workspaces resolve that at call time, and List Repositories in Workspace enumerates what is visible - a private repo the connecting user has no access to stays out of reach.

Can Lyro request changes on a pull request rather than approving it?

Yes. Request Pull Request Changes is a distinct action from Approve Pull Request, and Resolve Pull Request Comment closes out a thread once it has been dealt with, so a review can end in a rejection with reasons rather than a binary approve or nothing.

Can Lyro annotate a commit with results from an external check?

Create Commit Report Annotations, Update Commit Insight Report, and Get Commit Reports let Lyro attach findings to a specific commit, which is how a linter or scanner result shows up inline in the Bitbucket diff rather than only in a chat message.

Can Lyro change CI pipeline variables?

Create Team Pipeline Variable, Create User Pipeline Variable, and their update counterparts are exposed, alongside Get Repository Pipeline Variables for reading. Because these carry build credentials, they should sit behind the same review your team already applies to CI configuration changes.

Bitbucket Integration - Lyro AI Agent

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create an issue comment
Lyro posts a comment on a Bitbucket issue with the details from the conversation. The engineering team sees the context on the ticket without an agent forwarding it separately.
Merge pull request
Lyro merges an approved pull request in Bitbucket directly through the API. The change ships without a developer stopping what they're doing to click merge.
Browse repository path
Lyro looks up the contents of a file or folder in a Bitbucket repository at a given revision. Agents can check the actual code behind a bug report without opening the repo themselves.

See all 105 actions

How businesses use Bitbucket + Lyro

Each card is one request a support team gets, and the Bitbucket actions Lyro runs to close it.

Find the code behind a reported problem
Lyro searches code across the workspace, opens the file at the revision in question, and reads the commit history behind it before anyone forms a theory.
Search Code in WorkspaceGet File From RepositoryGet File Commit History
Turn a report into a branch and a pull request
Lyro files the issue, cuts the branch, and opens the pull request with the reporter's own wording in the description so the fix starts from what was actually observed.
Create an IssueCreate a BranchCreate a Pull Request
Move a pull request through review
Lyro reads the diff, leaves the review comment, and approves or merges once the conversation and the checks agree.
Get Pull Request DiffCreate Pull Request CommentMerge Pull Request
Report which pipeline run broke and where
Lyro lists recent pipelines, drills into the failing steps, and matches the result to the commit build status so the blame lands on a change rather than a guess.
List PipelinesGet Pipeline StepsGet Commit Build Status

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Bitbucket actions it has and picks the ones a request needs.

01
Connect Bitbucket
Authorize the Bitbucket account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Bitbucket actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Bitbucket · Lyro

Everything else about Bitbucket

Setup, permissions, and the limits of what Lyro can do inside Bitbucket.

Only what the connected account can. Get User Permissions for Repositories and Get User Permissions for Workspaces resolve that at call time, and List Repositories in Workspace enumerates what is visible - a private repo the connecting user has no access to stays out of reach.

Every action available in Bitbucket

All 105 actions your agent can call on Bitbucket, straight from the live MCP connection.

Approve pull request
Approve a pull request as the authenticated user.
Browse repository path
Retrieve content for a file path or browse directory contents at a specified revision in a Bitbucket repository.
Create a branch
Creates a new branch in a Bitbucket repository from a target commit hash; the branch name must be unique, adhere to Bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Create an issue
Creates a new issue in a Bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component IDs exist.
Create an issue comment
Adds a new comment with markdown support to an existing Bitbucket issue.
Create a pull request
Creates a new pull request in a specified Bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
Create pull request comment
Creates a new comment on a Bitbucket pull request.
Create commit report annotations
Adds multiple annotations to a commit report in bulk.
List commits from revision (post)
List commits from a revision using POST method.
Create repository
Creates a new Bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if project_key is not provided.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified Bitbucket snippet.
Create team pipeline variable
Creates a team-level pipeline configuration variable in Bitbucket.
Create user pipeline variable
Creates a user-level pipeline variable for Bitbucket pipelines.
Delete commit comment
Permanently deletes a specific comment on a commit.
Delete issue
Permanently deletes a specific issue, identified by its issue_id, from the repository specified by repo_slug within the given workspace.
Delete pull request comment
Permanently deletes a specific pull request comment (top-level, inline, or threaded reply).
Delete commit report annotation
Deletes a single annotation matching the provided ID from a commit report.
Delete repository
Permanently deletes a specified Bitbucket repository; this action is irreversible and does not affect forks.
Delete snippet watch
Stops watching a specific snippet.
Delete user pipeline variable
Permanently deletes a user-level pipeline configuration variable identified by its UUID.
Get branch
Retrieves detailed information about a specific branch in a Bitbucket repository.
Get commit build status
Get a specific build status for a commit in Bitbucket.
Get commit changes
Retrieve a page of changes made in a specified commit, showing all changed files with their change statistics (lines added/removed, status).
Get commit comment
Retrieves a specific comment from a commit by its ID.
Get commit diff
Retrieve the unified diff between two provided revisions or for a single commit in a Bitbucket repository.
Get current user (v2)
Retrieve complete profile information for the currently authenticated Bitbucket user.
Get deployment environment variables
Retrieves deployment environment level variables for a specific Bitbucket repository environment.
Get file from repository
Retrieves a specific file's content from a Bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit.
Get hook events
Retrieves a paginated list of all valid webhook events for a specified entity type (repository or workspace).
Get openid configuration for oidc in pipelines
Retrieves the OpenID Connect discovery configuration for Bitbucket Pipelines OIDC.

The tools Bitbucket sits next to

Same connection, same setup. Pick the next one your team already uses.

Browse every integration

Bitbucket MCP integration

Three actions you can hand over today

Create an issue comment

Merge pull request

Browse repository path

How businesses use Bitbucket + Lyro

Find the code behind a reported problem

Turn a report into a branch and a pull request

Move a pull request through review

Report which pipeline run broke and where

Get started in 3 steps

Connect Bitbucket

Tell your agent what you need

Watch it work

Everything else about Bitbucket

Every action available in Bitbucket

Approve pull request

Browse repository path

Create a branch

Create an issue

Create an issue comment

Create a pull request

Create pull request comment

Create commit report annotations

List commits from revision (post)

Create repository

Create snippet comment

Create team pipeline variable

Create user pipeline variable

Delete commit comment

Delete issue

Delete pull request comment

Delete commit report annotation

Delete repository

Delete snippet watch

Delete user pipeline variable

Get branch

Get commit build status

Get commit changes

Get commit comment

Get commit diff

Get current user (v2)

Get deployment environment variables

Get file from repository

Get hook events

Get openid configuration for oidc in pipelines

The tools Bitbucket sits next to

Bolt iot

Cursor

Google address validation

Ngrok

Screenshotone

V0

Ready to connect Bitbucket?