Bitbucket MCP Server A19f4667

MCP安全风控

提供方 SvitEM · 包名 @bitbucket-mcp/server

安全风控 stdio · 本地进程 Token 社区 / 第三方 Claude DesktopClaude
查看接入方式

Bitbucket MCP服务器是一个安全、自托管的模型上下文协议(MCP)服务器,专为企业、隔离网络和私有网络环境设计,提供高性能和零运行时依赖。

一句话选型结论

按资料字段整理

Bitbucket MCP Server A19f4667 属于安全风控类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 19 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量19暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

企业安全Rust本地部署自托管零依赖Rust开发Bitbucket集成

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
npx @bitbucket-mcp/server

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 19 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 19 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Bitbucket MCP Server A19f4667当前 19 stdio · 本地进程 本地部署 有 2026-05-17
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方SvitEM上游标注的维护方 SvitEM
分类安全风控本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@bitbucket-mcp/server · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

14.7 KB
来自项目仓库与上游目录的原文,未做删改

Bitbucket MCP Server - Enterprise Secure Edition

Secure, self-hosted Model Context Protocol (MCP) server for Bitbucket Server/Data Center — designed for enterprise, air-gapped, and private network environments. Built in Rust for maximum security, performance, and zero runtime dependencies.


🎯 Why This MCP Server?

Feature This Server Other MCP Servers
Deployment Single binary Node.js + npm dependencies
Security Rust memory safety JavaScript runtime vulnerabilities
Dependencies Zero at runtime 100+ npm packages
Air-gapped ✅ Fully supported ❌ Requires npm registry
SSL/TLS Custom CA support Limited
Permissions Granular READ/WRITE/DELETE All-or-nothing
Audit Trail Security-audited dependencies Supply chain risks

Perfect For:

  • 🔒 Enterprise environments with strict security policies
  • 🏢 Corporate networks behind firewalls
  • ✈️ Air-gapped systems without internet access
  • 🛡️ Compliance requirements (SOC2, ISO27001, GDPR)
  • 📦 Minimal attack surface requirements

🚀 Quick Start

Install (30 seconds)```bash

Global install

npm install -g @bitbucket-mcp/server

Or run without install

npx @bitbucket-mcp/server


### Configure Claude Desktop

**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
**Linux**: `~/.config/Claude/claude_desktop_config.json````json
{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": ["-y", "@bitbucket-mcp/server"],
      "env": {
        "BITBUCKET_BASE_URL": "https://bitbucket.your-company.com",
        "BITBUCKET_USERNAME": "service-account",
        "BITBUCKET_PASSWORD": "your-personal-access-token",
        "BITBUCKET_SSL_VERIFY": "true",
        "BITBUCKET_ALLOW_READ": "true",
        "BITBUCKET_ALLOW_WRITE": "false",
        "BITBUCKET_ALLOW_DELETE": "false"
      }
    }
  }
}

🔐 Security Features

Enterprise-Grade Security

Feature Description
Memory Safety Rust prevents buffer overflows, use-after-free, data races
Zero Supply Chain Risk No runtime npm dependencies to compromise
Audited Dependencies All Rust crates scanned with cargo-audit
Granular Permissions Separate READ/WRITE/DELETE controls
Self-Signed SSL Support for internal CA certificates
No Telemetry Zero data collection, fully offline-capable

Security Configuration```json

{
"env": {
// Require SSL verification (default: true)
"BITBUCKET_SSL_VERIFY": "true",

// Read-only mode for maximum security
"BITBUCKET_ALLOW_READ": "true",
"BITBUCKET_ALLOW_WRITE": "false",
"BITBUCKET_ALLOW_DELETE": "false",

// Use personal access token instead of password
"BITBUCKET_PASSWORD": "your-pat-token"

}
}


### Compliance Ready

- ✅ **SOC2**: Audit trails, access controls, encryption in transit
- ✅ **ISO27001**: Secure development, dependency management
- ✅ **GDPR**: No data retention, on-premise deployment
- ✅ **HIPAA**: Private network deployment supported

---

## 🛠️ Available Tools (19 MCP Tools)

### Projects

| Tool | Description | Permission |
|------|-------------|------------|
| `list_projects` | List all projects with pagination | READ |
| `get_project` | Get project details by key | READ |

### Repositories

| Tool | Description | Permission |
|------|-------------|------------|
| `list_repos` | List repositories in a project | READ |
| `get_repo` | Get repository details | READ |

### Pull Requests

| Tool | Description | Permission |
|------|-------------|------------|
| `list_prs` | List pull requests with filters (state, author) | READ |
| `get_pr` | Get pull request details | READ |
| `create_pr` | Create a new pull request | WRITE |
| `update_pr` | Update pull request title/description | WRITE |
| `merge_pr` | Merge a pull request | DELETE |
| `decline_pr` | Decline a pull request | DELETE |
| `pr_diff` | Get pull request diff | READ |
| `pr_changes` | Get pull request file changes | READ |

### Branches

| Tool | Description | Permission |
|------|-------------|------------|
| `list_branches` | List repository branches | READ |
| `create_branch` | Create a new branch from ref | WRITE |
| `compare_branches` | Compare commits between branches | READ |

### Commits

| Tool | Description | Permission |
|------|-------------|------------|
| `list_commits` | List repository commits with filters | READ |
| `get_commit` | Get commit details | READ |

### Files

| Tool | Description | Permission |
|------|-------------|------------|
| `list_files` | Browse repository files | READ |
| `get_file_content` | Get file content at specific commit | READ |

---

## 📦 Deployment Options

### Option 1: NPM (Recommended)```bash
npm install -g @bitbucket-mcp/server

Option 2: Direct Binary (Air-Gapped)

Download prebuilt binary for your platform:

Platform Binary Size
macOS Intel bitbucket-mcp-darwin-x64 ~15 MB
macOS ARM bitbucket-mcp-darwin-arm64 ~12 MB
Linux x64 bitbucket-mcp-linux-x64 ~18 MB
Linux ARM64 bitbucket-mcp-linux-arm64 ~16 MB
Windows x64 bitbucket-mcp-win32-x64.exe ~20 MB
# Download and run
chmod +x bitbucket-mcp-linux-x64
./bitbucket-mcp-linux-x64

Option 3: Docker (Coming Soon)```dockerfile

FROM scratch
COPY bitbucket-mcp-linux-x64 /bitbucket-mcp
ENTRYPOINT ["/bitbucket-mcp"]


---

## 🏢 Enterprise Deployment

### Air-Gapped Installation

1. **Download on internet-connected machine:**```bash
   npm pack @bitbucket-mcp/server
   ```

2. **Transfer to air-gapped system** via secure media

3. **Install offline:**```bash
   npm install -g bitbucket-mcp-server-0.1.0.tgz
   ```

### Corporate Proxy Support```json
{
  "env": {
    "BITBUCKET_BASE_URL": "https://bitbucket.internal.company.com",
    "HTTP_PROXY": "http://proxy.company.com:8080",
    "HTTPS_PROXY": "http://proxy.company.com:8080",
    "NO_PROXY": "localhost,127.0.0.1,.internal.company.com"
  }
}

Service Account Setup```bash

1. Create dedicated service account in Bitbucket

2. Grant minimal required permissions

3. Generate Personal Access Token (PAT)

4. Use in configuration (never commit to git!)


---

## 🔧 Configuration Reference

### Environment Variables

| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `BITBUCKET_BASE_URL` | **Yes** | - | Bitbucket Server base URL |
| `BITBUCKET_API_KEY` | No | - | API Key / PAT for Bearer token authentication (has priority over Basic Auth) |
| `BITBUCKET_USERNAME` | **Yes** | - | Username for Basic Auth (ignored if BITBUCKET_API_KEY is set) |
| `BITBUCKET_PASSWORD` | **Yes** | - | Password or PAT for Basic authentication (ignored if BITBUCKET_API_KEY is set) |
| `BITBUCKET_SSL_VERIFY` | No | `true` | SSL certificate verification |
| `BITBUCKET_ALLOW_READ` | No | `true` | Allow read operations |
| `BITBUCKET_ALLOW_WRITE` | No | `true` | Allow write operations |
| `BITBUCKET_ALLOW_DELETE` | No | `true` | Allow delete operations |

### Permission Modes```json
// Read-only (maximum security)
{ "BITBUCKET_ALLOW_READ": "true", "BITBUCKET_ALLOW_WRITE": "false", "BITBUCKET_ALLOW_DELETE": "false" }

// Developer mode (no delete)
{ "BITBUCKET_ALLOW_READ": "true", "BITBUCKET_ALLOW_WRITE": "true", "BITBUCKET_ALLOW_DELETE": "false" }

// Admin mode (full access)
{ "BITBUCKET_ALLOW_READ": "true", "BITBUCKET_ALLOW_WRITE": "true", "BITBUCKET_ALLOW_DELETE": "true" }

🛡️ Security Best Practices

1. Use Personal Access Tokens```bash

❌ Don't use password

BITBUCKET_PASSWORD="my-actual-password"

✅ Use PAT with minimal scope

BITBUCKET_PASSWORD="pat:read-only-projects-repos"


### 2. Enable Read-Only Mode```json
{
  "env": {
    "BITBUCKET_ALLOW_WRITE": "false",
    "BITBUCKET_ALLOW_DELETE": "false"
  }
}

3. Restrict Network Access```bash

Bind to localhost only (if supported)

Or use firewall rules to restrict access

sudo ufw allow from 127.0.0.1 to any port 3000


### 4. Rotate Credentials```bash
# Rotate PAT every 90 days
# Monitor Bitbucket audit logs for unusual activity

5. Enable SSL Verification```json

{
"env": {
"BITBUCKET_SSL_VERIFY": "true" // Never disable in production
}
}


---

## 🐛 Troubleshooting

### SSL Certificate Errors

**For self-signed/internal CA certificates:**```json
{
  "env": {
    // Option 1: Add to system trust store (recommended)
    // Option 2: Disable verification (NOT recommended for production)
    "BITBUCKET_SSL_VERIFY": "false"
  }
}

⚠️ Warning: Only disable SSL verification for trusted internal servers.

Authentication Failed```bash

Check credentials

curl -u username:password https://bitbucket.example.com/rest/api/1.0/projects

Verify PAT has required permissions

Check user is not locked/suspended


### Connection Refused```bash
# Verify URL includes protocol
BITBUCKET_BASE_URL="https://bitbucket.example.com"  # ✅
BITBUCKET_BASE_URL="bitbucket.example.com"          # ❌

# Test connectivity
curl -I https://bitbucket.example.com

# Check firewall/proxy rules

Permission Denied```json

{
"env": {
// Enable only required permissions
"BITBUCKET_ALLOW_READ": "true",
"BITBUCKET_ALLOW_WRITE": "false",
"BITBUCKET_ALLOW_DELETE": "false"
}
}


---

## 🏗️ Architecture```
┌─────────────────┐     ┌──────────────────┐     ┌─────────────────┐
│  Claude Desktop │────▶│  MCP Server      │────▶│  Bitbucket      │
│  (AI Assistant) │     │  (Rust Binary)   │     │  Server/DC      │
└─────────────────┘     └──────────────────┘     └─────────────────┘
        │                       │                        │
        │                       │                        │
   User Requests          Zero Dependencies        REST API 1.0
   Natural Language         Memory Safe              Basic Auth
                            Single Binary            SSL/TLS

Why Rust?

  • Memory Safety: No buffer overflows, use-after-free, or data races
  • Performance: Native code, no GC pauses
  • Security: Audited dependencies, minimal attack surface
  • Portability: Single static binary, no runtime dependencies

📚 Resources

  • Model Context Protocol Documentation
  • Bitbucket Server REST API
  • Security Best Practices
  • Enterprise Deployment Guide
  • Build Instructions

🤝 Contributing

We welcome contributions! Please see our Contributing Guide for details.

Development```bash

git clone https://github.com/your-org/bitbucket-mcp-server.git
cd bitbucket-mcp-server

Build

cargo build --release

Test

cargo test

Security audit

cargo audit


---

## 🔄 CI/CD & Automated Releases

### Automatic Versioning

При каждом коммите в ветку `main` автоматически:

1. **Dependabot** обновляет зависимости (еженедельно по понедельникам)
2. **Создается новый тег** с инкрементом patch-версии (v0.1.0 → v0.1.1)
3. **Генерируется changelog** на основе Conventional Commits
4. **Публикуется GitHub Release** с бинарниками для всех платформ
5. **Публикация в npm** (при наличии токена `NPM_TOKEN`)

### Conventional Commits

Используйте формат коммитов для автоматического определения типа изменений:```bash
# Новые функции (minor version)
git commit -m "feat: add branch comparison tool"

# Исправления (patch version)
git commit -m "fix: handle SSL certificate errors"

# Обновления зависимостей (patch version)
git commit -m "deps: update tokio to 1.42"

# Документация (не создает релиз)
git commit -m "docs: update README examples"

Workflow Overview```

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Push to main │────▶│ auto-release.yml│────▶│ Create tag │
│ (non-.md) │ │ │ │ (v0.1.0→0.1.1) │
└─────────────────┘ └──────────────────┘ └────────┬────────┘
│
┌─────────────────┐ ┌──────────────────┐ ┌────────▼────────┐
│ npm Publish │◀────│ release.yml │◀────│ GitHub Release │
│ │ │ Build & Test │ │ + Changelog │
└─────────────────┘ └──────────────────┘ └─────────────────┘
```

Required Secrets

Настройте secrets в GitHub Repository Settings → Secrets → Actions:

Secret Description Required
GITHUB_TOKEN Автоматически создается GitHub ✅ Yes
NPM_TOKEN Токен для публикации в npm ❌ Optional

Dependabot Configuration

Dependabot автоматически обновляет:
- Rust зависимости (Cargo.toml) — еженедельно
- npm зависимости (package.json) — еженедельно
- GitHub Actions — еженедельно

Все обновления создаются как Pull Request с лейблами:
- dependencies + rust / javascript / ci/cd
- Группированные обновления для minor/patch версий


📄 License

MIT License - see LICENSE file for details.


🔍 Keywords

MCP server, Model Context Protocol, Bitbucket Server, Bitbucket Data Center, enterprise MCP, secure MCP, self-hosted MCP, air-gapped MCP, on-premise MCP, single binary MCP, Rust MCP server, zero dependencies, private network MCP, corporate MCP, SOC2 compliant, ISO27001 compliant, Atlassian integration, Bitbucket REST API, Claude Desktop MCP, AI integration


Built for enterprise security • Zero runtime dependencies • Air-gapped ready

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Bitbucket MCP Server A19f4667 怎么安装?

在客户端按下面的安装命令接入:npx @bitbucket-mcp/server。对应的包名是 @bitbucket-mcp/server。装完在客户端配置里引用同一个包或端点。

Bitbucket MCP Server A19f4667 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Bitbucket MCP Server A19f4667 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Bitbucket MCP Server A19f4667 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Bitbucket MCP Server A19f4667 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Bitbucket MCP Server A19f4667 能提供哪些能力?

资料显示约 19 个工具;能力标签包括 企业安全、Rust、Claude、自托管。具体工具清单以官方文档为准。

Bitbucket MCP Server A19f4667 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Bitbucket MCP Server A19f4667 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。