How to connect Bitbucket to Cursor

  • Cursor gets 24 Bitbucket tools through one Metorial MCP URL.
  • Setup is 3 steps; teammates then sign in with SSO.
  • You need Cursor with MCP support.

What Cursor can do with Bitbucket

Ask your agent in plain language. Each of these maps to a real tool on the server.

  • Ask Cursor to use the manage pipelines tool in Bitbucket
  • Ask Cursor to use the create pull request tool in Bitbucket
  • Ask Cursor to use the search code tool in Bitbucket
  • Ask Cursor to use the list commits tool in Bitbucket
  • Ask Cursor to use the create repository tool in Bitbucket

Add the Bitbucket MCP server to Cursor

Run these once. Afterwards, everyone you give access to signs in the same way.

  1. 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. 2. Add Metorial to your MCP config

    Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.

    {
    "mcpServers": {
    "metorial": {
    "url": "<your-magic-mcp-url>"
    }
    }
    }
  3. 3. Sign in

    Open Customize in the sidebar, find Metorial and sign in to load Bitbucket tools.

Give your team Bitbucket in Cursor

Once Bitbucket is enabled in Metorial, teammates sign in with SSO and get the same connection in Cursor, 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.

Bitbucket tools available in Cursor

Full descriptions and inputs are on the Bitbucket MCP server page.

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

Using Bitbucket tools in Cursor

What to expect once Bitbucket is connected.

  • Cursor picks MCP tools automatically when they are relevant, including in Plan Mode. Name a Bitbucket tool to steer it.
  • Cursor asks for approval before it uses an MCP tool by default. Click the arrow next to the tool name to check the arguments first.
  • Switch the Metorial server off from Customize in the sidebar without removing it.
  • Cursor shows each Bitbucket tool response in chat, with expandable views of the arguments and the result.

Troubleshooting Cursor

Metorial connects but tools are missing or failing
Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.
Your company blocks the server
Enterprise admins approve remote servers in Team Settings, then MCP Configuration. Ask them to add a URL entry for your Metorial URL.
Cursor asks before every tool call
That is the default. Allowlist the Metorial tools you trust in your Run Mode settings to run them without a prompt.

Based on the Cursor MCP documentation.

Frequently asked questions

Common questions about connecting Bitbucket to AI agents with Metorial.

  1. Does Cursor support the Bitbucket MCP server?
    Yes. Cursor connects to the Bitbucket MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.
  2. No. You sign in to Bitbucket once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.
  3. All 24 Bitbucket tools your team allows, such as Delete Repository, Browse Source, Get Pull Request. Admins can narrow that list per team.
  4. Yes. Role-based access control decides who can use Bitbucket and which of its tools appear in Cursor, and every call is logged with the person's identity.
  5. Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.

Connect Bitbucket to other AI clients

Connect other apps to Cursor