Bitbucket Server MCP

Created By
kartikpatpatwingifya year ago
MCP (Model Context Protocol) server for Bitbucket Server Pull Request management
Overview

what is Bitbucket Server MCP?

Bitbucket Server MCP is a Model Context Protocol server designed for managing pull requests in Bitbucket Server. It provides tools and resources to interact with the Bitbucket Server API through the MCP protocol.

how to use Bitbucket Server MCP?

To use Bitbucket Server MCP, you can install it via Smithery or manually using npm. After installation, configure the server settings in your VSCode MCP settings file and ensure you have the required environment variables set up.

key features of Bitbucket Server MCP?

  • Create, retrieve, merge, and decline pull requests.
  • Add comments to pull requests.
  • Fetch review history and diffs for pull requests.
  • Push multiple files in a single commit to a repository branch.

use cases of Bitbucket Server MCP?

  1. Automating pull request management in Bitbucket Server.
  2. Integrating Bitbucket Server with CI/CD pipelines.
  3. Enhancing collaboration among development teams through efficient pull request handling.

FAQ from Bitbucket Server MCP?

  • What are the requirements to run Bitbucket Server MCP?

You need Node.js version 16 or higher.

  • How do I install Bitbucket Server MCP?

You can install it via Smithery or manually using npm commands.

  • What authentication methods are supported?

You can use a personal access token or basic authentication with a username and password.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kartikpatpatwingify
Star
0
Language
JavaScript
License
Apache-2.0 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)

4 hours ago
Gpt Scrambler

a day ago