x=hub

your toolset

    build deployment
    sign in

    Slack (Archived)

    mcpother official
    io.docker.mcp/slack · vb4ee623039a6
    deploy just this

    Interact with Slack Workspaces over the Slack API.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    #!/usr/bin/env bash
    # slack (io.docker.mcp/slack), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-slack.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-slack -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp/slack
    
    [Unit]
    Description=MCP server slack (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/slack
    WorkingDirectory=/var/lib/mcp/slack
    ExecStart=/opt/mcp/my-agent/bin/slack.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/slack
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    docker run --rm -p 127.0.0.1:8101:8000 -e SLACK_BOT_TOKEN mcp/slack
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T06:08:43+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:
      slack:
        image: mcp/slack
        ports:
        - 127.0.0.1:8101:8000
        restart: unless-stopped
        x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
          HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
          instead.'
        environment:
          SLACK_BOT_TOKEN: ${SLACK_BOT_TOKEN}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T06:08:43+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: slack
      namespace: mcp
      labels: &id001
        app: slack
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: slack
            image: mcp/slack
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: SLACK_BOT_TOKEN
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: SLACK_BOT_TOKEN
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: slack
      namespace: mcp
    spec:
      selector:
        app: slack
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T06:08:43+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:
      slack:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: slack
          image: mcp/slack
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: SLACK_BOT_TOKEN
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: SLACK_BOT_TOKEN
    
    # 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: SLACK_BOT_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
    docker run -i --rm -e SLACK_BOT_TOKEN mcp/slack
    {
      "mcpServers": {
        "slack": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "SLACK_BOT_TOKEN",
            "mcp/slack"
          ],
          "env": {
            "SLACK_BOT_TOKEN": "${SLACK_BOT_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 slack -e "SLACK_BOT_TOKEN=${SLACK_BOT_TOKEN}" -- docker run -i --rm -e SLACK_BOT_TOKEN mcp/slack
    
    {
      "mcpServers": {
        "slack": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "SLACK_BOT_TOKEN",
            "mcp/slack"
          ],
          "env": {
            "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}"
          }
        }
      }
    }
    {
      "servers": {
        "slack": {
          "type": "stdio",
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "SLACK_BOT_TOKEN",
            "mcp/slack"
          ],
          "env": {
            "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}"
          }
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.docker.mcp/slack
    
    • not probed yet: tools unpinned, ingest lists them

    tools

    Probe result: faileddocker: the container exited: Please set SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-17 14:54 local-mac-vm docker failed gvisor docker: the container exited: Please set SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables