Taskfile.yml

version: '3'

tasks:
  scan:
    desc: "Run security scan on a specific MCP server"
    summary: |
      Run Cisco AI Defense mcp-scanner on a specific MCP server configuration.

      Usage:
        task scan -- npx/browserbase-mcp-server
        task scan -- uvx/blender-mcp
        task scan -- npx/sentry-mcp-server

      The server path should be relative to the project root and contain a spec.yaml file.

      Environment variables:
        MCP_SCANNER_ENABLE_LLM=true  - Enable LLM analyzer (requires API key)
        MCP_SCANNER_LLM_API_KEY      - API key for LLM service
    requires:
      vars: [CLI_ARGS]
    vars:
      SERVER_PATH: '{{.CLI_ARGS}}'
      PROTOCOL:
        sh: echo "{{.SERVER_PATH}}" | cut -d'/' -f1
      SERVER_NAME:
        sh: echo "{{.SERVER_PATH}}" | cut -d'/' -f2
    cmds:
      - |
        if [ ! -f "{{.SERVER_PATH}}/spec.yaml" ]; then
          echo "❌ Error: spec.yaml not found at {{.SERVER_PATH}}/spec.yaml"
          exit 1
        fi
      - 'echo "🔍 Scanning MCP server: {{.SERVER_NAME}} ({{.PROTOCOL}})"'
      - |
        # Generate config (outputs JSON with command/args)
        config_json=$(python3 scripts/mcp-scan/generate_mcp_config.py \
          "{{.SERVER_PATH}}/spec.yaml" \
          "{{.PROTOCOL}}" \
          "{{.SERVER_NAME}}")

        command=$(echo "$config_json" | jq -r '.command')
        args=$(echo "$config_json" | jq -r '.args')

        # Run scan using Cisco AI Defense mcp-scanner
        # Note: stderr is redirected to a separate file to avoid corrupting JSON output
        python3 scripts/mcp-scan/run_scan.py "$command" "$args" \
          > "/tmp/mcp-scan-{{.SERVER_NAME}}.json" 2> "/tmp/mcp-scan-{{.SERVER_NAME}}.stderr" || true

        # Show stderr if it exists (for debugging)
        if [ -s "/tmp/mcp-scan-{{.SERVER_NAME}}.stderr" ]; then
          echo "Scanner stderr:"
          cat "/tmp/mcp-scan-{{.SERVER_NAME}}.stderr"
        fi
      - |
        python3 scripts/mcp-scan/process_scan_results.py \
          "/tmp/mcp-scan-{{.SERVER_NAME}}.json" \
          "{{.SERVER_NAME}}" \
          "{{.SERVER_PATH}}/spec.yaml"
      - echo "✅ Scan completed for {{.SERVER_NAME}}"
      - 'echo "📄 Raw results: /tmp/mcp-scan-{{.SERVER_NAME}}.json"'

  scan-all:
    desc: "Run security scan on all MCP servers"
    summary: |
      Run Cisco AI Defense mcp-scanner on all MCP server configurations found in the project.

      This will scan all spec.yaml files found in:
      - npx/*/spec.yaml
      - uvx/*/spec.yaml
      - go/*/spec.yaml
    cmds:
      - |
        echo "🔍 Discovering all MCP server configurations..."
        configs=$(find npx uvx go -name "spec.yaml" -type f 2>/dev/null | sort)
        
        if [ -z "$configs" ]; then
          echo "❌ No MCP server configurations found"
          exit 1
        fi
        
        echo "📋 Found configurations:"
        echo "$configs" | sed 's/^/  - /'
        echo ""
        
        total=$(echo "$configs" | wc -l)
        current=0
        
        for config in $configs; do
          current=$((current + 1))
          server_dir=$(dirname "$config")
          
          echo "🔍 [$current/$total] Scanning: $server_dir"
          task scan -- "$server_dir" || echo "⚠️  Scan failed for $server_dir"
          echo ""
        done
        
        echo "✅ All scans completed!"

  scan-setup:
    desc: "Setup Cisco AI Defense mcp-scanner"
    summary: |
      Install and setup the Cisco AI Defense mcp-scanner tool.
      This only needs to be run once or when the tool needs updating.

      Set MCP_SCANNER_ENABLE_LLM=true for LLM analysis (requires API key).
    cmds:
      - echo "🔧 Setting up Cisco AI Defense mcp-scanner..."
      - uv tool install cisco-ai-mcp-scanner
      - echo "✅ mcp-scanner setup completed"
      - echo "ℹ️  Set MCP_SCANNER_ENABLE_LLM=true for LLM analysis"
      - mcp-scanner --help || true

  scan-clean:
    desc: "Clean up temporary scan files"
    summary: |
      Remove temporary files created during security scans.
    cmds:
      - echo "🧹 Cleaning up temporary scan files..."
      - rm -f /tmp/*mcp-config.json /tmp/mcp-scan-*.json /tmp/mcp-scan-storage
      - echo "✅ Cleanup completed"

  scan-help:
    desc: "Show help for security scanning tasks"
    summary: |
      Display detailed help and examples for using the security scanning tasks.
    cmds:
      - |
        echo "🔒 MCP Security Scanning Tasks (Cisco AI Defense)"
        echo "=================================================="
        echo ""
        echo "Available tasks:"
        echo "  scan        - Run security scan on a specific server"
        echo "  scan-all    - Run security scan on all servers"
        echo "  scan-setup  - Setup mcp-scanner tool (run once)"
        echo "  scan-clean  - Clean up temporary files"
        echo "  scan-help   - Show this help"
        echo ""
        echo "Examples:"
        echo "  task scan -- npx/browserbase-mcp-server"
        echo "  task scan -- uvx/blender-mcp"
        echo "  task scan-all"
        echo "  task scan-setup"
        echo ""
        echo "Environment variables:"
        echo "  MCP_SCANNER_ENABLE_LLM=true  - Enable LLM analyzer"
        echo "  MCP_SCANNER_LLM_API_KEY      - API key for LLM service"
        echo ""
        echo "The scan results will show:"
        echo "  ✅ - No security issues found"
        echo "  ❌ - Security issues found (not allowlisted)"
        echo "  ⚠️  - Security issues found but allowlisted"
        echo ""
        echo "Issue codes use AITech taxonomy (e.g., AITech-8.2 for data exposure)"
        echo "For detailed analysis, check the raw JSON output files in /tmp/"

  build:
    desc: "Generate Dockerfile from MCP server spec"
    summary: |
      Generate a Dockerfile from an MCP server specification.
      
      Usage:
        task build -- npx/context7
        task build -- uvx/mcp-clickhouse
        task build -- go/my-go-server
      
      The server path should be relative to the project root and contain a spec.yaml file.
      Output will be written to stdout by default.
    requires:
      vars: [CLI_ARGS]
    vars:
      SERVER_PATH: '{{.CLI_ARGS}}'
      SPEC_FILE: '{{.SERVER_PATH}}/spec.yaml'
    cmds:
      - |
        if [ ! -f "{{.SPEC_FILE}}" ]; then
          echo "❌ Error: spec.yaml not found at {{.SPEC_FILE}}"
          exit 1
        fi
      - echo "🏗️ Generating Dockerfile for {{.SERVER_PATH}}"
      - build/dockhand build -c "{{.SPEC_FILE}}"

  build-file:
    desc: "Generate Dockerfile from MCP server spec and save to file"
    summary: |
      Generate a Dockerfile from an MCP server specification and save to a file.
      
      Usage:
        task build-file -- npx/context7 Dockerfile
        task build-file -- uvx/mcp-clickhouse my-dockerfile
      
      Arguments:
        1. Server path (e.g., npx/context7)
        2. Output file path (e.g., Dockerfile)
    requires:
      vars: [CLI_ARGS]
    vars:
      ARGS: '{{.CLI_ARGS}}'
      SERVER_PATH:
        sh: echo "{{.ARGS}}" | cut -d' ' -f1
      OUTPUT_FILE:
        sh: echo "{{.ARGS}}" | cut -d' ' -f2
      SPEC_FILE: '{{.SERVER_PATH}}/spec.yaml'
    cmds:
      - |
        if [ ! -f "{{.SPEC_FILE}}" ]; then
          echo "❌ Error: spec.yaml not found at {{.SPEC_FILE}}"
          exit 1
        fi
      - |
        if [ -z "{{.OUTPUT_FILE}}" ]; then
          echo "❌ Error: Output file not specified"
          echo "Usage: task build-file -- <server-path> <output-file>"
          exit 1
        fi
      - echo "🏗️ Generating Dockerfile for {{.SERVER_PATH}} → {{.OUTPUT_FILE}}"
      - build/dockhand build -c "{{.SPEC_FILE}}" -o "{{.OUTPUT_FILE}}"
      - echo "✅ Dockerfile saved to {{.OUTPUT_FILE}}"

  build-tag:
    desc: "Generate Dockerfile with custom tag"
    summary: |
      Generate a Dockerfile from an MCP server specification with a custom tag.
      
      Usage:
        task build-tag -- npx/context7 my-custom-tag:latest
        task build-tag -- uvx/mcp-clickhouse myregistry/image:v1.0.0
      
      Arguments:
        1. Server path (e.g., npx/context7)
        2. Custom tag (e.g., my-custom-tag:latest)
    requires:
      vars: [CLI_ARGS]
    vars:
      ARGS: '{{.CLI_ARGS}}'
      SERVER_PATH:
        sh: echo "{{.ARGS}}" | cut -d' ' -f1
      CUSTOM_TAG:
        sh: echo "{{.ARGS}}" | cut -d' ' -f2-
      SPEC_FILE: '{{.SERVER_PATH}}/spec.yaml'
    cmds:
      - |
        if [ ! -f "{{.SPEC_FILE}}" ]; then
          echo "❌ Error: spec.yaml not found at {{.SPEC_FILE}}"
          exit 1
        fi
      - |
        if [ -z "{{.CUSTOM_TAG}}" ]; then
          echo "❌ Error: Custom tag not specified"
          echo "Usage: task build-tag -- <server-path> <custom-tag>"
          exit 1
        fi
      - echo "🏗️ Generating Dockerfile for {{.SERVER_PATH}} with tag {{.CUSTOM_TAG}}"
      - build/dockhand build -c "{{.SPEC_FILE}}" -t "{{.CUSTOM_TAG}}"

  test-build:
    desc: "Test build an MCP server container"
    summary: |
      Generate Dockerfile and build a container image for testing.
      
      Usage:
        task test-build -- npx/context7
        task test-build -- uvx/mcp-clickhouse
      
      This will:
      1. Generate a Dockerfile
      2. Build the container image
      3. Test that the container runs
    requires:
      vars: [CLI_ARGS]
    vars:
      SERVER_PATH: '{{.CLI_ARGS}}'
      PROTOCOL:
        sh: echo "{{.SERVER_PATH}}" | cut -d'/' -f1
      SERVER_NAME:
        sh: echo "{{.SERVER_PATH}}" | cut -d'/' -f2
      SPEC_FILE: '{{.SERVER_PATH}}/spec.yaml'
      TEST_TAG: 'test-{{.SERVER_NAME}}:latest'
    cmds:
      - |
        if [ ! -f "{{.SPEC_FILE}}" ]; then
          echo "❌ Error: spec.yaml not found at {{.SPEC_FILE}}"
          exit 1
        fi
      - echo "🏗️ Testing build for {{.SERVER_PATH}}"
      - echo "📝 Generating Dockerfile..."
      - build/dockhand build -c "{{.SPEC_FILE}}" -o "Dockerfile.test"
      - echo "🔨 Building container image..."
      - podman build -t "{{.TEST_TAG}}" -f Dockerfile.test .
      - echo "🧪 Testing container..."
      - podman run --rm "{{.TEST_TAG}}" --help || echo "⚠️  Container built but --help failed (this may be expected)"
      - echo "✅ Test build completed for {{.SERVER_NAME}}"
      - echo "🏷️ Image tagged as {{.TEST_TAG}}"
      - rm -f Dockerfile.test

  build-setup:
    desc: "Build and install dockhand CLI"
    summary: |
      Build the dockhand CLI tool from source.
      This needs to be run once or when the tool is updated.
    sources:
      - "cmd/dockhand/**/*.go"
      - "go.mod"
      - "go.sum"
    generates:
      - "build/dockhand"
    cmds:
      - echo "🔧 Building dockhand CLI..."
      - mkdir -p build
      - go build -o build/dockhand ./cmd/dockhand
      - echo "✅ dockhand CLI built successfully"
      - build/dockhand --help

  build-help:
    desc: "Show help for build tasks"
    summary: |
      Display detailed help and examples for using the build tasks.
    cmds:
      - |
        echo "🏗️ MCP Server Build Tasks"
        echo "========================"
        echo ""
        echo "Available tasks:"
        echo "  build        - Generate Dockerfile to stdout"
        echo "  build-file   - Generate Dockerfile and save to file"
        echo "  build-tag    - Generate Dockerfile with custom tag"
        echo "  test-build   - Generate, build, and test container"
        echo "  build-setup  - Build dockhand CLI tool"
        echo "  build-help   - Show this help"
        echo ""
        echo "Examples:"
        echo "  task build -- npx/context7"
        echo "  task build-file -- npx/context7 Dockerfile"
        echo "  task build-tag -- uvx/mcp-clickhouse myregistry/image:v1.0.0"
        echo "  task test-build -- npx/context7"
        echo "  task build-setup"
        echo ""
        echo "Prerequisites:"
        echo "  - Run 'task build-setup' first to build the dockhand CLI"
        echo "  - Ensure podman is running and 'dev' container exists"
        echo ""
        echo "The generated Dockerfiles can be used with:"
        echo "  podman build -t my-image:tag -f Dockerfile ."