bitbucket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | No | Base URL for Jira (e.g., https://yourcompany.atlassian.net). Required along with JIRA_API_TOKEN to enable the Jira tool. | |
| JIRA_API_TOKEN | No | Jira API token with read:jira-work scope. Required along with JIRA_BASE_URL to enable the Jira tool. | |
| ATLASSIAN_EMAIL | Yes | Your Atlassian account email address (required by Bitbucket API authentication). | |
| BITBUCKET_API_TOKEN | Yes | Atlassian API token with read:repository:bitbucket and read:pullrequest:bitbucket scopes. | |
| BITBUCKET_REPO_SLUG | No | Default Bitbucket repository slug to use when not specified in tool arguments. | |
| BITBUCKET_WORKSPACE | No | Default Bitbucket workspace to use when not specified in tool arguments. | |
| REVIEW_CHECKLIST_PATH | No | Path to a custom markdown file containing the review checklist. If missing or empty, the default checklist is used. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pull_requestsA | List pull requests in a Bitbucket Cloud repository. |
| get_diffA | Fetch the unified diff for a pull request. |
| post_commentA | Post a comment on a pull request. Provide path and line to attach it to a specific line of the diff. |
| get_pull_requestA | Title, description, author, state, and branches for one pull request. The description is what the change claims to do, which is what a review measures it against. |
| get_diffstatA | Which files a pull request touches and how many lines each gained or lost, without the diff itself. Use this first on a large pull request to decide what is worth reading. |
| get_fileA | Read a whole file at the pull request's source commit. A diff shows changed lines but not the code around them, so use this when a hunk cannot be judged on its own. |
| get_commentsA | Read existing comments on a pull request, so a review does not repeat points someone already raised. Inline comments carry the file and line they sit on. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_pull_request | Fetch a pull request diff and review it against the checklist. |
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/EnesPolovina/bitbucket-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server