Bitbucket - Veryfront

At a glance

Availability: Experimental (how to enable).
Authentication: OAuth 2.0.
Connection: A user authorizes the connection in the provider’s consent screen.
Scopes: repository, pullrequest:write, issue, account.

Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

Variable	Required	Description
`BITBUCKET_CLIENT_ID`	Yes	Bitbucket OAuth Consumer Key Docs.
`BITBUCKET_CLIENT_SECRET`	Yes	Bitbucket OAuth Consumer Secret Docs.

Tools

Tool	Access	Description
List Repositories `bitbucket__list_repositories`	Read	Get list of user’s repositories
Get Repository `bitbucket__get_repository`	Read	Get details of a specific repository
List Pull Requests `bitbucket__list_pull_requests`	Read	Get pull requests for a repository
Get Pull Request `bitbucket__get_pull_request`	Read	Get details of a specific pull request
Create Pull Request `bitbucket__create_pull_request`	Write	Create a new pull request
Add Pull Request Comment `bitbucket__add_pull_request_comment`	Write	Add a comment to a pull request
List Issues `bitbucket__list_issues`	Read	Get issues for a repository

Verify the connection

Call a read tool such as bitbucket__list_repositories with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.