Developer & CI · wired today
What can agents actually do with Bitbucket?
Build, review and release state is where agents earn their keep. The Bitbucket connector is one of 205 executable connectors and gives agents 5 read-only tools, with the credential held in the vault and every call receipted.
The Bitbucket tool list, exactly as agents see it
get_user— Get the Bitbucket account the credential belongs tolist_workspaces— List the Bitbucket workspaces this account is a member oflist_repositories— List the repositories in one Bitbucket workspaceget_repository— Get one Bitbucket repository by workspace and repository sluglist_pullrequests— List pull requests on one Bitbucket repository, optionally filtered by state
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Bitbucket connector needs
You provide username, app password from your Bitbucket account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Bitbucket's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
Bitbucket answers every unauthenticated request identically, so its endpoint paths rest on Bitbucket's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.
Bitbucket integration FAQ
What can Quox agents do with Bitbucket?
Agents can run 5 read-only tools against Bitbucket: get user, list workspaces, list repositories, get repository, list pullrequests. Every call is receipted in the evidence trail.
What does the Bitbucket integration need?
You provide username, app password from your Bitbucket account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Bitbucket credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Bitbucket connector?
Bitbucket answers every unauthenticated request identically, so its endpoint paths rest on Bitbucket's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.