Install
$ agentstack add mcp-jishadmt-bitbucket-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
MCP Bitbucket Review Server
This is an MCP server for LLMs to use capabilities of bitbucket to it's code review workflows.
Installation
> [!IMPORTANT] > You need python 3.10 or above for this to work.
Install from pip:
pip install mcp-bitbucket-review
Configuration in Cursor
- Go to
File->Preferences->Cursor Settings->MCP & Integrations.
- Add a new MCP server.
- Add the bitbucket server MCP from the following to the mcpServers object of mcp.json:
```jsonc { "mcpServers": { // ... your rest of the MCP servers "bitbucket": { "command": "mcp-bitbucket-review-server", "env": { "BITBUCKETEMAIL": "YOURBITBUCKETEMAIL", "BITBUCKETAPITOKEN": "YOURBITBUCKETAPITOKEN" } } } }
- Save the settings.
Usage sample
Open new chat and give following prompt:
> Review pull request
Code Review Checklist
You can provide a custom code review checklist to be used during the review process. The checklist is read from a file and can have both general guidelines and guidelines specific to each repository.
Checklist file structure
The checklist file is a plain text file with sections for each repository. A section starts with the repository name in square brackets (e.g., [my-repo]). A special section named [general] can be used for guidelines that apply to all repositories.
Here is an example of a checklist file:
[general]
Ensure code is well-documented.
Check for any commented-out code that should be removed.
[my-awesome-repo]
Follow the "Awesome Repo" coding style.
Make sure to update the `awesome-spec.json` file.
[another-repo]
All new features must be covered by integration tests.
Configuration
To use the checklist, you need to set the BITBUCKET_CODE_REVIEW_CHECKLIST environment variable to the absolute path of your checklist file.
You can add this to your mcp.json configuration file:
{
"mcpServers": {
// ... your rest of the MCP servers
"bitbucket": {
"command": "mcp-bitbucket-review-server",
"env": {
// ... other environment variables
"BITBUCKET_CODE_REVIEW_CHECKLIST": "C:\\path\\to\\your\\checklist.txt"
}
}
}
}
Get API token from bitbucket
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click on button labelled
Create API token with scopes
- Give scopes and store the API token. Make sure you give the following scopes to the API token:
`` read:pullrequest:bitbucket write:pullrequest:bitbucket read:repository:bitbucket ``
Happy coding!
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: JishadMT
- Source: JishadMT/bitbucket-mcp
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.