Atlassian Bitbucket IntegrationAtlassian Bitbucket Integration

Remote
Scanned

Access and manage your Bitbucket repositories, pull requests, and commits directly from AI assistants. Enhance your workflow by integrating Bitbucket data seamlessly into your AI interactions. Utilize a customizable server to connect your AI systems with Atlassian Bitbucket securely and efficiently.

Tools

list_workspaces

List Bitbucket workspaces accessible to the authenticated user, with optional pagination. PURPOSE: Discover available workspaces and retrieve their slugs, names, and basic metadata. Essential for finding the correct 'workspaceSlug' needed as input for repository-related tools (list_repositories, get_repository, list_pull_requests, get_pull_request). WHEN TO USE: - To find the 'workspaceSlug' for a known workspace name. - To explore all workspaces you have access to. - To get a high-level overview before diving into specific repositories. - When you don't know the exact slug required by other tools. WHEN NOT TO USE: - When you already have the 'workspaceSlug'. - When you need detailed information about a *single* workspace (use 'get_workspace'). - When you need repository or pull request information (use repository/pull_request tools with a known 'workspaceSlug'). RETURNS: Formatted list of workspace memberships, including workspace name, slug, UUID, your permission level, and access dates. Includes pagination details if applicable. EXAMPLES: - List all accessible workspaces: {} - Paginate results: { limit: 10, cursor: "some-cursor-value" } ERRORS: - Authentication failures: Check Bitbucket credentials. - No workspaces found: You may not have access to any workspaces.

get_workspace

Get detailed information about a specific Bitbucket workspace using its slug. PURPOSE: Retrieves comprehensive metadata for a *known* workspace, including UUID, name, type, creation date, and links to related resources like repositories and projects. WHEN TO USE: - When you need full details about a *specific* workspace and you already know its 'workspaceSlug'. - After using 'list_workspaces' to identify the target workspace slug. - To get quick links to a workspace's repositories, projects, or members page. WHEN NOT TO USE: - When you don't know the workspace slug (use 'list_workspaces' first). - When you only need a list of workspaces (use 'list_workspaces'). - When you need information about repositories *within* the workspace (use repository tools). RETURNS: Detailed workspace information including slug, name, UUID, type, creation date, and links. Fetches all available details by default. EXAMPLES: - Get details for a workspace: { workspaceSlug: "my-dev-team" } ERRORS: - Workspace not found: Verify the 'workspaceSlug' is correct and exists. - Permission errors: Ensure you have access to view the specified workspace.

list_repositories

List repositories within a specific Bitbucket workspace, with optional filtering and pagination. Requires 'workspaceSlug'. PURPOSE: Discover repositories within a given workspace and retrieve their slugs, names, owners, and basic metadata. Essential for finding the 'repoSlug' needed for repository or pull request details tools. WHEN TO USE: - To find the 'repoSlug' for a known repository name within a specific workspace. - To explore all repositories within a known workspace ('workspaceSlug' is required). - To filter repositories based on name ('query'), your role ('role'), or sort them ('sort'). - Before using 'get_repository' or pull request tools if the 'repoSlug' is unknown. WHEN NOT TO USE: - When you don't know the 'workspaceSlug' (use 'list_workspaces' first). - When you already have the 'repoSlug' and need full details (use 'get_repository'). - When you need pull request information (use pull request tools). RETURNS: Formatted list of repositories including name, full name, owner, description, privacy status, dates, and URL. Includes pagination details if applicable. EXAMPLES: - List repositories in a workspace: { workspaceSlug: "my-team" } - Filter by name fragment: { workspaceSlug: "my-team", query: "backend-api" } - Filter by your role: { workspaceSlug: "my-team", role: "contributor" } - Sort by last update (descending): { workspaceSlug: "my-team", sort: "-updated_on" } - Paginate results: { workspaceSlug: "my-team", limit: 10, cursor: "next-page-token" } ERRORS: - Workspace not found: Verify the 'workspaceSlug' is correct. - Authentication failures: Check Bitbucket credentials. - No repositories found: Workspace might be empty, filters too restrictive, or permissions lacking.

get_repository

Get detailed information about a specific Bitbucket repository using its workspace and repository slugs. Requires 'workspaceSlug' and 'repoSlug'. PURPOSE: Retrieves comprehensive metadata for a *known* repository, including UUID, owner, description, language, size, creation/update dates, and links. WHEN TO USE: - When you need full details about a *specific* repository and you know its 'workspaceSlug' and 'repoSlug'. - After using 'list_repositories' to identify the target repository slugs. - To get repository metadata before analyzing its pull requests or content. WHEN NOT TO USE: - When you don't know the 'workspaceSlug' or 'repoSlug' (use 'list_workspaces' and/or 'list_repositories' first). - When you only need a list of repositories (use 'list_repositories'). - When you need pull request information (use pull request tools). RETURNS: Detailed repository information including name, full name, UUID, description, language, size, owner, dates, and links. Fetches all available details by default. EXAMPLES: - Get details for a repository: { workspaceSlug: "my-team", repoSlug: "backend-api" } ERRORS: - Repository not found: Verify the 'workspaceSlug' and 'repoSlug' are correct and the repository exists. - Permission errors: Ensure you have access to view the specified repository.

View 3 more tools

Installation

Configuration

Enable debug logging

API token for Atlassian API access

Your Atlassian site name, e.g., 'your-instance' for 'your-instance.atlassian.net'

Your Atlassian account email address

Security
secureInvariant LabsInvariant

Monthly Tool Calls

78

Deployed from

Local

No

Published

3/24/2025