Schema | Bitbucket MCP

Bitbucket MCP

Describes the environment variables required to run the server.

Name	Required	Description
`BITBUCKET_EMAIL`	Yes	Your Atlassian account email
`BITBUCKET_API_TOKEN`	Yes	Bitbucket App Password (from account → App passwords)
`BITBUCKET_WORKSPACE`	Yes	Full workspace URL or slug (e.g. my-workspace)

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
search_by_jira_idA	Search Bitbucket for PRs and commits related to a Jira issue ID. Finds PRs where the ID appears in the title or source branch name, and commits where it appears in the message.
search_by_pr_titleA	Search pull requests by keyword in the title. Returns PR details, description, comments, and changed files.
get_changed_filesB	Get the list of files changed in a pull request or commit, with per-file line add/remove counts.
get_diffA	Get the full unified diff for a pull request or commit. Diffs larger than 50,000 characters are truncated at a line boundary.
get_file_contentA	Get the full content of a file at a given branch name or commit hash. If no ref is given, the repository's default branch is used.
get_commit_history_for_fileB	Get the commit history for a specific file, showing who changed it and how frequently.
get_related_prsA	Find other pull requests that touched the same files as a given PR or commit. Useful for discovering related work and potential conflict areas.
list_reposB	List all repositories in the configured Bitbucket workspace.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SamtheIII/Bitbucket-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server