Developer tools
Bitbucket for AI agents.
Managed auth, ready-made tools.
List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
About Bitbucket
With the Bitbucket connector, your agent works in each user’s own Bitbucket workspaces through Agent200: it lists and opens pull requests, comments on them, reads code and checks pipeline runs. Every user connects their own account through managed OAuth, and the agent acts with that user’s repository access.
Bitbucket is Atlassian’s Git hosting service, with pull requests, code review and built-in CI/CD through Bitbucket Pipelines.
Tools
What your agent can do in Bitbucket.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Bitbucket connection.
-
List repositories
Readbitbucket_list_repositoriesList the repositories in a workspace the user can access.
-
List pull requests
Readbitbucket_list_pull_requestsList a repository's pull requests, filtered by state.
-
Create a pull request
Writebitbucket_create_pull_requestOpen a pull request from one branch into another.
-
Comment on a pull request
Writebitbucket_create_commentAdd a comment to a pull request.
-
Approve a pull request
Writebitbucket_approve_pull_requestApprove a pull request as the connected user.
-
Read a file
Readbitbucket_get_fileRead a file from a repository at a branch or commit.
-
List pipelines
Readbitbucket_list_pipelinesList a repository's pipeline runs and their results.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Bitbucket, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let your agent read and comment, and switch off
bitbucket_approve_pull_requestif approvals should stay with people. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use. A call outside them is refused.
Get started
Connect Bitbucket
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Bitbucket
Each end user authorizes their own Bitbucket account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Bitbucket account, once. const connection = await agent200 .user("user_123") .connect("bitbucket"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Bitbucket tools
Name the user, the model and the tools. The model decides which Bitbucket tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "List the open pull requests in the payments repo", tools: ["bitbucket"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, with their Atlassian account on Bitbucket's own page. You never see or store their password.
-
What access is requested
Bitbucket shows the permissions requested, such as reading repositories, reading or writing pull requests and reading pipelines. The agent reaches only the workspaces and repositories that user can already open.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Bitbucket connector and how to use it.
Connector: Bitbucket, through Agent200. In code: "bitbucket". What it does: List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces. Page: https://www.agent200.com/tools/bitbucket/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Bitbucket's own page, through the authorization link Agent200 returns. Never ask a user for a Bitbucket password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: bitbucket_list_repositories, bitbucket_list_pull_requests, bitbucket_get_file, bitbucket_list_pipelines. Write tools: bitbucket_create_pull_request, bitbucket_create_comment, bitbucket_approve_pull_request. Name "bitbucket" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/bitbucket/framework/claude/ https://www.agent200.com/tools/bitbucket/framework/chatgpt/ https://www.agent200.com/tools/bitbucket/framework/claude-code/ https://www.agent200.com/tools/bitbucket/framework/muse/ https://www.agent200.com/tools/bitbucket/framework/grok-bot/ https://www.agent200.com/tools/bitbucket/framework/openai-dots/ https://www.agent200.com/tools/bitbucket/framework/claude-duet/ https://www.agent200.com/tools/bitbucket/framework/hermes-agent/ https://www.agent200.com/tools/bitbucket/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/bitbucket.md
Guides
Use Bitbucket with the AI you build on.
Step-by-step setup for Bitbucket with a specific model, assistant or agent framework.
-
Bitbucket + Claude
How to connect Bitbucket to Claude
-
Bitbucket + ChatGPT
How to connect Bitbucket to ChatGPT
-
Bitbucket + Claude Code
How to connect Bitbucket to Claude Code
-
Bitbucket + Muse
How to connect Bitbucket to Muse
-
Bitbucket + Grok Bot
How to connect Bitbucket to Grok Bot
-
Bitbucket + OpenAI Dots
How to connect Bitbucket to OpenAI Dots
-
Bitbucket + Claude Duet
How to connect Bitbucket to Claude Duet
-
Bitbucket + Hermes Agent
How to connect Bitbucket to Hermes Agent
-
Bitbucket + OpenClaw
How to connect Bitbucket to OpenClaw
FAQ
Bitbucket and Agent200, answered.
Who handles the Bitbucket OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Bitbucket.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Bitbucket connection, never another user's. It cannot reach anything the user or Bitbucket has not authorized.
Can I limit what my agent can do in Bitbucket?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.