Bitbucket MCP

Created By
MatanYeminia year ago
Bitbucket MCP - A Model Context Protocol (MCP) server for integrating with Bitbucket Cloud and Server APIs
Overview

What is Bitbucket MCP?

Bitbucket MCP is a Model Context Protocol (MCP) server designed for integrating with Bitbucket Cloud and Server APIs, enabling AI assistants to interact with Bitbucket repositories and pull requests.

How to use Bitbucket MCP?

To use Bitbucket MCP, you can run it via NPX or install it globally. Set the required environment variables for Bitbucket URL, username, and password, then execute the server to start interacting with your Bitbucket resources.

Key features of Bitbucket MCP?

  • Safe operations with no DELETE commands to prevent data loss.
  • Integration with AI assistants like Cursor for seamless interaction with Bitbucket.
  • Tools for listing repositories, fetching pull requests, and managing comments and tasks.

Use cases of Bitbucket MCP?

  1. Automating repository management tasks.
  2. Enhancing AI assistant capabilities for Bitbucket interactions.
  3. Streamlining pull request reviews and comments.

FAQ from Bitbucket MCP?

  • Is Bitbucket MCP safe to use?

Yes, it does not perform any destructive operations, ensuring data safety.

  • How do I set up Bitbucket MCP?

You can set it up using NPX or by installing it globally with npm, followed by configuring the necessary environment variables.

  • Can I integrate it with AI tools?

Yes, it is designed to work with AI assistants like Cursor.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MatanYemini
Star
3
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago