Blinkly
Optimize Bitbucket Server pull request management with MCP protocol tools for seamless API integration
Bitbucket Server MCP Server is an essential tool for integrating various AI applications, including Claude Desktop, Continue, and Cursor, with your Bitbucket Server instance. This server acts as a bridge between the Bitbucket API and model context protocols (MCP), enabling seamless interaction and data exchange through a standardized protocol. By leveraging the power of MCP, developers can ensure that their AI applications have consistent access to critical tools and resources from Bitbucket.
Bitbucket Server MCP Server offers robust capabilities for managing pull requests through the MCP protocol. These features include:
Developers can create new pull requests by providing parameters such as project key, repository slug, title, source branch, and target branch. This capability helps streamline the development process and ensures that code changes are reviewed efficiently.
Retrieve comprehensive information about a specific pull request by specifying its ID, project key, and other relevant details. This feature allows developers to gather all necessary context for reviewing or managing pull requests effectively.
Merge pull requests with options like merge-commit, squash, or fast-forward. The server supports these strategies to ensure that the merge process aligns with best practices and project requirements.
Decline a pull request by providing reasons for doing so. This feature helps maintain quality control and ensures that only high-quality changes are merged into the main codebase.
Add comments to pull requests as part of the review process or for clarification purposes. The server allows developers to include detailed feedback directly from an AI application, enhancing collaboration and communication.
Retrieve the difference between the source and target branches (commit diffs) in a pull request by specifying relevant parameters such as project key, repository slug, and PR ID. This capability helps track changes and understand what modifications are being considered for merging.
View the review history of a pull request, including approvals and reviews. This feature provides insight into the decision-making process surrounding each change request.
Bitbucket Server MCP Server is built on top of the Model Context Protocol (MCP) architecture. The server's core functionality revolves around implementing the MCP protocol to facilitate communication between AI applications and Bitbucket Server. Specifically, the server incorporates key libraries such as @modelcontextprotocol/sdk, ensuring that all interactions are consistent and reliable.
To install and set up this MCP server, follow these steps:
Ensure you have Node.js version 16 or higher installed.
Use Smithery for automated installation if needed:
npx -y @smithery/cli install @garc33/bitbucket-server-mcp-server --client claude
Alternatively, perform a manual installation using the following commands:
npm install
Build the server for production use with:
npm run build
Ensure that your environment meets the requirement of Node.js version 16 or higher. You can check the installed version using:
node -v
For a seamless installation, you can use Smithery to manage dependencies and installations effortlessly:
npx -y @smithery/cli install @garc33/bitbucket-server-mcp-server --client claude
This command sets up the server specifically for Claude Desktop, ensuring compliance with its requirements.
Install the necessary dependencies by running:
npm install
The integration provided by Bitbucket Server MCP Server enhances various AI workflows. For instance:
Automated Code Reviews and Pull Request Management
Interactive Development Environment Integration
Bitbucket Server MCP Server supports a wide range of MCP clients, ensuring compatibility across different development and AI frameworks. The following table outlines supported clients:
| MCP Client | Resources | Tools | Prompts | Status |
|---|---|---|---|---|
| Claude Desktop | ✅ | ✅ | ✅ | Full Support |
| Continue | ✅ | ✅ | ✅ | Full Support |
| Cursor | ❌ | ✅ | ❌ | Tools Only |
Claude Desktop: Fully supports creating, reviewing, merging, declining pull requests, and adding comments.
Continue: Similarly integrated for comprehensive pull request management but does not yet support prompts or AI-driven interactions within the development environment.
To ensure optimal performance and compatibility, this section provides a detailed overview of supported environments and configurations:
The server is designed to handle a wide range of use cases, making it ideal for both small and large development teams.
Configuration of Bitbucket Server MCP Server involves setting up environment variables in a VSCode MCP settings file. Here's an example:
{
"mcpServers": {
"bitbucket": {
"command": "node",
"args": ["/path/to/bitbucket-server/build/index.js"],
"env": {
"BITBUCKET_URL": "https://your-bitbucket-server.com",
// Authentication (choose one):
// Option 1: Personal Access Token
"BITBUCKET_TOKEN": "your-access-token",
// Option 2: Username/Password
"BITBUCKET_USERNAME": "your-username",
"BITBUCKET_PASSWORD": "your-password",
// Optional: Default project
"BITBUCKET_DEFAULT_PROJECT": "your-default-project"
}
}
}
}
This configuration ensures secure and efficient communication with your Bitbucket Server instance. Pay special attention to setting up correct authentication mechanisms.
Bitbucket Server MCP Server supports a range of MCP clients, including Claude Desktop, Continue, and Cursor. For more details on client compatibility, refer to the provided matrix in this documentation.
Yes, you can modify the BITBUCKET_DEFAULT_PROJECT environment variable in the configuration file according to your specific needs. This setting does not affect other configurations unless explicitly changed.
The server logs detailed error messages in bitbucket.log. Ensure that your credentials are correct and follow best practices for securing sensitive information like tokens and passwords.
Absolutely. You can specify the merge strategy (merge-commit, squash, or fast-forward) via API calls to achieve the desired outcomes during pull request merging.
Bitbucket Server MCP Server uses Winston for logging. Review the bitbucket.log file for any errors or warnings that can help you diagnose and resolve issues effectively.
Contributions to Bitbucket Server MCP Server are highly welcome! If you wish to contribute, please adhere to the following guidelines:
git clone https://github.com/your-username/bitbucket-server-mcp-server.git
Bitbucket Server MCP Server is part of an extensive ecosystem that includes various tools, resources, and documentation. Explore the official MCP documentation for deeper insights into protocol implementation and advanced features. Additionally, join community forums to connect with other developers facing similar integration challenges.
This comprehensive documentation positions Bitbucket Server MCP Server as a powerful tool for enhancing AI work processes through seamless Integration with Bitbucket Server via Model Context Protocol (MCP).
RuinedFooocus is a local AI image generator and chatbot image server for seamless creative control
Learn to set up MCP Airflow Database server for efficient database interactions and querying airflow data
Simplify MySQL queries with Java-based MysqlMcpServer for easy standard input-output communication
Access NASA APIs for space data, images, asteroids, weather, and exoplanets via MCP integration
Explore CoRT MCP server for advanced self-arguing AI with multi-LLM inference and enhanced evaluation methods
Build stunning one-page websites track engagement create QR codes monetize content easily with Acalytica