# How to connect Bitbucket to OpenClaw (no API keys) > Connect Bitbucket to OpenClaw with ClawLink in one click — 105 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/bitbucket The usual route to Bitbucket access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Bitbucket setup: install one ClawHub skill, connect Bitbucket in the browser, and OpenClaw can call real Bitbucket actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/bitbucket ## Setup It takes three steps to connect OpenClaw to Bitbucket. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bitbucket** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect bitbucket # connect Bitbucket (browser OAuth) npx -y @useclawlink/cli actions bitbucket # list available actions npx -y @useclawlink/cli run bitbucket --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Bitbucket in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Bitbucket to approve pull request and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Bitbucket is connected in the dashboard, that agent calls the same 105 Bitbucket tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Bitbucket MCP for OpenClaw Looking for a Bitbucket MCP server for OpenClaw? ClawLink connects Bitbucket to OpenClaw and exposes 105 Bitbucket tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Bitbucket integration](https://claw-link.dev/hermes/bitbucket) works the same way. ## What the OpenClaw Bitbucket integration can do 105 Bitbucket tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 105. ### 30 of 105 Bitbucket tools for OpenClaw | Tool | What it does | |---|---| | **Approve pull request** `bitbucket_approve_pull_request` | Approve a pull request | | **Browse repository path** `bitbucket_browse_repository_path` | Browse repository contents at a path | | **Create branch** `bitbucket_create_branch` | Create a new branch in a repository | | **Create issue** `bitbucket_create_issue` | Create a new issue in a repository | | **Create pull request** `bitbucket_create_pull_request` | Create a new pull request | | **Create repository** `bitbucket_create_repository` | Create a new repository | | **Create repositories commits2** `bitbucket_create_repositories_commits2` | List commits from a revision using POST method | | **Get branch** `bitbucket_get_branch` | Retrieves detailed information about a specific branch in a Bitbucket repository | | **Get commit build status** `bitbucket_get_commit_build_status` | Get a specific build status for a commit in Bitbucket | | **Get commit changes** `bitbucket_get_commit_changes` | Retrieve a page of changes made in a specified commit, showing all changed files with their | | **Get commit comment** `bitbucket_get_commit_comment` | Retrieves a specific comment from a commit by its ID | | **Get commit diff** `bitbucket_get_commit_diff` | Retrieve the unified diff between two provided revisions or for a single commit in a Bitbucket | | **Get current user2** `bitbucket_get_current_user2` | Retrieve complete profile information for the currently authenticated Bitbucket user | | **Get deployment environment variables** `bitbucket_get_deployment_environment_variables` | Retrieves deployment environment level variables for a specific Bitbucket repository environment | | **Get file from repository** `bitbucket_get_file_from_repository` | Retrieves a specific file's content from a Bitbucket repository at a given commit (hash | | **Get hook events** `bitbucket_get_hook_events` | Retrieves a paginated list of all valid webhook events for a specified entity type (repository | | **Get openid configuration** `bitbucket_get_openid_configuration` | Retrieves the OpenID Connect discovery configuration for Bitbucket Pipelines OIDC | | **Get pull request** `bitbucket_get_pull_request` | Get a single pull request by ID with complete details | | **Get pull request comment** `bitbucket_get_pull_request_comment` | Retrieve a specific comment from a pull request by its ID | | **Get pull request commits** `bitbucket_get_pull_request_commits` | Retrieve commits for a specified pull request | | **Get pull request diff** `bitbucket_get_pull_request_diff` | Fetch the unified diff for a Bitbucket pull request (follows 302 redirect to repository diff) | | **Get pull request diffstat** `bitbucket_get_pull_request_diffstat` | Get the diffstat for a Bitbucket pull request, showing all changed files with their change | | **Get repositories branching model** `bitbucket_get_repositories_branching_model` | Return the branching model as applied to the repository | | **Get repositories commit** `bitbucket_get_repositories_commit` | Retrieve detailed information about a specific commit in a Bitbucket repository | | **Get repositories commit comments** `bitbucket_get_repositories_commit_comments` | Retrieves all comments on a specific commit in a Bitbucket repository | | **Get repositories commit report** `bitbucket_get_repositories_commit_report` | Returns a single report matching the provided ID from a commit | | **Get repositories commit reports** `bitbucket_get_repositories_commit_reports` | Get reports linked to a specific commit | | **Get repositories commit reports annotations** `bitbucket_get_repositories_commit_reports_annotations` | Returns a single annotation matching the provided ID from a commit report | | **Get repositories commit statuses** `bitbucket_get_repositories_commit_statuses` | Returns all build statuses (e.g., CI/CD pipeline results) for a specific commit | | **Get repositories effective branching model** `bitbucket_get_repositories_effective_branching_model` | Retrieves the effective branching model for a Bitbucket repository, showing which branching | ## Example prompts **Approve Pull Request** > Use Bitbucket to approve pull request and walk me through the result in plain English. **Browse Repository Path** > Use Bitbucket to browse repository path and walk me through the result in plain English. **Create Branch** > Create it in Bitbucket for me, then confirm the important fields before you finish. **Create Issue** > Create it in Bitbucket for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bitbucket working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Bitbucket app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Bitbucket through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Bitbucket. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Bitbucket actions to the runtime in a format your agent can reliably use. | 105 tools for Bitbucket are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bitbucket to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Bitbucket in the browser, and the 105 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Bitbucket skill but can't call the tools The ClawHub skill teaches OpenClaw about Bitbucket, but the calls run through the ClawLink plugin and your connected account. Make sure Bitbucket is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Bitbucket from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Bitbucket tools Bitbucket tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Bitbucket call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Bitbucket returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Bitbucket and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Bitbucket integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bitbucket: link your Bitbucket account once in the browser and OpenClaw can call the Bitbucket API through 105 ready-made tools — no custom code or token handling. ### How do I add Bitbucket to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bitbucket skill from ClawHub, then you click Connect in the dashboard to authorize Bitbucket. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Bitbucket to OpenClaw? About two minutes. Sign in, click Connect next to Bitbucket in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bitbucket up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bitbucket working from chat. ### OpenClaw installed the Bitbucket skill but can't call the tools The ClawHub skill teaches OpenClaw about Bitbucket, but the calls run through the ClawLink plugin and your connected account. Make sure Bitbucket is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.