Bitbucket MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_EMAIL | Yes | Your Atlassian account email used for authentication. | |
| BITBUCKET_API_TOKEN | Yes | Bitbucket API token with required scopes (read:repository:bitbucket, read:pullrequest:bitbucket, write:pullrequest:bitbucket). | |
| BITBUCKET_WORKSPACE | No | Optional Bitbucket workspace. If omitted, workspace must be specified in each tool call. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_repositoriesA | Lists repositories in a workspace, sorted by most recently updated. |
| list_pull_requestsB | Lists a repository's PRs, filtered by state. |
| get_pull_requestA | Returns full metadata for a PR (description, branches, reviewers, state). |
| get_pull_request_diffB | Returns the PR's full unified diff — the basis for a first-pass review. |
| get_pull_request_commentsB | Lists a PR's existing comments (general and inline). |
| get_pull_request_commitsC | Lists the commits that make up the PR. |
| get_fileA | Reads a file's contents. If |
| list_directoryA | Lists files and directories under a repository path at a commit/branch. Use it to explore the project structure while reviewing a PR. Empty |
| add_pull_request_commentA | WRITE — posts a comment on the PR. Provide |
| approve_pull_requestB | WRITE — records the authenticated user's approval on the PR. |
| request_changes_pull_requestB | WRITE — records the authenticated user's 'request changes' on the PR. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/daniloneto/bitbucket-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server