x=hub

your toolset

    build deployment
    sign in

    atlassian-dc-mcp-bitbucket

    mcpkey · package
    io.github.b1ff/atlassian-dc-mcp-bitbucket · v0.38.0
    deploy just this

    MCP server for Atlassian Bitbucket Data Center - interact with repositories and code

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    # once, as root:
    # as_mcp DIR COMMAND...: runs COMMAND as the mcp user in DIR, its home, sandboxed as the
    # units are: a package's install scripts can write to DIR only, as the server later can
    as_mcp() {
      local dir="$1"; shift
      systemd-run --quiet --wait --pipe --collect --uid=mcp --gid=mcp \
        -p WorkingDirectory="$dir" -p Environment=HOME="$dir" -p ReadWritePaths="$dir" \
        -p NoNewPrivileges=true -p ProtectSystem=strict -p ProtectHome=true -p PrivateTmp=true \
        -- "$@" </dev/null
    }
    install -d -m 0750 -o mcp -g mcp /var/lib/mcp/atlassian-dc-mcp-bitbucket
    # atlassian-dc-mcp-bitbucket: its packages, installed whole before its unit starts (no session installs)
    # npx takes a half-installed tree for installed: a rerun starts them afresh
    systemctl stop mcp-my-agent-atlassian-dc-mcp-bitbucket.service 2>/dev/null || true
    as_mcp /var/lib/mcp/atlassian-dc-mcp-bitbucket rm -rf /var/lib/mcp/atlassian-dc-mcp-bitbucket/.npm/_npx
    as_mcp /var/lib/mcp/atlassian-dc-mcp-bitbucket npx --yes --package=@atlassian-dc-mcp/[email protected] -- true
    as_mcp /var/lib/mcp/atlassian-dc-mcp-bitbucket npx --yes --package=supergateway@4 -- true
    
    #!/usr/bin/env bash
    # atlassian-dc-mcp-bitbucket (io.github.b1ff/atlassian-dc-mcp-bitbucket), recipe baremetal (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-atlassian-dc-mcp-bitbucket.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec npx -y supergateway@4 --stdio 'npx -y @atlassian-dc-mcp/[email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz
    
    [Unit]
    Description=MCP server atlassian-dc-mcp-bitbucket (toolset my-agent), generated by Hub
    After=network-online.target
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/atlassian-dc-mcp-bitbucket
    WorkingDirectory=/var/lib/mcp/atlassian-dc-mcp-bitbucket
    ExecStart=/opt/mcp/my-agent/bin/atlassian-dc-mcp-bitbucket.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/atlassian-dc-mcp-bitbucket
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e ATLASSIAN_DC_MCP_CONFIG_FILE -e BITBUCKET_HOST -e BITBUCKET_API_BASE_PATH -e BITBUCKET_API_TOKEN node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y @atlassian-dc-mcp/[email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T20:33:37+00:00).
    # Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
    #   cp .env.example .env    # fill the ${VAR}s
    #   docker compose up -d && bash smoke.sh
    # Remote servers are not here: clients reach them directly (see clients/).
    name: mcp-my-agent
    services:
      atlassian-dc-mcp-bitbucket:
        image: node:22-alpine
        command:
        - sh
        - -c
        - npx -y supergateway@4 --stdio 'npx -y @atlassian-dc-mcp/[email protected]' --outputTransport streamableHttp
          --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
        ports:
        - 127.0.0.1:8101:8000
        volumes:
        - npm-cache:/root/.npm
        healthcheck:
          test:
          - CMD-SHELL
          - wget -qO- http://127.0.0.1:8000/healthz || exit 1
          interval: 30s
          timeout: 5s
          retries: 5
          start_period: 2m
        restart: unless-stopped
        environment:
          ATLASSIAN_DC_MCP_CONFIG_FILE: ${ATLASSIAN_DC_MCP_CONFIG_FILE}
          BITBUCKET_HOST: ${BITBUCKET_HOST}
          BITBUCKET_API_BASE_PATH: ${BITBUCKET_API_BASE_PATH}
          BITBUCKET_API_TOKEN: ${BITBUCKET_API_TOKEN}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T20:33:37+00:00).
    #   kubectl create namespace mcp
    #   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
    #   kubectl apply -f kubernetes.yaml
    # Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
    # with auth in front before exposing any of them.
    apiVersion: v1
    kind: Namespace
    metadata:
      name: mcp
    ---
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: atlassian-dc-mcp-bitbucket
      namespace: mcp
      labels: &id001
        app: atlassian-dc-mcp-bitbucket
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: atlassian-dc-mcp-bitbucket
            image: node:22-alpine
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: ATLASSIAN_DC_MCP_CONFIG_FILE
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: ATLASSIAN_DC_MCP_CONFIG_FILE
            - name: BITBUCKET_HOST
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: BITBUCKET_HOST
            - name: BITBUCKET_API_BASE_PATH
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: BITBUCKET_API_BASE_PATH
            - name: BITBUCKET_API_TOKEN
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: BITBUCKET_API_TOKEN
            args:
            - sh
            - -c
            - npx -y supergateway@4 --stdio 'npx -y @atlassian-dc-mcp/[email protected]' --outputTransport
              streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint
              /healthz
            readinessProbe:
              httpGet:
                path: /healthz
                port: http
              initialDelaySeconds: 10
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: atlassian-dc-mcp-bitbucket
      namespace: mcp
    spec:
      selector:
        app: atlassian-dc-mcp-bitbucket
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T20:33:37+00:00).
    # Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
    # Each server under `servers` is one Deployment + Service; the keys after it configure
    # upstream charts a worker verified.
    servers:
      atlassian-dc-mcp-bitbucket:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: atlassian-dc-mcp-bitbucket
          image: node:22-alpine
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: ATLASSIAN_DC_MCP_CONFIG_FILE
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: ATLASSIAN_DC_MCP_CONFIG_FILE
          - name: BITBUCKET_HOST
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: BITBUCKET_HOST
          - name: BITBUCKET_API_BASE_PATH
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: BITBUCKET_API_BASE_PATH
          - name: BITBUCKET_API_TOKEN
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: BITBUCKET_API_TOKEN
          args:
          - sh
          - -c
          - npx -y supergateway@4 --stdio 'npx -y @atlassian-dc-mcp/[email protected]' --outputTransport streamableHttp
            --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
          readinessProbe:
            httpGet:
              path: /healthz
              port: http
            initialDelaySeconds: 10
    
    # helm install my-agent helm/my-agent -n mcp
    

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb

    The form opens with CHANGE_ME for each value you supply: ATLASSIAN_DC_MCP_CONFIG_FILE, BITBUCKET_HOST, BITBUCKET_API_BASE_PATH, BITBUCKET_API_TOKEN. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    npx -y @atlassian-dc-mcp/[email protected]
    # env: ATLASSIAN_DC_MCP_CONFIG_FILE, BITBUCKET_HOST, BITBUCKET_API_BASE_PATH, BITBUCKET_API_TOKEN
    {
      "mcpServers": {
        "atlassian-dc-mcp-bitbucket": {
          "command": "npx",
          "args": [
            "-y",
            "@atlassian-dc-mcp/[email protected]"
          ],
          "env": {
            "ATLASSIAN_DC_MCP_CONFIG_FILE": "${ATLASSIAN_DC_MCP_CONFIG_FILE}",
            "BITBUCKET_HOST": "${BITBUCKET_HOST}",
            "BITBUCKET_API_BASE_PATH": "${BITBUCKET_API_BASE_PATH}",
            "BITBUCKET_API_TOKEN": "${BITBUCKET_API_TOKEN}"
          }
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add atlassian-dc-mcp-bitbucket -e "ATLASSIAN_DC_MCP_CONFIG_FILE=${ATLASSIAN_DC_MCP_CONFIG_FILE}" -e "BITBUCKET_HOST=${BITBUCKET_HOST}" -e "BITBUCKET_API_BASE_PATH=${BITBUCKET_API_BASE_PATH}" -e "BITBUCKET_API_TOKEN=${BITBUCKET_API_TOKEN}" -- npx -y @atlassian-dc-mcp/[email protected]
    
    {
      "mcpServers": {
        "atlassian-dc-mcp-bitbucket": {
          "command": "npx",
          "args": [
            "-y",
            "@atlassian-dc-mcp/[email protected]"
          ],
          "env": {
            "ATLASSIAN_DC_MCP_CONFIG_FILE": "${ATLASSIAN_DC_MCP_CONFIG_FILE}",
            "BITBUCKET_HOST": "${BITBUCKET_HOST}",
            "BITBUCKET_API_BASE_PATH": "${BITBUCKET_API_BASE_PATH}",
            "BITBUCKET_API_TOKEN": "${BITBUCKET_API_TOKEN}"
          }
        }
      }
    }
    {
      "servers": {
        "atlassian-dc-mcp-bitbucket": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@atlassian-dc-mcp/[email protected]"
          ],
          "env": {
            "ATLASSIAN_DC_MCP_CONFIG_FILE": "${ATLASSIAN_DC_MCP_CONFIG_FILE}",
            "BITBUCKET_HOST": "${BITBUCKET_HOST}",
            "BITBUCKET_API_BASE_PATH": "${BITBUCKET_API_BASE_PATH}",
            "BITBUCKET_API_TOKEN": "${BITBUCKET_API_TOKEN}"
          }
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.b1ff/atlassian-dc-mcp-bitbucket
    
    • not probed yet: tools unpinned, ingest lists them

    tools

    Probe result: needs authdocker: credentials=placeholder: no MCP server found (:8000/mcp: HTTP 404: MCPError: MCP server process failed; :8000/: HTTP 404: MCPError: Not Found) [supergateway] Modern HTTP adapter error: SdkError: Connection closed before a response was produced | [supergateway] Child stderr: npm error process terminated | [supergateway] Child stderr: npm error signal SIGTERM | [supergateway] Child stderr: npm error A complete log of this run can be found in: <path> | throw new Error( | …`${ATLASSIAN_DC_MCP_CONFIG_FILE_ENV_VAR} must be an absolute path: ${filePath}`); ^ Error: ATLASSIAN_DC_MCP_CONFIG_FILE must be an absolute path: <secret> at EnvFileSource.getExplicitFilePath (file://<path>:27:19) at EnvFileSource.loadFile (file://<path>:32:39) at EnvFileSource.initialize (file://<path>:12:14) at DefaultConfigRegistry.initialize (file://<path>:13:32) at initializeRuntimeConfig (file://<path>:6:14) at file://<path>:8:1 at ModuleJob.run (node:internal/modules/esm/module_job:343:25) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:681:26) at async file://<path>:6:3 [supergateway] Child stderr: Node.js v22.23.3 [supergateway] Child exited: code=1, signal=null; baremetal: same crash as docker

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-18 18:44 local-mac-vm docker needs auth gvisor docker: credentials=placeholder: no MCP server found (:8000/mcp: HTTP 404: MCPError: MCP server process failed; :8000/: HTTP 404: MCPError: Not Found) [supergat…