Bitbucket is a Git-based source code repository hosting service owned by Atlassian. It enables teams to plan projects, collaborate on code, test, and deploy.
Why this server?
Enables interaction with Bitbucket Cloud and Server APIs, providing tools for listing and retrieving repositories, managing pull requests, and working with repository content.
Why this server?
Provides tools for managing Bitbucket Server pull requests, including creating, retrieving, merging, and declining PRs, adding comments, retrieving diffs, and managing reviews.
Why this server?
Allows AI assistants to interact with Bitbucket repositories, including listing repositories, accessing pull requests, viewing commit information, and exploring workspaces.
Why this server?
Allows access to Bitbucket repositories and data through SQL queries.
Why this server?
Provides access to Bitbucket repositories, pull requests and issues through relational SQL models.
Why this server?
Provides SQL-based read-only access to Bitbucket repositories and data.
Why this server?
Enables SQL-based access to Bitbucket repositories, allowing queries of code repositories and related metadata.
Why this server?
Allows querying Bitbucket repositories, issues, and pull requests through SQL queries.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver integration.
Why this server?
Enables querying of SAS Data Sets containing Bitbucket data using SQL.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Bitbucket data.
Why this server?
Provides read-only access to Bitbucket repository data.
Why this server?
Enables querying Bitbucket repositories and related data through SQL.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Allows querying Bitbucket repositories, pull requests, and issues using SQL.
Why this server?
Provides SQL-based access to Bitbucket repositories, pull requests, issues, and other version control data.
Why this server?
Provides read-only access to Bitbucket repository and project data via SQL models.
Why this server?
Allows reading Bitbucket repositories, pull requests, and other Git data through SQL.
Why this server?
Provides access to Bitbucket repository data through relational SQL models, with tools for listing tables, retrieving column information, and executing SQL queries.
Why this server?
Allows accessing Bitbucket repository and project data through SQL queries.
Why this server?
Enables querying Bitbucket repositories, commits, and project data through SQL
Why this server?
Listed as a supported data source that can be integrated with the MCP server for data access.
Why this server?
Provides access to Bitbucket repository data through SQL-based tools for listing tables, retrieving column information, and executing SELECT queries.
Why this server?
Listed as a supported data source for accessing Bitbucket repositories and related data.
Why this server?
Provides SQL-based access to Bitbucket repositories, pull requests, and project data.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver, enabling data querying capabilities.
Why this server?
Listed as a supported data source for integration, allowing access to Bitbucket data through the MCP server.
Why this server?
Allows querying of Bitbucket data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver, allowing for data retrieval from Bitbucket repositories.
Why this server?
Allows querying of Bitbucket repositories, pull requests, and other data through SQL-based access.
Why this server?
Provides access to Bitbucket repository data by exposing it as queryable SQL tables through the MCP server.
Why this server?
Allows SQL-based access to Bitbucket repositories, issues, and pull requests.
Why this server?
Provides read access to Bitbucket repository data through SQL interfaces, enabling natural language querying of code repositories.
Why this server?
Provides tools for repository management (creating, deleting, searching), branch operations, file handling (read, write, delete), issue tracking (creating, deleting issues), and pull request creation in Bitbucket repositories.
Why this server?
Enables querying of Bitbucket repositories, pull requests, issues, and other code management data through a SQL interface.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Enables access to Bitbucket repositories, pull requests, and issues through SQL models.
Why this server?
Allows querying Bitbucket repository and project data using SQL.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Bitbucket data.
Why this server?
Provides SQL-based access to Bitbucket repositories, issues, and other development workflow data.
Why this server?
Allows querying Bitbucket repositories, issues, and pull requests.
Why this server?
Enables access to Bitbucket repositories, pull requests, and other version control data.
Why this server?
Listed as a supported data source that can be accessed through CData JDBC Driver and exposed via the MCP server.
Why this server?
Allows access to repository and code management data from Bitbucket.
Why this server?
Provides access to Bitbucket data by exposing it as a relational SQL model queryable through natural language.
Why this server?
Included in the list of supported sources for data retrieval through the MCP server.
Why this server?
Provides access to Bitbucket repository data, allowing retrieval of code, commits, and pull request information through natural language questions.
Why this server?
Offers read-only access to Bitbucket repositories, commits, pull requests, and other version control data.
Why this server?
Enables access to Bitbucket repositories, pull requests, issues and other Git data through SQL queries.
Why this server?
Allows querying Bitbucket repository and project data through SQL interfaces.
Why this server?
Bitbucket repository management for deploying applications from Bitbucket repositories to Dokploy
Why this server?
Provides tools for interacting with the Bitbucket API, supporting both Bitbucket Cloud and Bitbucket Server. Enables management of pull requests (creating, updating, listing, approving, commenting), handling code reviews, working with branches, and viewing diffs.
Why this server?
Provides read-only access to Bitbucket repositories, enabling queries for code repositories, pull requests, issues, and other development resources.
Why this server?
Provides comprehensive access to Bitbucket Cloud API features for managing repositories, pull requests, issues, branches, pipelines, deployments, webhooks, and more. Supports automation of pull request workflows including creation, approval, merging and commenting.
Why this server?
Provides tools for querying Bitbucket repositories, including repository info, commits, diffs, branches, tags, pull requests, and file/directory content for both public and private repositories.
Why this server?
Provides access to repository information, branch management, Pull Request operations, file content retrieval, file creation and editing, and Pipelines integration