# 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.

- Page: https://www.agent200.com/tools/bitbucket/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `bitbucket`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

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/

## About

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.

## Bitbucket tools

- **List repositories** (`bitbucket_list_repositories`, read): List the repositories in a workspace the user can access.
- **List pull requests** (`bitbucket_list_pull_requests`, read): List a repository's pull requests, filtered by state.
- **Create a pull request** (`bitbucket_create_pull_request`, write): Open a pull request from one branch into another.
- **Comment on a pull request** (`bitbucket_create_comment`, write): Add a comment to a pull request.
- **Approve a pull request** (`bitbucket_approve_pull_request`, write): Approve a pull request as the connected user.
- **Read a file** (`bitbucket_get_file`, read): Read a file from a repository at a branch or commit.
- **List pipelines** (`bitbucket_list_pipelines`, read): List a repository's pipeline runs and their results.

## Limits you can set

**Turn single tools on or off.** Let your agent read and comment, and switch off `bitbucket_approve_pull_request` if 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "List the open pull requests in the payments repo"
- "Did the last pipeline on develop pass"
- "Open a pull request from feature/search into main"
- "Comment on PR 18 that the tests need updating"

## Guides: Bitbucket with your AI framework

- [Bitbucket + Claude](https://www.agent200.com/tools/bitbucket/framework/claude.md): Connect Bitbucket to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Bitbucket + ChatGPT](https://www.agent200.com/tools/bitbucket/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Bitbucket into your own agent with OpenAI's models and the Agent200 SDK.
- [Bitbucket + Claude Code](https://www.agent200.com/tools/bitbucket/framework/claude-code.md): Have Claude Code build a Bitbucket agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Bitbucket + Muse](https://www.agent200.com/tools/bitbucket/framework/muse.md): Connect Bitbucket to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Bitbucket + Grok Bot](https://www.agent200.com/tools/bitbucket/framework/grok-bot.md): Connect Bitbucket to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Bitbucket + OpenAI Dots](https://www.agent200.com/tools/bitbucket/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Bitbucket agent with OpenAI's models and the Agent200 SDK.
- [Bitbucket + Claude Duet](https://www.agent200.com/tools/bitbucket/framework/claude-duet.md): Connect Bitbucket to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Bitbucket + Hermes Agent](https://www.agent200.com/tools/bitbucket/framework/hermes-agent.md): Connect Bitbucket to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Bitbucket + OpenClaw](https://www.agent200.com/tools/bitbucket/framework/openclaw.md): Connect Bitbucket to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### 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.

## Related connectors

- [GitHub](https://www.agent200.com/tools/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/tools/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Jira](https://www.agent200.com/tools/jira.md): Search, create and transition Jira issues for the connected user.
- [Linear](https://www.agent200.com/tools/linear.md): Create and update issues, and read projects and cycles in your users' Linear teams.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
