Does Claude support the Bitbucket MCP server?

Yes. Claude connects to the Bitbucket MCP server through its connector settings, pointed at your Metorial URL. You need any Claude plan; Free plans allow one custom connector.

Do I need an API key to connect Bitbucket to Claude?

No. You sign in to Bitbucket once through Metorial, and Claude uses that connection. No API keys go into Claude's settings.

Which Bitbucket tools can Claude use?

All 24 Bitbucket tools your team allows, such as Delete Repository, Browse Source, Get Pull Request. Admins can narrow that list per team.

Can I control which teammates use Bitbucket in Claude?

Yes. Role-based access control decides who can use Bitbucket and which of its tools appear in Claude, and every call is logged with the person's identity.

What if Claude doesn't show Bitbucket tools?

On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.

Connect Bitbucket to Claude (MCP setup guide)

Ask Claude to use the delete repository tool in Bitbucket
Ask Claude to use the browse source tool in Bitbucket
Ask Claude to use the get pull request tool in Bitbucket
Ask Claude to use the fork repository tool in Bitbucket
Ask Claude to use the manage branches tool in Bitbucket

1. Enable Bitbucket in Metorial
In your Metorial portal, enable the Bitbucket MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add a custom connector
Open Customize, then Connectors. Select Add, then Custom, then Web.
3. Paste your Metorial MCP URL
Name it Metorial, paste your Magic MCP URL (<your-magic-mcp-url>) and continue.
4. Sign in
Select Add and sign in to load Bitbucket tools.

Once Bitbucket is enabled in Metorial, teammates sign in with SSO and get the same connection in Claude, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Delete Repository: Permanently delete a repository from the workspace.
Browse Source: Browse repository source files at a specific revision (branch, tag, or commit hash).
Get Pull Request: Retrieve detailed information about a specific pull request including its description, reviewers, merge details, and comments summary.
Fork Repository: Fork an existing repository.
Manage Branches: List, create, or delete branches in a repository.
Manage Pull Request: Perform actions on a pull request: **approve**, **unapprove**, **merge**, **decline**, **request_changes**, or **remove_change_request**.
List Workspace Members: List all members in the configured workspace.
Update Repository: Update repository settings (wiki, fork policy, project, privacy, language, name, description).
List Pull Requests: List pull requests for a repository.
Manage Projects: List, create, update, or delete projects in the workspace.
Manage Pipelines: List, get, trigger, or stop Bitbucket Pipelines.
Create Pull Request: Create a new pull request to merge changes from a source branch into a destination branch.
Search Code: Search for code across repositories in the workspace, optionally scoped to one repository.
List Commits: List commits in a repository, optionally filtered by branch.
Create Repository: Create a new Git repository in the configured workspace.
And 9 more on the Bitbucket MCP server page.

Turn Metorial on for a conversation with the + button, then Connectors; each connector has its own toggle.
Claude asks before it runs a Bitbucket tool. Choose Allow always only for tools you trust to run unsupervised.
Use the Search and tools menu to switch off tools you do not need in the current conversation.
Remove the connector from Customize, then Connectors. Team and Enterprise owners can do this for the whole organization.

Members on a Team or Enterprise plan cannot add the connector: On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.
The Free plan only allows one custom connector: One is enough: your Metorial URL carries every app your team approves, so you never need a second connector.
Tools do not show up in a chat: Connectors are switched on per conversation. Open the + menu in the chat, choose Connectors, and turn Metorial on.

Based on the Claude MCP documentation.

Frequently asked questions

Common questions about connecting Bitbucket to AI agents with Metorial.

Does Claude support the Bitbucket MCP server?
Yes. Claude connects to the Bitbucket MCP server through its connector settings, pointed at your Metorial URL. You need any Claude plan; Free plans allow one custom connector.
Do I need an API key to connect Bitbucket to Claude?
No. You sign in to Bitbucket once through Metorial, and Claude uses that connection. No API keys go into Claude's settings.
Which Bitbucket tools can Claude use?
All 24 Bitbucket tools your team allows, such as Delete Repository, Browse Source, Get Pull Request. Admins can narrow that list per team.
Can I control which teammates use Bitbucket in Claude?
Yes. Role-based access control decides who can use Bitbucket and which of its tools appear in Claude, and every call is logged with the person's identity.
What if Claude doesn't show Bitbucket tools?
On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.