x=hub

your toolset

    build deployment
    sign in

    taskflow-mcp

    projectother official scanned
    io.github.pinkpixel-dev/taskflow-mcp · v
    deploy just this

    A task management Model Context Protocol (MCP) server that helps AI assistants break down user requests into manageable tasks with subtasks, dependencies, and notes. Enforces a structured workflow with user approval steps.

    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/taskflow:main https://github.com/pinkpixel-dev/taskflow-mcp.git#main
    
    #!/usr/bin/env bash
    # taskflow (io.github.pinkpixel-dev/taskflow-mcp), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-taskflow.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-taskflow -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp-local/taskflow:main
    
    [Unit]
    Description=MCP server taskflow (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/taskflow
    WorkingDirectory=/var/lib/mcp/taskflow
    ExecStart=/opt/mcp/my-agent/bin/taskflow.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/taskflow
    
    [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 taskflow https://github.com/pinkpixel-dev/taskflow-mcp.git#main
    docker run --rm -p 127.0.0.1:8101:8000 taskflow
    
    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-18T06:10:23+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:
      taskflow:
        build:
          context: https://github.com/pinkpixel-dev/taskflow-mcp.git#main
        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.'
    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-18T06:10:23+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: taskflow
      namespace: mcp
      labels: &id001
        app: taskflow
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: taskflow
            image: CHANGE_ME
            ports:
            - containerPort: 8000
              name: http
            env: []
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: taskflow
      namespace: mcp
    spec:
      selector:
        app: taskflow
      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-18T06:10:23+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:
      taskflow:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: taskflow
          image: CHANGE_ME
          ports:
          - containerPort: 8000
            name: http
          env: []
    
    # helm install my-agent helm/my-agent -n mcp
    

    Scanned github.com/pinkpixel-dev/taskflow-mcp at 95b1d5fb0a7c with [email protected][email protected] on 2026-10-17 before the build: 12 dependencies, 40 known vulnerabilities (1 critical, 25 high, 12 medium, 2 low), nothing in the code that looks malicious.

    in the cloud

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

    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.

    connect to it

    copy what your client needs
    {
      "mcpServers": {
        "taskflow": {
          "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 taskflow -- CHANGE_ME
    
    {
      "mcpServers": {
        "taskflow": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    {
      "servers": {
        "taskflow": {
          "type": "stdio",
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.pinkpixel-dev/taskflow-mcp
    
    • not probed yet: tools unpinned, ingest lists them
    • no tested recipe for target 'local' yet: build it from https://github.com/pinkpixel-dev/taskflow-mcp by hand, or wait for the worker

    tools

    Probe result: faileddocker: sandbox: docker build: Dockerfile:14 -------------------- 12 | WORKDIR /app 13 | 14 | >>> COPY --from=builder /app/dist /app/dist 15 | COPY --from=builder /app/package.json /app/package.json 16 | COPY --from=builder /app/package-lock.json /app/package-lock.json -------------------- ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref pcnkb67uozf07pt7gpyfaqs68::bykrtl0hz4e2rmao9l8yojl1g: "/app/dist": not found

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-17 20:06 local-mac-vm docker failed gvisor docker: sandbox: docker build: Dockerfile:14 -------------------- 12 | WORKDIR /app 13 | 14 | >>> COPY --from=builder /app/dist /app/dist 15 | COPY --from=build…