Bitbucket MCP Server vs Repowise
A side-by-side look at the Bitbucket MCP Server and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bitbucket MCP Server for version control work as a local process; choose Repowise for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bitbucket MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_TRANSPORT, BITBUCKET_ACCESS_TOKEN, BITBUCKET_EMAIL, BITBUCKET_USERNAME, BITBUCKET_CLIENT_ID, BITBUCKET_CLIENT_SECRET, BITBUCKET_DEFAULT_WORKSPACE, LLM_PROVIDER. - You want tools like
get_current_user, list_pull_requests, get_pull_request.
Choose Repowise when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 55/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | MCP_TRANSPORTBITBUCKET_ACCESS_TOKENBITBUCKET_EMAILBITBUCKET_USERNAMEBITBUCKET_CLIENT_IDBITBUCKET_CLIENT_SECRETBITBUCKET_DEFAULT_WORKSPACELLM_PROVIDER | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 7,893 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Bitbucket MCP Server | View Repowise |
Tools & capabilities
Bitbucket MCP Server tools 10
get_current_userAuthenticated user.list_pull_requestsList PRs (filter by state/query).get_pull_requestFetch a PR by id.create_pull_requestOpen a PR.update_pull_requestEdit an open PR title and/or description.get_pull_request_diffRaw unified diff.get_pull_request_filesChanged files + line stats.get_pull_request_commentsPR comments.comment_pull_requestAdd a (optionally inline) comment.analyze_pull_requestAI review returning a standard `ReviewResult`.
Repowise tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Bitbucket MCP Server
{
"mcpServers": {
"bitbucket-mcp-server": {
"command": "npx",
"args": [
"-y",
"@droplinkperformance/bitbucket-mcp-server"
],
"env": {
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"BITBUCKET_ACCESS_TOKEN": "YOUR_BITBUCKET_ACCESS_TOKEN_HERE",
"BITBUCKET_EMAIL": "YOUR_BITBUCKET_EMAIL_HERE",
"BITBUCKET_USERNAME": "YOUR_BITBUCKET_USERNAME_HERE",
"BITBUCKET_CLIENT_ID": "YOUR_BITBUCKET_CLIENT_ID_HERE",
"BITBUCKET_CLIENT_SECRET": "YOUR_BITBUCKET_CLIENT_SECRET_HERE",
"BITBUCKET_DEFAULT_WORKSPACE": "YOUR_BITBUCKET_DEFAULT_WORKSPACE_HERE",
"LLM_PROVIDER": "YOUR_LLM_PROVIDER_HERE"
}
}
}
}
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
Bitbucket MCP Server is categorized under Version Control and uses a local stdio subprocess. Repowise belongs to Version Control and uses a local stdio subprocess. Pick Bitbucket MCP Server for version control work and Repowise for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Bitbucket MCP Server has no declared pricing — check the project's own site. Repowise is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bitbucket-mcp-server and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bitbucket MCP Server has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,893 GitHub stars.