x=hub

your toolset

    build deployment
    sign in

    s3

    mcpkey · package
    com.pulsemcp/s3 · v0.0.5
    deploy just this

    MCP server for AWS S3 with fine-grained tool control and S3-compatible endpoint support.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    #!/usr/bin/env bash
# s3 (com.pulsemcp/s3), recipe baremetal (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-s3.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz

[Unit]
Description=MCP server s3 (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/s3
WorkingDirectory=/var/lib/mcp/s3
ExecStart=/opt/mcp/my-agent/bin/s3.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/s3

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_REGION -e AWS_ENDPOINT_URL -e S3_FORCE_PATH_STYLE -e S3_BUCKET -e S3_ENABLED_TOOLGROUPS -e S3_ENABLED_TOOLS -e S3_DISABLED_TOOLS -e SKIP_HEALTH_CHECKS node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y [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-18T12:35:33+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:
  s3:
    image: node:22-alpine
    command:
    - sh
    - -c
    - npx -y supergateway@4 --stdio 'npx -y [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:
      AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}
      AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}
      AWS_REGION: ${AWS_REGION}
      AWS_ENDPOINT_URL: ${AWS_ENDPOINT_URL}
      S3_FORCE_PATH_STYLE: ${S3_FORCE_PATH_STYLE}
      S3_BUCKET: ${S3_BUCKET}
      S3_ENABLED_TOOLGROUPS: ${S3_ENABLED_TOOLGROUPS}
      S3_ENABLED_TOOLS: ${S3_ENABLED_TOOLS}
      S3_DISABLED_TOOLS: ${S3_DISABLED_TOOLS}
      SKIP_HEALTH_CHECKS: ${SKIP_HEALTH_CHECKS}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T12:35:33+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: s3
  namespace: mcp
  labels: &id001
    app: s3
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: s3
        image: node:22-alpine
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: AWS_ACCESS_KEY_ID
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: AWS_ACCESS_KEY_ID
        - name: AWS_SECRET_ACCESS_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: AWS_SECRET_ACCESS_KEY
        - name: AWS_REGION
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: AWS_REGION
        - name: AWS_ENDPOINT_URL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: AWS_ENDPOINT_URL
        - name: S3_FORCE_PATH_STYLE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: S3_FORCE_PATH_STYLE
        - name: S3_BUCKET
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: S3_BUCKET
        - name: S3_ENABLED_TOOLGROUPS
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: S3_ENABLED_TOOLGROUPS
        - name: S3_ENABLED_TOOLS
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: S3_ENABLED_TOOLS
        - name: S3_DISABLED_TOOLS
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: S3_DISABLED_TOOLS
        - name: SKIP_HEALTH_CHECKS
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: SKIP_HEALTH_CHECKS
        command:
        - sh
        - -c
        - npx -y supergateway@4 --stdio 'npx -y [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: s3
  namespace: mcp
spec:
  selector:
    app: s3
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T12:35:33+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:
  s3:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: s3
      image: node:22-alpine
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: AWS_ACCESS_KEY_ID
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: AWS_ACCESS_KEY_ID
      - name: AWS_SECRET_ACCESS_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: AWS_SECRET_ACCESS_KEY
      - name: AWS_REGION
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: AWS_REGION
      - name: AWS_ENDPOINT_URL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: AWS_ENDPOINT_URL
      - name: S3_FORCE_PATH_STYLE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: S3_FORCE_PATH_STYLE
      - name: S3_BUCKET
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: S3_BUCKET
      - name: S3_ENABLED_TOOLGROUPS
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: S3_ENABLED_TOOLGROUPS
      - name: S3_ENABLED_TOOLS
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: S3_ENABLED_TOOLS
      - name: S3_DISABLED_TOOLS
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: S3_DISABLED_TOOLS
      - name: SKIP_HEALTH_CHECKS
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: SKIP_HEALTH_CHECKS
      command:
      - sh
      - -c
      - npx -y supergateway@4 --stdio 'npx -y [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
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, AWS_ENDPOINT_URL, S3_FORCE_PATH_STYLE, S3_BUCKET, S3_ENABLED_TOOLGROUPS, S3_ENABLED_TOOLS, S3_DISABLED_TOOLS, SKIP_HEALTH_CHECKS. Fill them in before you deploy.

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

    azure
    deploy to azuretemplate

    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 [email protected]
# env: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, AWS_ENDPOINT_URL, S3_FORCE_PATH_STYLE, S3_BUCKET, S3_ENABLED_TOOLGROUPS, S3_ENABLED_TOOLS, S3_DISABLED_TOOLS, SKIP_HEALTH_CHECKS
    {
  "mcpServers": {
    "s3": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "${AWS_ACCESS_KEY_ID}",
        "AWS_SECRET_ACCESS_KEY": "${AWS_SECRET_ACCESS_KEY}",
        "AWS_REGION": "${AWS_REGION}",
        "AWS_ENDPOINT_URL": "${AWS_ENDPOINT_URL}",
        "S3_FORCE_PATH_STYLE": "${S3_FORCE_PATH_STYLE}",
        "S3_BUCKET": "${S3_BUCKET}",
        "S3_ENABLED_TOOLGROUPS": "${S3_ENABLED_TOOLGROUPS}",
        "S3_ENABLED_TOOLS": "${S3_ENABLED_TOOLS}",
        "S3_DISABLED_TOOLS": "${S3_DISABLED_TOOLS}",
        "SKIP_HEALTH_CHECKS": "${SKIP_HEALTH_CHECKS}"
      }
    }
  }
}
    #!/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 s3 -e "AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID}" -e "AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY}" -e "AWS_REGION=${AWS_REGION}" -e "AWS_ENDPOINT_URL=${AWS_ENDPOINT_URL}" -e "S3_FORCE_PATH_STYLE=${S3_FORCE_PATH_STYLE}" -e "S3_BUCKET=${S3_BUCKET}" -e "S3_ENABLED_TOOLGROUPS=${S3_ENABLED_TOOLGROUPS}" -e "S3_ENABLED_TOOLS=${S3_ENABLED_TOOLS}" -e "S3_DISABLED_TOOLS=${S3_DISABLED_TOOLS}" -e "SKIP_HEALTH_CHECKS=${SKIP_HEALTH_CHECKS}" -- npx -y [email protected]

    {
  "mcpServers": {
    "s3": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "${AWS_ACCESS_KEY_ID}",
        "AWS_SECRET_ACCESS_KEY": "${AWS_SECRET_ACCESS_KEY}",
        "AWS_REGION": "${AWS_REGION}",
        "AWS_ENDPOINT_URL": "${AWS_ENDPOINT_URL}",
        "S3_FORCE_PATH_STYLE": "${S3_FORCE_PATH_STYLE}",
        "S3_BUCKET": "${S3_BUCKET}",
        "S3_ENABLED_TOOLGROUPS": "${S3_ENABLED_TOOLGROUPS}",
        "S3_ENABLED_TOOLS": "${S3_ENABLED_TOOLS}",
        "S3_DISABLED_TOOLS": "${S3_DISABLED_TOOLS}",
        "SKIP_HEALTH_CHECKS": "${SKIP_HEALTH_CHECKS}"
      }
    }
  }
}
    {
  "servers": {
    "s3": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "${AWS_ACCESS_KEY_ID}",
        "AWS_SECRET_ACCESS_KEY": "${AWS_SECRET_ACCESS_KEY}",
        "AWS_REGION": "${AWS_REGION}",
        "AWS_ENDPOINT_URL": "${AWS_ENDPOINT_URL}",
        "S3_FORCE_PATH_STYLE": "${S3_FORCE_PATH_STYLE}",
        "S3_BUCKET": "${S3_BUCKET}",
        "S3_ENABLED_TOOLGROUPS": "${S3_ENABLED_TOOLGROUPS}",
        "S3_ENABLED_TOOLS": "${S3_ENABLED_TOOLS}",
        "S3_DISABLED_TOOLS": "${S3_DISABLED_TOOLS}",
        "SKIP_HEALTH_CHECKS": "${SKIP_HEALTH_CHECKS}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: com.pulsemcp/s3
    • not probed yet: tools unpinned, ingest lists them

    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.