x=hub

your toolset

    build deployment
    sign in

    xbbg MCP

    mcpother
    io.github.underloam/xbbg-mcp · v1.5.1
    deploy just this

    Local Bloomberg tools for xbbg users.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # once, as root:
    docker build -t mcp-local/xbbg:latest https://github.com/underloam/xbbg.git#:apps/xbbg-mcp
    
    #!/usr/bin/env bash
    # xbbg (io.github.underloam/xbbg-mcp), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-xbbg.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-xbbg -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp-local/xbbg:latest
    
    [Unit]
    Description=MCP server xbbg (toolset my-agent), generated by Hub
    After=network-online.target docker.service
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    SupplementaryGroups=docker
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/xbbg
    WorkingDirectory=/var/lib/mcp/xbbg
    ExecStart=/opt/mcp/my-agent/bin/xbbg.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/xbbg
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    docker build -t xbbg https://github.com/underloam/xbbg.git#:apps/xbbg-mcp
    docker run --rm -p 127.0.0.1:8101:8000 -e XBBG_MCP_LIB_DIR -e XBBG_MCP_HOST -e XBBG_MCP_PORT -e XBBG_MCP_AUTH_METHOD -e XBBG_MCP_MAX_ROWS -e XBBG_MCP_MAX_CELLS -e XBBG_MCP_MAX_METADATA_PROPERTIES -e XBBG_MCP_MAX_METADATA_BYTES -e XBBG_MCP_MAX_STRING_CHARS -e XBBG_MCP_MAX_STRING_BYTES -e XBBG_MCP_MAX_RESULT_BYTES xbbg
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T05:38:16+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:
      xbbg:
        build:
          context: https://github.com/underloam/xbbg.git#:apps/xbbg-mcp
        ports:
        - 127.0.0.1:8101:8000
        restart: unless-stopped
        x-note: 'CHANGE_ME: built from the repository''s Dockerfile, assuming it serves streamable HTTP at
          :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.'
        environment:
          XBBG_MCP_LIB_DIR: ${XBBG_MCP_LIB_DIR}
          XBBG_MCP_HOST: ${XBBG_MCP_HOST}
          XBBG_MCP_PORT: ${XBBG_MCP_PORT}
          XBBG_MCP_AUTH_METHOD: ${XBBG_MCP_AUTH_METHOD}
          XBBG_MCP_MAX_ROWS: ${XBBG_MCP_MAX_ROWS}
          XBBG_MCP_MAX_CELLS: ${XBBG_MCP_MAX_CELLS}
          XBBG_MCP_MAX_METADATA_PROPERTIES: ${XBBG_MCP_MAX_METADATA_PROPERTIES}
          XBBG_MCP_MAX_METADATA_BYTES: ${XBBG_MCP_MAX_METADATA_BYTES}
          XBBG_MCP_MAX_STRING_CHARS: ${XBBG_MCP_MAX_STRING_CHARS}
          XBBG_MCP_MAX_STRING_BYTES: ${XBBG_MCP_MAX_STRING_BYTES}
          XBBG_MCP_MAX_RESULT_BYTES: ${XBBG_MCP_MAX_RESULT_BYTES}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T05:38:16+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: xbbg
      namespace: mcp
      labels: &id001
        app: xbbg
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: xbbg
            image: CHANGE_ME
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: XBBG_MCP_LIB_DIR
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_LIB_DIR
            - name: XBBG_MCP_HOST
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_HOST
            - name: XBBG_MCP_PORT
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_PORT
            - name: XBBG_MCP_AUTH_METHOD
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_AUTH_METHOD
            - name: XBBG_MCP_MAX_ROWS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_ROWS
            - name: XBBG_MCP_MAX_CELLS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_CELLS
            - name: XBBG_MCP_MAX_METADATA_PROPERTIES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_METADATA_PROPERTIES
            - name: XBBG_MCP_MAX_METADATA_BYTES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_METADATA_BYTES
            - name: XBBG_MCP_MAX_STRING_CHARS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_STRING_CHARS
            - name: XBBG_MCP_MAX_STRING_BYTES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_STRING_BYTES
            - name: XBBG_MCP_MAX_RESULT_BYTES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: XBBG_MCP_MAX_RESULT_BYTES
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: xbbg
      namespace: mcp
    spec:
      selector:
        app: xbbg
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T05:38:16+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:
      xbbg:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: xbbg
          image: CHANGE_ME
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: XBBG_MCP_LIB_DIR
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_LIB_DIR
          - name: XBBG_MCP_HOST
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_HOST
          - name: XBBG_MCP_PORT
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_PORT
          - name: XBBG_MCP_AUTH_METHOD
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_AUTH_METHOD
          - name: XBBG_MCP_MAX_ROWS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_ROWS
          - name: XBBG_MCP_MAX_CELLS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_CELLS
          - name: XBBG_MCP_MAX_METADATA_PROPERTIES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_METADATA_PROPERTIES
          - name: XBBG_MCP_MAX_METADATA_BYTES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_METADATA_BYTES
          - name: XBBG_MCP_MAX_STRING_CHARS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_STRING_CHARS
          - name: XBBG_MCP_MAX_STRING_BYTES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_STRING_BYTES
          - name: XBBG_MCP_MAX_RESULT_BYTES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: XBBG_MCP_MAX_RESULT_BYTES
    
    # 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: XBBG_MCP_LIB_DIR, XBBG_MCP_HOST, XBBG_MCP_PORT, XBBG_MCP_AUTH_METHOD, XBBG_MCP_MAX_ROWS, XBBG_MCP_MAX_CELLS, XBBG_MCP_MAX_METADATA_PROPERTIES, XBBG_MCP_MAX_METADATA_BYTES, XBBG_MCP_MAX_STRING_CHARS, XBBG_MCP_MAX_STRING_BYTES, XBBG_MCP_MAX_RESULT_BYTES. Fill them in before you deploy.

    Koyeb builds the repository's Dockerfile from branch main; change the branch in the form if the default one has another name.

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

    cloud run

    Cloud Shell clones the repository, builds its Dockerfile and deploys it to Cloud Run.

    Cloud Run sends requests to $PORT (8080); the recipe expects :8000, so the server has to read PORT, or set the container port on the service afterwards.

    Set XBBG_MCP_LIB_DIR, XBBG_MCP_HOST, XBBG_MCP_PORT, XBBG_MCP_AUTH_METHOD, XBBG_MCP_MAX_ROWS, XBBG_MCP_MAX_CELLS, XBBG_MCP_MAX_METADATA_PROPERTIES, XBBG_MCP_MAX_METADATA_BYTES, XBBG_MCP_MAX_STRING_CHARS, XBBG_MCP_MAX_STRING_BYTES, XBBG_MCP_MAX_RESULT_BYTES on the service afterwards: the button asks only for what the repository's own app.json lists.

    connect to it

    copy what your client needs
    {
      "mcpServers": {
        "xbbg": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    #!/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 xbbg -- CHANGE_ME
    
    {
      "mcpServers": {
        "xbbg": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    {
      "servers": {
        "xbbg": {
          "type": "stdio",
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.underloam/xbbg-mcp
    
    • not probed yet: tools unpinned, ingest lists them
    • no recipe for target 'local': fill the files by hand

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.