From 33e03db0d6e18c2f70c88ac47c21dd802f9df573 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 14:21:50 +0000 Subject: [PATCH 01/19] feat: mount MCP servers as local CLIs after gateway starts - Add `start_mcp_gateway.sh`: save CLI manifest (server names + local URLs) to /tmp/gh-aw/mcp-cli/manifest.json before cleanup - Add `mount_mcp_as_cli.sh`: new shell script that reads the manifest, queries each server's tools/list via JSON-RPC, and generates a standalone CLI wrapper script in /tmp/gh-aw/mcp-cli/bin/ (chmod 555) - Add `mcp_cli_mount.go`: Go helpers getMCPCLIServerNames() and generateMCPCLIMountStep() + buildMCPCLIPromptSection() - Add "Mount MCP servers as CLIs" workflow step in compiler_yaml_main_job.go - Inject MCP CLI tools prompt section in unified_prompt_step.go - Update golden test fixtures Agent-Logs-Url: https://github.com/github/gh-aw/sessions/f83b0114-9c57-4701-ac7d-bfa80f07a971 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/ace-editor.lock.yml | 33 ++ .../agent-performance-analyzer.lock.yml | 34 ++ .../workflows/agent-persona-explorer.lock.yml | 35 ++ .../agentic-observability-kit.lock.yml | 34 ++ .github/workflows/ai-moderator.lock.yml | 34 ++ .github/workflows/archie.lock.yml | 34 ++ .github/workflows/artifacts-summary.lock.yml | 33 ++ .github/workflows/audit-workflows.lock.yml | 35 ++ .github/workflows/auto-triage-issues.lock.yml | 33 ++ .github/workflows/blog-auditor.lock.yml | 34 ++ .github/workflows/bot-detection.lock.yml | 33 ++ .github/workflows/brave.lock.yml | 34 ++ .../breaking-change-checker.lock.yml | 33 ++ .github/workflows/changeset.lock.yml | 33 ++ .github/workflows/ci-coach.lock.yml | 34 ++ .github/workflows/ci-doctor.lock.yml | 34 ++ .../claude-code-user-docs-review.lock.yml | 34 ++ .../cli-consistency-checker.lock.yml | 33 ++ .../workflows/cli-version-checker.lock.yml | 34 ++ .github/workflows/cloclo.lock.yml | 37 +++ .../workflows/code-scanning-fixer.lock.yml | 34 ++ .github/workflows/code-simplifier.lock.yml | 33 ++ .../codex-github-remote-mcp-test.lock.yml | 33 ++ .../commit-changes-analyzer.lock.yml | 33 ++ .../constraint-solving-potd.lock.yml | 34 ++ .github/workflows/contribution-check.lock.yml | 33 ++ .../workflows/copilot-agent-analysis.lock.yml | 34 ++ .../copilot-cli-deep-research.lock.yml | 33 ++ .../copilot-pr-merged-report.lock.yml | 34 ++ .../copilot-pr-nlp-analysis.lock.yml | 34 ++ .../copilot-pr-prompt-analysis.lock.yml | 34 ++ .../copilot-session-insights.lock.yml | 34 ++ .github/workflows/craft.lock.yml | 33 ++ .../daily-architecture-diagram.lock.yml | 34 ++ .../daily-assign-issue-to-user.lock.yml | 33 ++ .github/workflows/daily-choice-test.lock.yml | 33 ++ .../workflows/daily-cli-performance.lock.yml | 33 ++ .../workflows/daily-cli-tools-tester.lock.yml | 34 ++ .github/workflows/daily-code-metrics.lock.yml | 34 ++ .../daily-community-attribution.lock.yml | 33 ++ .../workflows/daily-compiler-quality.lock.yml | 35 ++ .../daily-copilot-token-report.lock.yml | 34 ++ .github/workflows/daily-doc-healer.lock.yml | 35 ++ .github/workflows/daily-doc-updater.lock.yml | 35 ++ .github/workflows/daily-fact.lock.yml | 33 ++ .github/workflows/daily-file-diet.lock.yml | 34 ++ .../workflows/daily-firewall-report.lock.yml | 35 ++ .../workflows/daily-function-namer.lock.yml | 35 ++ .../daily-integrity-analysis.lock.yml | 35 ++ .../workflows/daily-issues-report.lock.yml | 34 ++ .../daily-malicious-code-scan.lock.yml | 33 ++ .../daily-mcp-concurrency-analysis.lock.yml | 35 ++ .../daily-multi-device-docs-tester.lock.yml | 34 ++ .github/workflows/daily-news.lock.yml | 35 ++ .../daily-observability-report.lock.yml | 34 ++ .../daily-performance-summary.lock.yml | 34 ++ .github/workflows/daily-regulatory.lock.yml | 33 ++ .../daily-rendering-scripts-verifier.lock.yml | 35 ++ .../workflows/daily-repo-chronicle.lock.yml | 34 ++ .../daily-safe-output-integrator.lock.yml | 33 ++ .../daily-safe-output-optimizer.lock.yml | 35 ++ .../daily-safe-outputs-conformance.lock.yml | 33 ++ .../workflows/daily-secrets-analysis.lock.yml | 33 ++ .../daily-security-red-team.lock.yml | 33 ++ .github/workflows/daily-semgrep-scan.lock.yml | 34 ++ .../daily-syntax-error-quality.lock.yml | 33 ++ .../daily-team-evolution-insights.lock.yml | 33 ++ .github/workflows/daily-team-status.lock.yml | 33 ++ .../daily-testify-uber-super-expert.lock.yml | 34 ++ .../workflows/daily-workflow-updater.lock.yml | 33 ++ .github/workflows/dead-code-remover.lock.yml | 34 ++ .github/workflows/deep-report.lock.yml | 35 ++ .github/workflows/delight.lock.yml | 33 ++ .github/workflows/dependabot-burner.lock.yml | 33 ++ .../workflows/dependabot-go-checker.lock.yml | 33 ++ .github/workflows/dev-hawk.lock.yml | 34 ++ .github/workflows/dev.lock.yml | 34 ++ .../developer-docs-consolidator.lock.yml | 36 ++ .github/workflows/dictation-prompt.lock.yml | 34 ++ .../workflows/discussion-task-miner.lock.yml | 33 ++ .github/workflows/docs-noob-tester.lock.yml | 34 ++ .github/workflows/draft-pr-cleanup.lock.yml | 33 ++ .../duplicate-code-detector.lock.yml | 34 ++ .../example-permissions-warning.lock.yml | 33 ++ .../example-workflow-analyzer.lock.yml | 34 ++ .github/workflows/firewall-escape.lock.yml | 34 ++ .github/workflows/firewall.lock.yml | 33 ++ .../workflows/functional-pragmatist.lock.yml | 33 ++ .../github-mcp-structural-analysis.lock.yml | 34 ++ .../github-mcp-tools-report.lock.yml | 34 ++ .../github-remote-mcp-auth-test.lock.yml | 33 ++ .../workflows/glossary-maintainer.lock.yml | 36 ++ .github/workflows/go-fan.lock.yml | 35 ++ .github/workflows/go-logger.lock.yml | 34 ++ .../workflows/go-pattern-detector.lock.yml | 34 ++ .github/workflows/gpclean.lock.yml | 34 ++ .github/workflows/grumpy-reviewer.lock.yml | 34 ++ .github/workflows/hourly-ci-cleaner.lock.yml | 33 ++ .../workflows/instructions-janitor.lock.yml | 34 ++ .github/workflows/issue-arborist.lock.yml | 33 ++ .github/workflows/issue-monster.lock.yml | 33 ++ .github/workflows/issue-triage-agent.lock.yml | 33 ++ .github/workflows/jsweep.lock.yml | 35 ++ .../workflows/layout-spec-maintainer.lock.yml | 33 ++ .github/workflows/lockfile-stats.lock.yml | 34 ++ .github/workflows/mcp-inspector.lock.yml | 49 +++ .github/workflows/mergefest.lock.yml | 33 ++ .github/workflows/metrics-collector.lock.yml | 34 ++ .../workflows/notion-issue-summary.lock.yml | 34 ++ .github/workflows/org-health-report.lock.yml | 34 ++ .github/workflows/pdf-summary.lock.yml | 35 ++ .github/workflows/plan.lock.yml | 33 ++ .github/workflows/poem-bot.lock.yml | 34 ++ .github/workflows/portfolio-analyst.lock.yml | 35 ++ .../workflows/pr-nitpick-reviewer.lock.yml | 34 ++ .github/workflows/pr-triage-agent.lock.yml | 33 ++ .../prompt-clustering-analysis.lock.yml | 35 ++ .github/workflows/python-data-charts.lock.yml | 35 ++ .github/workflows/q.lock.yml | 36 ++ .github/workflows/refiner.lock.yml | 33 ++ .github/workflows/release.lock.yml | 33 ++ .../workflows/repo-audit-analyzer.lock.yml | 34 ++ .github/workflows/repo-tree-map.lock.yml | 33 ++ .../repository-quality-improver.lock.yml | 35 ++ .github/workflows/research.lock.yml | 34 ++ .github/workflows/safe-output-health.lock.yml | 35 ++ .../schema-consistency-checker.lock.yml | 34 ++ .../schema-feature-coverage.lock.yml | 33 ++ .github/workflows/scout.lock.yml | 39 +++ .../workflows/security-compliance.lock.yml | 33 ++ .github/workflows/security-review.lock.yml | 35 ++ .../semantic-function-refactor.lock.yml | 34 ++ .github/workflows/sergo.lock.yml | 35 ++ .../workflows/slide-deck-maintainer.lock.yml | 35 ++ .../workflows/smoke-agent-all-merged.lock.yml | 33 ++ .../workflows/smoke-agent-all-none.lock.yml | 33 ++ .../smoke-agent-public-approved.lock.yml | 33 ++ .../smoke-agent-public-none.lock.yml | 33 ++ .../smoke-agent-scoped-approved.lock.yml | 33 ++ .../workflows/smoke-call-workflow.lock.yml | 33 ++ .github/workflows/smoke-claude.lock.yml | 38 +++ .github/workflows/smoke-codex.lock.yml | 37 +++ .github/workflows/smoke-copilot-arm.lock.yml | 37 +++ .github/workflows/smoke-copilot.lock.yml | 37 +++ .../smoke-create-cross-repo-pr.lock.yml | 33 ++ .github/workflows/smoke-gemini.lock.yml | 34 ++ .github/workflows/smoke-multi-pr.lock.yml | 33 ++ .github/workflows/smoke-project.lock.yml | 33 ++ .../workflows/smoke-service-ports.lock.yml | 33 ++ .github/workflows/smoke-temporary-id.lock.yml | 33 ++ .github/workflows/smoke-test-tools.lock.yml | 33 ++ .../smoke-update-cross-repo-pr.lock.yml | 34 ++ .../smoke-workflow-call-with-inputs.lock.yml | 33 ++ .../workflows/smoke-workflow-call.lock.yml | 33 ++ .../workflows/stale-repo-identifier.lock.yml | 34 ++ .../workflows/static-analysis-report.lock.yml | 35 ++ .../workflows/step-name-alignment.lock.yml | 34 ++ .github/workflows/sub-issue-closer.lock.yml | 33 ++ .github/workflows/super-linter.lock.yml | 34 ++ .../workflows/technical-doc-writer.lock.yml | 35 ++ .github/workflows/terminal-stylist.lock.yml | 34 ++ .../test-create-pr-error-handling.lock.yml | 34 ++ .github/workflows/test-dispatcher.lock.yml | 33 ++ .../test-project-url-default.lock.yml | 33 ++ .github/workflows/test-workflow.lock.yml | 33 ++ .github/workflows/tidy.lock.yml | 33 ++ .github/workflows/typist.lock.yml | 34 ++ .../workflows/ubuntu-image-analyzer.lock.yml | 33 ++ .github/workflows/unbloat-docs.lock.yml | 36 ++ .github/workflows/update-astro.lock.yml | 33 ++ .github/workflows/video-analyzer.lock.yml | 33 ++ .../weekly-blog-post-writer.lock.yml | 35 ++ .../weekly-editors-health-check.lock.yml | 34 ++ .../workflows/weekly-issue-summary.lock.yml | 34 ++ .../weekly-safe-outputs-spec-review.lock.yml | 33 ++ .github/workflows/workflow-generator.lock.yml | 33 ++ .../workflow-health-manager.lock.yml | 33 ++ .../workflows/workflow-normalizer.lock.yml | 34 ++ .../workflow-skill-extractor.lock.yml | 33 ++ actions/setup/sh/mount_mcp_as_cli.sh | 309 ++++++++++++++++++ actions/setup/sh/start_mcp_gateway.sh | 16 + pkg/workflow/compiler_yaml_main_job.go | 3 + pkg/workflow/mcp_cli_mount.go | 140 ++++++++ pkg/workflow/prompt_constants.go | 1 + pkg/workflow/prompts/mcp_cli_tools_prompt.md | 26 ++ .../basic-copilot.golden | 33 ++ .../with-imports.golden | 33 ++ pkg/workflow/unified_prompt_step.go | 7 + 188 files changed, 6649 insertions(+) create mode 100755 actions/setup/sh/mount_mcp_as_cli.sh create mode 100644 pkg/workflow/mcp_cli_mount.go create mode 100644 pkg/workflow/prompts/mcp_cli_tools_prompt.md diff --git a/.github/workflows/ace-editor.lock.yml b/.github/workflows/ace-editor.lock.yml index 32ef931ae78..56d3deaaa67 100644 --- a/.github/workflows/ace-editor.lock.yml +++ b/.github/workflows/ace-editor.lock.yml @@ -189,6 +189,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_3b0f91d4e2fcc9d9_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -411,6 +438,12 @@ jobs: } } GH_AW_MCP_CONFIG_20e6f2291791c37c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agent-performance-analyzer.lock.yml b/.github/workflows/agent-performance-analyzer.lock.yml index ecafc156c9a..910c1ab54b0 100644 --- a/.github/workflows/agent-performance-analyzer.lock.yml +++ b/.github/workflows/agent-performance-analyzer.lock.yml @@ -161,6 +161,34 @@ jobs: Tools: add_comment(max:10), create_issue(max:5), create_discussion(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -727,6 +755,12 @@ jobs: } } GH_AW_MCP_CONFIG_d9c841c74e91f91c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agent-persona-explorer.lock.yml b/.github/workflows/agent-persona-explorer.lock.yml index 41b173ebb2c..81a9e86b57c 100644 --- a/.github/workflows/agent-persona-explorer.lock.yml +++ b/.github/workflows/agent-persona-explorer.lock.yml @@ -169,6 +169,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -680,6 +709,12 @@ jobs: } } GH_AW_MCP_CONFIG_5ae1cb25093c05e1_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agentic-observability-kit.lock.yml b/.github/workflows/agentic-observability-kit.lock.yml index ebf498667b9..f7fe0933080 100644 --- a/.github/workflows/agentic-observability-kit.lock.yml +++ b/.github/workflows/agentic-observability-kit.lock.yml @@ -165,6 +165,34 @@ jobs: Tools: create_issue, create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -687,6 +715,12 @@ jobs: } } GH_AW_MCP_CONFIG_072a2a06a610d9da_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ai-moderator.lock.yml b/.github/workflows/ai-moderator.lock.yml index 49555223573..38b4697951c 100644 --- a/.github/workflows/ai-moderator.lock.yml +++ b/.github/workflows/ai-moderator.lock.yml @@ -203,6 +203,34 @@ jobs: Tools: add_labels, hide_comment(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -670,6 +698,12 @@ jobs: } } GH_AW_MCP_CONFIG_9cfc9d89b67815ed_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/archie.lock.yml b/.github/workflows/archie.lock.yml index 469cc14b252..4af0967db42 100644 --- a/.github/workflows/archie.lock.yml +++ b/.github/workflows/archie.lock.yml @@ -206,6 +206,34 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -688,6 +716,12 @@ jobs: } } GH_AW_MCP_CONFIG_1aecf03afd94e396_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/artifacts-summary.lock.yml b/.github/workflows/artifacts-summary.lock.yml index 0d36efee638..771f72d78cf 100644 --- a/.github/workflows/artifacts-summary.lock.yml +++ b/.github/workflows/artifacts-summary.lock.yml @@ -154,6 +154,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -568,6 +595,12 @@ jobs: } } GH_AW_MCP_CONFIG_089491fa939a5dc3_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/audit-workflows.lock.yml b/.github/workflows/audit-workflows.lock.yml index 200489f7112..4d1773dfcbe 100644 --- a/.github/workflows/audit-workflows.lock.yml +++ b/.github/workflows/audit-workflows.lock.yml @@ -177,6 +177,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -749,6 +778,12 @@ jobs: } } GH_AW_MCP_CONFIG_dc00d5b21f5764cd_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index 7b279f549cb..f5881637756 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -172,6 +172,33 @@ jobs: Tools: create_discussion, add_labels(max:10), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -604,6 +631,12 @@ jobs: } } GH_AW_MCP_CONFIG_17800b88a17b863b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/blog-auditor.lock.yml b/.github/workflows/blog-auditor.lock.yml index 51f721f5959..36362009e56 100644 --- a/.github/workflows/blog-auditor.lock.yml +++ b/.github/workflows/blog-auditor.lock.yml @@ -164,6 +164,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -606,6 +634,12 @@ jobs: } } GH_AW_MCP_CONFIG_582c8214644aae0b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/bot-detection.lock.yml b/.github/workflows/bot-detection.lock.yml index 86ab6b0092d..da74a6b1804 100644 --- a/.github/workflows/bot-detection.lock.yml +++ b/.github/workflows/bot-detection.lock.yml @@ -162,6 +162,33 @@ jobs: Tools: create_issue, update_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -652,6 +679,12 @@ jobs: } } GH_AW_MCP_CONFIG_fbf069f346e13146_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/brave.lock.yml b/.github/workflows/brave.lock.yml index a2e6dd30c37..b8fc92d2418 100644 --- a/.github/workflows/brave.lock.yml +++ b/.github/workflows/brave.lock.yml @@ -196,6 +196,34 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `brave-search` — run `brave-search --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -634,6 +662,12 @@ jobs: } } GH_AW_MCP_CONFIG_bdc9ed36a6083efb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/breaking-change-checker.lock.yml b/.github/workflows/breaking-change-checker.lock.yml index aec82c35007..b96c3411a79 100644 --- a/.github/workflows/breaking-change-checker.lock.yml +++ b/.github/workflows/breaking-change-checker.lock.yml @@ -158,6 +158,33 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -583,6 +610,12 @@ jobs: } } GH_AW_MCP_CONFIG_1c57e2cab2f2caf9_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index bd245b8a8b6..b6f9cd9fe1a 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -208,6 +208,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_913c1d056bceed0c_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -690,6 +717,12 @@ jobs: } } GH_AW_MCP_CONFIG_03abdce85ee0b9b7_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index fa7523977af..d8b794edc40 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -166,6 +166,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_c3b070ffe5979e04_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -657,6 +685,12 @@ jobs: } } GH_AW_MCP_CONFIG_d174788768fb96df_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ci-doctor.lock.yml b/.github/workflows/ci-doctor.lock.yml index 40ca9abfbfd..25c0d423b8c 100644 --- a/.github/workflows/ci-doctor.lock.yml +++ b/.github/workflows/ci-doctor.lock.yml @@ -222,6 +222,34 @@ jobs: Tools: add_comment, create_issue, update_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -810,6 +838,12 @@ jobs: } } GH_AW_MCP_CONFIG_a6198c3e524b5cdb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/claude-code-user-docs-review.lock.yml b/.github/workflows/claude-code-user-docs-review.lock.yml index 39cbd71ec93..ed9776f91f6 100644 --- a/.github/workflows/claude-code-user-docs-review.lock.yml +++ b/.github/workflows/claude-code-user-docs-review.lock.yml @@ -165,6 +165,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -603,6 +631,12 @@ jobs: } } GH_AW_MCP_CONFIG_82bfc77fc848bc07_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cli-consistency-checker.lock.yml b/.github/workflows/cli-consistency-checker.lock.yml index 55eef3e4f78..88337024660 100644 --- a/.github/workflows/cli-consistency-checker.lock.yml +++ b/.github/workflows/cli-consistency-checker.lock.yml @@ -149,6 +149,33 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -571,6 +598,12 @@ jobs: } } GH_AW_MCP_CONFIG_0aa423252227dacb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cli-version-checker.lock.yml b/.github/workflows/cli-version-checker.lock.yml index 4f9f647ca50..d84db4ef343 100644 --- a/.github/workflows/cli-version-checker.lock.yml +++ b/.github/workflows/cli-version-checker.lock.yml @@ -165,6 +165,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -611,6 +639,12 @@ jobs: } } GH_AW_MCP_CONFIG_68bf802d1e480d49_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index 974deb724ce..85b39f6b6dd 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -257,6 +257,37 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_910c108d300753ae_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -908,6 +939,12 @@ jobs: } } GH_AW_MCP_CONFIG_16ec4d0414e29855_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index 22766d599ef..154e218705d 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -161,6 +161,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ea41311dd97f7585_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -639,6 +667,12 @@ jobs: } } GH_AW_MCP_CONFIG_a60fb1ebbfa2b26b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index 864ae344686..b59ee3ed26e 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -168,6 +168,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_958f7037a674f6ba_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -595,6 +622,12 @@ jobs: } } GH_AW_MCP_CONFIG_7a76b439cf427b72_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/codex-github-remote-mcp-test.lock.yml b/.github/workflows/codex-github-remote-mcp-test.lock.yml index d0f79ec94af..610ac910acf 100644 --- a/.github/workflows/codex-github-remote-mcp-test.lock.yml +++ b/.github/workflows/codex-github-remote-mcp-test.lock.yml @@ -151,6 +151,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_3d136f493b7edd72_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -399,6 +426,12 @@ jobs: } } GH_AW_MCP_CONFIG_c685301f8ea8b6a0_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/commit-changes-analyzer.lock.yml b/.github/workflows/commit-changes-analyzer.lock.yml index 413b2344e6e..bc6a18ee1be 100644 --- a/.github/workflows/commit-changes-analyzer.lock.yml +++ b/.github/workflows/commit-changes-analyzer.lock.yml @@ -163,6 +163,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -578,6 +605,12 @@ jobs: } } GH_AW_MCP_CONFIG_96c724bdb02bb676_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/constraint-solving-potd.lock.yml b/.github/workflows/constraint-solving-potd.lock.yml index 1c2674560b6..78b33d332a9 100644 --- a/.github/workflows/constraint-solving-potd.lock.yml +++ b/.github/workflows/constraint-solving-potd.lock.yml @@ -158,6 +158,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -574,6 +602,12 @@ jobs: } } GH_AW_MCP_CONFIG_ac4bca1b70cc519b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/contribution-check.lock.yml b/.github/workflows/contribution-check.lock.yml index 7bb38b8cab3..3b1123c7fde 100644 --- a/.github/workflows/contribution-check.lock.yml +++ b/.github/workflows/contribution-check.lock.yml @@ -159,6 +159,33 @@ jobs: Tools: add_comment(max:10), create_issue, add_labels(max:4), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -618,6 +645,12 @@ jobs: } } GH_AW_MCP_CONFIG_2eaf8996402089a2_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-agent-analysis.lock.yml b/.github/workflows/copilot-agent-analysis.lock.yml index 1bcbf9ff460..57bf012de22 100644 --- a/.github/workflows/copilot-agent-analysis.lock.yml +++ b/.github/workflows/copilot-agent-analysis.lock.yml @@ -171,6 +171,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -642,6 +670,12 @@ jobs: } } GH_AW_MCP_CONFIG_1a79405c65a64208_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-cli-deep-research.lock.yml b/.github/workflows/copilot-cli-deep-research.lock.yml index 16f3f6831f5..cfad61e183a 100644 --- a/.github/workflows/copilot-cli-deep-research.lock.yml +++ b/.github/workflows/copilot-cli-deep-research.lock.yml @@ -155,6 +155,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -595,6 +622,12 @@ jobs: } } GH_AW_MCP_CONFIG_f96a821409b6a483_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-merged-report.lock.yml b/.github/workflows/copilot-pr-merged-report.lock.yml index 9d537199f5d..6e2202d7846 100644 --- a/.github/workflows/copilot-pr-merged-report.lock.yml +++ b/.github/workflows/copilot-pr-merged-report.lock.yml @@ -161,6 +161,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -732,6 +760,12 @@ jobs: } } GH_AW_MCP_CONFIG_214c4b63db1c096a_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-nlp-analysis.lock.yml b/.github/workflows/copilot-pr-nlp-analysis.lock.yml index 2cdfc7d9673..fa7d2a8ee91 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.lock.yml +++ b/.github/workflows/copilot-pr-nlp-analysis.lock.yml @@ -168,6 +168,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -689,6 +717,12 @@ jobs: } } GH_AW_MCP_CONFIG_909ba834faadfa85_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-prompt-analysis.lock.yml b/.github/workflows/copilot-pr-prompt-analysis.lock.yml index 289c028e8ed..cdfe9a8d32f 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.lock.yml +++ b/.github/workflows/copilot-pr-prompt-analysis.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -636,6 +664,12 @@ jobs: } } GH_AW_MCP_CONFIG_7efc8a9b8bd1094b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-session-insights.lock.yml b/.github/workflows/copilot-session-insights.lock.yml index c9233c57614..b6cde92b53d 100644 --- a/.github/workflows/copilot-session-insights.lock.yml +++ b/.github/workflows/copilot-session-insights.lock.yml @@ -177,6 +177,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -693,6 +721,12 @@ jobs: } } GH_AW_MCP_CONFIG_81cb9bf6bbab9ca6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index 25a6d45f55f..998643c5f7d 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -195,6 +195,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_c7b97f63987d3f1e_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -639,6 +666,12 @@ jobs: } } GH_AW_MCP_CONFIG_1b2dccce30014d92_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-architecture-diagram.lock.yml b/.github/workflows/daily-architecture-diagram.lock.yml index 79b9ae1f013..a33a49d077d 100644 --- a/.github/workflows/daily-architecture-diagram.lock.yml +++ b/.github/workflows/daily-architecture-diagram.lock.yml @@ -160,6 +160,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f5a79467418a74fe_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -638,6 +666,12 @@ jobs: } } GH_AW_MCP_CONFIG_ada8a355f17974cb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-assign-issue-to-user.lock.yml b/.github/workflows/daily-assign-issue-to-user.lock.yml index 0a1473f884f..308342621b9 100644 --- a/.github/workflows/daily-assign-issue-to-user.lock.yml +++ b/.github/workflows/daily-assign-issue-to-user.lock.yml @@ -148,6 +148,33 @@ jobs: Tools: add_comment, assign_to_user, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -574,6 +601,12 @@ jobs: } } GH_AW_MCP_CONFIG_905ec6d74bd3cef6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-choice-test.lock.yml b/.github/workflows/daily-choice-test.lock.yml index 0f2a77f8b13..a508b6a7613 100644 --- a/.github/workflows/daily-choice-test.lock.yml +++ b/.github/workflows/daily-choice-test.lock.yml @@ -157,6 +157,33 @@ jobs: Tools: missing_tool, missing_data, noop, test_environment + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -572,6 +599,12 @@ jobs: } } GH_AW_MCP_CONFIG_9df20f616181b904_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-cli-performance.lock.yml b/.github/workflows/daily-cli-performance.lock.yml index 88b08b8a9cc..50b5d299dd0 100644 --- a/.github/workflows/daily-cli-performance.lock.yml +++ b/.github/workflows/daily-cli-performance.lock.yml @@ -184,6 +184,33 @@ jobs: Tools: add_comment(max:5), create_issue(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -794,6 +821,12 @@ jobs: } } GH_AW_MCP_CONFIG_be21b238233abce6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-cli-tools-tester.lock.yml b/.github/workflows/daily-cli-tools-tester.lock.yml index b9f89545c3a..76e1f0b8a6e 100644 --- a/.github/workflows/daily-cli-tools-tester.lock.yml +++ b/.github/workflows/daily-cli-tools-tester.lock.yml @@ -164,6 +164,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -660,6 +688,12 @@ jobs: } } GH_AW_MCP_CONFIG_f87695436f43f2f4_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-code-metrics.lock.yml b/.github/workflows/daily-code-metrics.lock.yml index 4220be6f4bb..cf9e8f856e0 100644 --- a/.github/workflows/daily-code-metrics.lock.yml +++ b/.github/workflows/daily-code-metrics.lock.yml @@ -172,6 +172,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -669,6 +697,12 @@ jobs: } } GH_AW_MCP_CONFIG_ac39fbd4537408b6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-community-attribution.lock.yml b/.github/workflows/daily-community-attribution.lock.yml index 1ae1484f1e2..e22a890baaa 100644 --- a/.github/workflows/daily-community-attribution.lock.yml +++ b/.github/workflows/daily-community-attribution.lock.yml @@ -165,6 +165,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_3a6544334ea882c2_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -620,6 +647,12 @@ jobs: } } GH_AW_MCP_CONFIG_929cc945f361fa8d_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-compiler-quality.lock.yml b/.github/workflows/daily-compiler-quality.lock.yml index 44229f73dd8..d98810cef0c 100644 --- a/.github/workflows/daily-compiler-quality.lock.yml +++ b/.github/workflows/daily-compiler-quality.lock.yml @@ -160,6 +160,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -658,6 +687,12 @@ jobs: } } GH_AW_MCP_CONFIG_8679f4bc190a1edd_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-copilot-token-report.lock.yml b/.github/workflows/daily-copilot-token-report.lock.yml index e8125167ca8..0e92b4a2868 100644 --- a/.github/workflows/daily-copilot-token-report.lock.yml +++ b/.github/workflows/daily-copilot-token-report.lock.yml @@ -168,6 +168,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -711,6 +739,12 @@ jobs: } } GH_AW_MCP_CONFIG_fcc05da5cd1839db_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-doc-healer.lock.yml b/.github/workflows/daily-doc-healer.lock.yml index 7407192eb4c..01489c7efc8 100644 --- a/.github/workflows/daily-doc-healer.lock.yml +++ b/.github/workflows/daily-doc-healer.lock.yml @@ -172,6 +172,35 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_1ab69342d96baba9_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -723,6 +752,12 @@ jobs: } } GH_AW_MCP_CONFIG_9095aa0893fa6ab9_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index 354ca5a1387..a12729b9a44 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -171,6 +171,35 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f28225f88d7db532_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -687,6 +716,12 @@ jobs: } } GH_AW_MCP_CONFIG_eec8b6fe34c3336b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-fact.lock.yml b/.github/workflows/daily-fact.lock.yml index cfd000e42f5..db30e473290 100644 --- a/.github/workflows/daily-fact.lock.yml +++ b/.github/workflows/daily-fact.lock.yml @@ -161,6 +161,33 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -664,6 +691,12 @@ jobs: } } GH_AW_MCP_CONFIG_baecbbeef522d057_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-file-diet.lock.yml b/.github/workflows/daily-file-diet.lock.yml index 7a1be41b0c1..4b958233d7c 100644 --- a/.github/workflows/daily-file-diet.lock.yml +++ b/.github/workflows/daily-file-diet.lock.yml @@ -161,6 +161,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -649,6 +677,12 @@ jobs: } } GH_AW_MCP_CONFIG_1fb97ead37ab5212_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-firewall-report.lock.yml b/.github/workflows/daily-firewall-report.lock.yml index dca6285ff82..4d9b0351b82 100644 --- a/.github/workflows/daily-firewall-report.lock.yml +++ b/.github/workflows/daily-firewall-report.lock.yml @@ -172,6 +172,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -721,6 +750,12 @@ jobs: } } GH_AW_MCP_CONFIG_b63e8ed128cf6d89_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-function-namer.lock.yml b/.github/workflows/daily-function-namer.lock.yml index be5317bfdbb..7b6d2945714 100644 --- a/.github/workflows/daily-function-namer.lock.yml +++ b/.github/workflows/daily-function-namer.lock.yml @@ -166,6 +166,35 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -667,6 +696,12 @@ jobs: } } GH_AW_MCP_CONFIG_5419bcbc3315f546_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-integrity-analysis.lock.yml b/.github/workflows/daily-integrity-analysis.lock.yml index abdc93ced10..e45d43e9ceb 100644 --- a/.github/workflows/daily-integrity-analysis.lock.yml +++ b/.github/workflows/daily-integrity-analysis.lock.yml @@ -172,6 +172,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -738,6 +767,12 @@ jobs: } } GH_AW_MCP_CONFIG_a90c815e7f132927_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-issues-report.lock.yml b/.github/workflows/daily-issues-report.lock.yml index 26e8994b8d6..4c71e5b3324 100644 --- a/.github/workflows/daily-issues-report.lock.yml +++ b/.github/workflows/daily-issues-report.lock.yml @@ -178,6 +178,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -719,6 +747,12 @@ jobs: } } GH_AW_MCP_CONFIG_77f821b27d834424_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-malicious-code-scan.lock.yml b/.github/workflows/daily-malicious-code-scan.lock.yml index d7a5841ffb1..d96de2b2d7f 100644 --- a/.github/workflows/daily-malicious-code-scan.lock.yml +++ b/.github/workflows/daily-malicious-code-scan.lock.yml @@ -154,6 +154,33 @@ jobs: Tools: create_code_scanning_alert, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -581,6 +608,12 @@ jobs: } } GH_AW_MCP_CONFIG_83683437db802e24_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml index 1eb0b86c816..a85de50a956 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml +++ b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml @@ -159,6 +159,35 @@ jobs: Tools: create_issue(max:5), create_agent_session(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -679,6 +708,12 @@ jobs: } } GH_AW_MCP_CONFIG_0491dbbd83e23c4f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml index 1b63cb7ddcf..5860eefc2a8 100644 --- a/.github/workflows/daily-multi-device-docs-tester.lock.yml +++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml @@ -170,6 +170,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -640,6 +668,12 @@ jobs: } } GH_AW_MCP_CONFIG_dee616c5c06308f2_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-news.lock.yml b/.github/workflows/daily-news.lock.yml index d0f80461697..0d565c509fb 100644 --- a/.github/workflows/daily-news.lock.yml +++ b/.github/workflows/daily-news.lock.yml @@ -167,6 +167,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `tavily` — run `tavily --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -761,6 +790,12 @@ jobs: } } GH_AW_MCP_CONFIG_3abca47eab86dbce_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml index 6fd2199bd7b..c5d5eade1fe 100644 --- a/.github/workflows/daily-observability-report.lock.yml +++ b/.github/workflows/daily-observability-report.lock.yml @@ -170,6 +170,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -701,6 +729,12 @@ jobs: } } GH_AW_MCP_CONFIG_3af8d89e5baa648f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-performance-summary.lock.yml b/.github/workflows/daily-performance-summary.lock.yml index b032a8d989e..248fbafd8d1 100644 --- a/.github/workflows/daily-performance-summary.lock.yml +++ b/.github/workflows/daily-performance-summary.lock.yml @@ -169,6 +169,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1119,6 +1147,12 @@ jobs: } } GH_AW_MCP_CONFIG_d1eb31902b227a1b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-regulatory.lock.yml b/.github/workflows/daily-regulatory.lock.yml index 208960540df..563a020f4cb 100644 --- a/.github/workflows/daily-regulatory.lock.yml +++ b/.github/workflows/daily-regulatory.lock.yml @@ -162,6 +162,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1052,6 +1079,12 @@ jobs: } } GH_AW_MCP_CONFIG_39191bed09b411d6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 597b51f719a..5f8841c4eb9 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -176,6 +176,35 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_526dda5557e006b5_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -698,6 +727,12 @@ jobs: } } GH_AW_MCP_CONFIG_0d1f10a17b7edb5f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml index 8e55694b0e5..94c306943a5 100644 --- a/.github/workflows/daily-repo-chronicle.lock.yml +++ b/.github/workflows/daily-repo-chronicle.lock.yml @@ -161,6 +161,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -639,6 +667,12 @@ jobs: } } GH_AW_MCP_CONFIG_ac24495438e56c9e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-output-integrator.lock.yml b/.github/workflows/daily-safe-output-integrator.lock.yml index 194d6e7847c..18d856a154c 100644 --- a/.github/workflows/daily-safe-output-integrator.lock.yml +++ b/.github/workflows/daily-safe-output-integrator.lock.yml @@ -157,6 +157,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_de84013d0b3384a0_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -582,6 +609,12 @@ jobs: } } GH_AW_MCP_CONFIG_904546420bba2ac6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-output-optimizer.lock.yml b/.github/workflows/daily-safe-output-optimizer.lock.yml index ef177a2b179..ac03105cd4e 100644 --- a/.github/workflows/daily-safe-output-optimizer.lock.yml +++ b/.github/workflows/daily-safe-output-optimizer.lock.yml @@ -174,6 +174,35 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -701,6 +730,12 @@ jobs: } } GH_AW_MCP_CONFIG_f1008ce58891551c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-outputs-conformance.lock.yml b/.github/workflows/daily-safe-outputs-conformance.lock.yml index 1b61bd46015..3eb51a2ea9d 100644 --- a/.github/workflows/daily-safe-outputs-conformance.lock.yml +++ b/.github/workflows/daily-safe-outputs-conformance.lock.yml @@ -161,6 +161,33 @@ jobs: Tools: create_issue(max:10), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -581,6 +608,12 @@ jobs: } } GH_AW_MCP_CONFIG_ed0c97f560af7ab9_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-secrets-analysis.lock.yml b/.github/workflows/daily-secrets-analysis.lock.yml index 00e09af8017..5efe61d44bb 100644 --- a/.github/workflows/daily-secrets-analysis.lock.yml +++ b/.github/workflows/daily-secrets-analysis.lock.yml @@ -154,6 +154,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -570,6 +597,12 @@ jobs: } } GH_AW_MCP_CONFIG_b987c38bcb160a34_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-security-red-team.lock.yml b/.github/workflows/daily-security-red-team.lock.yml index 0017fd47e84..c27dcb1ce8b 100644 --- a/.github/workflows/daily-security-red-team.lock.yml +++ b/.github/workflows/daily-security-red-team.lock.yml @@ -162,6 +162,33 @@ jobs: Tools: create_issue(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -585,6 +612,12 @@ jobs: } } GH_AW_MCP_CONFIG_1d39cb685714b3c4_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-semgrep-scan.lock.yml b/.github/workflows/daily-semgrep-scan.lock.yml index 02d216138f5..498799075dd 100644 --- a/.github/workflows/daily-semgrep-scan.lock.yml +++ b/.github/workflows/daily-semgrep-scan.lock.yml @@ -161,6 +161,34 @@ jobs: Tools: create_code_scanning_alert, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `semgrep` — run `semgrep --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -607,6 +635,12 @@ jobs: } } GH_AW_MCP_CONFIG_1b17b4ed5633b171_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-syntax-error-quality.lock.yml b/.github/workflows/daily-syntax-error-quality.lock.yml index 1095aec7773..4f3e0980de0 100644 --- a/.github/workflows/daily-syntax-error-quality.lock.yml +++ b/.github/workflows/daily-syntax-error-quality.lock.yml @@ -153,6 +153,33 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -586,6 +613,12 @@ jobs: } } GH_AW_MCP_CONFIG_427d7ff0f3021689_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-team-evolution-insights.lock.yml b/.github/workflows/daily-team-evolution-insights.lock.yml index f53ad2834c9..c479c6345c5 100644 --- a/.github/workflows/daily-team-evolution-insights.lock.yml +++ b/.github/workflows/daily-team-evolution-insights.lock.yml @@ -162,6 +162,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -578,6 +605,12 @@ jobs: } } GH_AW_MCP_CONFIG_9c5bdf2d6f07f6fd_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-team-status.lock.yml b/.github/workflows/daily-team-status.lock.yml index 525d420ff54..a7474e8beae 100644 --- a/.github/workflows/daily-team-status.lock.yml +++ b/.github/workflows/daily-team-status.lock.yml @@ -169,6 +169,33 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -590,6 +617,12 @@ jobs: } } GH_AW_MCP_CONFIG_a8ae48bfebeab6ac_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-testify-uber-super-expert.lock.yml b/.github/workflows/daily-testify-uber-super-expert.lock.yml index 16908e21662..07e9d17f0d4 100644 --- a/.github/workflows/daily-testify-uber-super-expert.lock.yml +++ b/.github/workflows/daily-testify-uber-super-expert.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -673,6 +701,12 @@ jobs: } } GH_AW_MCP_CONFIG_9801a019b807be10_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index 09f60f84430..d13708d24ce 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -153,6 +153,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ca1bb6eca19a6937_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -575,6 +602,12 @@ jobs: } } GH_AW_MCP_CONFIG_ded3d43bff6f4a01_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dead-code-remover.lock.yml b/.github/workflows/dead-code-remover.lock.yml index da7d51c22fa..2c1be840c0e 100644 --- a/.github/workflows/dead-code-remover.lock.yml +++ b/.github/workflows/dead-code-remover.lock.yml @@ -165,6 +165,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_bdef07df3fcaf856_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -626,6 +654,12 @@ jobs: } } GH_AW_MCP_CONFIG_ac605b6dffd51016_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/deep-report.lock.yml b/.github/workflows/deep-report.lock.yml index 2cf8deff8bc..bc65132e9a8 100644 --- a/.github/workflows/deep-report.lock.yml +++ b/.github/workflows/deep-report.lock.yml @@ -175,6 +175,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -777,6 +806,12 @@ jobs: } } GH_AW_MCP_CONFIG_06a69b26b842771b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/delight.lock.yml b/.github/workflows/delight.lock.yml index 9bb6beafee3..d422c60bbcb 100644 --- a/.github/workflows/delight.lock.yml +++ b/.github/workflows/delight.lock.yml @@ -158,6 +158,33 @@ jobs: Tools: create_issue(max:2), create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -634,6 +661,12 @@ jobs: } } GH_AW_MCP_CONFIG_17d1b71e7ef97bf6_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dependabot-burner.lock.yml b/.github/workflows/dependabot-burner.lock.yml index 019b8cfdf47..6580cf0f8ab 100644 --- a/.github/workflows/dependabot-burner.lock.yml +++ b/.github/workflows/dependabot-burner.lock.yml @@ -161,6 +161,33 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -582,6 +609,12 @@ jobs: } } GH_AW_MCP_CONFIG_4f351439e1605739_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dependabot-go-checker.lock.yml b/.github/workflows/dependabot-go-checker.lock.yml index 7f43c265cbb..6d1a39ffb23 100644 --- a/.github/workflows/dependabot-go-checker.lock.yml +++ b/.github/workflows/dependabot-go-checker.lock.yml @@ -159,6 +159,33 @@ jobs: Tools: create_issue(max:10), close_issue(max:20), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -600,6 +627,12 @@ jobs: } } GH_AW_MCP_CONFIG_7ea7c063c0476146_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dev-hawk.lock.yml b/.github/workflows/dev-hawk.lock.yml index b035fcc443c..23d8b5c2da9 100644 --- a/.github/workflows/dev-hawk.lock.yml +++ b/.github/workflows/dev-hawk.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -662,6 +690,12 @@ jobs: } } GH_AW_MCP_CONFIG_ab0350833da7ec40_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dev.lock.yml b/.github/workflows/dev.lock.yml index 9cc72d59b60..85b29c91ec9 100644 --- a/.github/workflows/dev.lock.yml +++ b/.github/workflows/dev.lock.yml @@ -217,6 +217,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -709,6 +737,12 @@ jobs: } } GH_AW_MCP_CONFIG_dbd02877d1f6e4f8_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index bbc58d52706..7fe47df9631 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -175,6 +175,36 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_b38f5e32f9abeaa2_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -800,6 +830,12 @@ jobs: } } GH_AW_MCP_CONFIG_d1a97433a4daeec5_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index d34768965f4..b34fca863df 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -163,6 +163,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_af0c22aa486b1fca_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -659,6 +687,12 @@ jobs: } } GH_AW_MCP_CONFIG_f79e6f0df29f0677_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/discussion-task-miner.lock.yml b/.github/workflows/discussion-task-miner.lock.yml index 3541f1e2b6e..8d27f478352 100644 --- a/.github/workflows/discussion-task-miner.lock.yml +++ b/.github/workflows/discussion-task-miner.lock.yml @@ -158,6 +158,33 @@ jobs: Tools: add_comment(max:3), create_issue(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -624,6 +651,12 @@ jobs: } } GH_AW_MCP_CONFIG_0c41d1cf13dc69ef_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/docs-noob-tester.lock.yml b/.github/workflows/docs-noob-tester.lock.yml index dcbbde4ed24..0ea534a47ac 100644 --- a/.github/workflows/docs-noob-tester.lock.yml +++ b/.github/workflows/docs-noob-tester.lock.yml @@ -160,6 +160,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -610,6 +638,12 @@ jobs: } } GH_AW_MCP_CONFIG_fdb2d8f24ab043f5_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/draft-pr-cleanup.lock.yml b/.github/workflows/draft-pr-cleanup.lock.yml index ebb5cc8d0fb..9d110e9cf21 100644 --- a/.github/workflows/draft-pr-cleanup.lock.yml +++ b/.github/workflows/draft-pr-cleanup.lock.yml @@ -149,6 +149,33 @@ jobs: Tools: add_comment(max:20), close_pull_request(max:10), add_labels(max:20), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -593,6 +620,12 @@ jobs: } } GH_AW_MCP_CONFIG_e6c8f82246cb70f3_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/duplicate-code-detector.lock.yml b/.github/workflows/duplicate-code-detector.lock.yml index 22b363fe8c8..58b5a08944d 100644 --- a/.github/workflows/duplicate-code-detector.lock.yml +++ b/.github/workflows/duplicate-code-detector.lock.yml @@ -168,6 +168,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -697,6 +725,12 @@ jobs: } } GH_AW_MCP_CONFIG_ba1ec8c1aa410beb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/example-permissions-warning.lock.yml b/.github/workflows/example-permissions-warning.lock.yml index 3d798a56e2b..6ea1f88c554 100644 --- a/.github/workflows/example-permissions-warning.lock.yml +++ b/.github/workflows/example-permissions-warning.lock.yml @@ -148,6 +148,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_5c3619dea31e9804_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -379,6 +406,12 @@ jobs: } } GH_AW_MCP_CONFIG_de5f7b75a2c85f8b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/example-workflow-analyzer.lock.yml b/.github/workflows/example-workflow-analyzer.lock.yml index ea756da9e65..af5f37962a3 100644 --- a/.github/workflows/example-workflow-analyzer.lock.yml +++ b/.github/workflows/example-workflow-analyzer.lock.yml @@ -166,6 +166,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -652,6 +680,12 @@ jobs: } } GH_AW_MCP_CONFIG_b24fc15d7cd3393e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/firewall-escape.lock.yml b/.github/workflows/firewall-escape.lock.yml index b9c429eb36f..cf1f948e563 100644 --- a/.github/workflows/firewall-escape.lock.yml +++ b/.github/workflows/firewall-escape.lock.yml @@ -176,6 +176,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -634,6 +662,12 @@ jobs: } } GH_AW_MCP_CONFIG_ed0f3038012ec10f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/firewall.lock.yml b/.github/workflows/firewall.lock.yml index 6272f77de1b..6da9652d2f2 100644 --- a/.github/workflows/firewall.lock.yml +++ b/.github/workflows/firewall.lock.yml @@ -148,6 +148,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_51f527cfa56efa24_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -381,6 +408,12 @@ jobs: } } GH_AW_MCP_CONFIG_574888acb18b422c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index 5fef408a36a..74f5e75e7df 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -163,6 +163,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_c168a14d0fc28a2f_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -587,6 +614,12 @@ jobs: } } GH_AW_MCP_CONFIG_36aa8fb910f8ac6e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-mcp-structural-analysis.lock.yml b/.github/workflows/github-mcp-structural-analysis.lock.yml index f222869739f..734dca2c233 100644 --- a/.github/workflows/github-mcp-structural-analysis.lock.yml +++ b/.github/workflows/github-mcp-structural-analysis.lock.yml @@ -169,6 +169,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -648,6 +676,12 @@ jobs: } } GH_AW_MCP_CONFIG_a1538eadb7702096_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index b0367806d54..88c86b467e9 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -169,6 +169,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_1af95d393f4b398a_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -643,6 +671,12 @@ jobs: } } GH_AW_MCP_CONFIG_07750a9d533cc384_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-remote-mcp-auth-test.lock.yml b/.github/workflows/github-remote-mcp-auth-test.lock.yml index 037959b366d..94293e28f7e 100644 --- a/.github/workflows/github-remote-mcp-auth-test.lock.yml +++ b/.github/workflows/github-remote-mcp-auth-test.lock.yml @@ -161,6 +161,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -586,6 +613,12 @@ jobs: } } GH_AW_MCP_CONFIG_89196e035e942d59_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index ae915cedcce..fda74b797b3 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -175,6 +175,36 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_6e15d7474d90bf3a_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -787,6 +817,12 @@ jobs: } } GH_AW_MCP_CONFIG_adf218d0f4ba2707_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-fan.lock.yml b/.github/workflows/go-fan.lock.yml index edbf9275817..9397165ebd3 100644 --- a/.github/workflows/go-fan.lock.yml +++ b/.github/workflows/go-fan.lock.yml @@ -168,6 +168,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -664,6 +693,12 @@ jobs: } } GH_AW_MCP_CONFIG_a10bea8653625418_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index 6fa2bb7020c..873db050507 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -169,6 +169,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_6d6cb0d29893f634_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -769,6 +797,12 @@ jobs: } } GH_AW_MCP_CONFIG_69356c4a7c3d1a8e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-pattern-detector.lock.yml b/.github/workflows/go-pattern-detector.lock.yml index c689e970f54..6e45c44578a 100644 --- a/.github/workflows/go-pattern-detector.lock.yml +++ b/.github/workflows/go-pattern-detector.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `ast-grep` — run `ast-grep --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -605,6 +633,12 @@ jobs: } } GH_AW_MCP_CONFIG_dfb548a38ce6c86b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/gpclean.lock.yml b/.github/workflows/gpclean.lock.yml index cc3c778c661..c10a07bdb70 100644 --- a/.github/workflows/gpclean.lock.yml +++ b/.github/workflows/gpclean.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -610,6 +638,12 @@ jobs: } } GH_AW_MCP_CONFIG_952d5af838607375_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/grumpy-reviewer.lock.yml b/.github/workflows/grumpy-reviewer.lock.yml index 313da0143f1..72e54442b7c 100644 --- a/.github/workflows/grumpy-reviewer.lock.yml +++ b/.github/workflows/grumpy-reviewer.lock.yml @@ -215,6 +215,34 @@ jobs: Tools: create_pull_request_review_comment(max:5), submit_pull_request_review, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -719,6 +747,12 @@ jobs: } } GH_AW_MCP_CONFIG_2198edc089fd5a7d_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index aa76a20d1ff..0a8f8f2ae9d 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -170,6 +170,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_73077ac1efa7ed06_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -639,6 +666,12 @@ jobs: } } GH_AW_MCP_CONFIG_fc13695802fe239f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index b84f71a9a09..48fa0f3799f 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -164,6 +164,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_efd5c992561c134e_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -606,6 +634,12 @@ jobs: } } GH_AW_MCP_CONFIG_de038345cb4d5a5f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-arborist.lock.yml b/.github/workflows/issue-arborist.lock.yml index fc1c9090d84..f565bec8251 100644 --- a/.github/workflows/issue-arborist.lock.yml +++ b/.github/workflows/issue-arborist.lock.yml @@ -165,6 +165,33 @@ jobs: Tools: create_issue(max:5), create_discussion, link_sub_issue(max:50), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -684,6 +711,12 @@ jobs: } } GH_AW_MCP_CONFIG_1b783250b5f416ed_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-monster.lock.yml b/.github/workflows/issue-monster.lock.yml index 6d8dfaf2640..70b9f470f76 100644 --- a/.github/workflows/issue-monster.lock.yml +++ b/.github/workflows/issue-monster.lock.yml @@ -529,6 +529,33 @@ jobs: Tools: add_comment(max:3), assign_to_agent(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -969,6 +996,12 @@ jobs: } } GH_AW_MCP_CONFIG_bb876e15355ae348_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-triage-agent.lock.yml b/.github/workflows/issue-triage-agent.lock.yml index 4200cc3534f..13b51381d50 100644 --- a/.github/workflows/issue-triage-agent.lock.yml +++ b/.github/workflows/issue-triage-agent.lock.yml @@ -160,6 +160,33 @@ jobs: Tools: add_comment, add_labels, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -569,6 +596,12 @@ jobs: } } GH_AW_MCP_CONFIG_2a65d7b11ae90e8e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index d0fde52f663..1c1dbf92cbb 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -168,6 +168,35 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_eac1fdf49c0156e5_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -683,6 +712,12 @@ jobs: } } GH_AW_MCP_CONFIG_5bef3d8af077c803_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index 183c37d18f3..3a4458093e1 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -163,6 +163,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f721fba8c5d6f4ce_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -591,6 +618,12 @@ jobs: } } GH_AW_MCP_CONFIG_86970275459cf827_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/lockfile-stats.lock.yml b/.github/workflows/lockfile-stats.lock.yml index ee896eb0be4..e942578e5b2 100644 --- a/.github/workflows/lockfile-stats.lock.yml +++ b/.github/workflows/lockfile-stats.lock.yml @@ -165,6 +165,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -599,6 +627,12 @@ jobs: } } GH_AW_MCP_CONFIG_ad0a2f6a6eba97c1_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/mcp-inspector.lock.yml b/.github/workflows/mcp-inspector.lock.yml index c1a4e130dbf..18015939f48 100644 --- a/.github/workflows/mcp-inspector.lock.yml +++ b/.github/workflows/mcp-inspector.lock.yml @@ -200,6 +200,49 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop, notion_add_comment, post_to_slack_channel + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `arxiv` — run `arxiv --help` to see available tools + - `ast-grep` — run `ast-grep --help` to see available tools + - `brave-search` — run `brave-search --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `context7` — run `context7 --help` to see available tools + - `datadog` — run `datadog --help` to see available tools + - `deepwiki` — run `deepwiki --help` to see available tools + - `fabric-rti` — run `fabric-rti --help` to see available tools + - `github` — run `github --help` to see available tools + - `markitdown` — run `markitdown --help` to see available tools + - `memory` — run `memory --help` to see available tools + - `microsoftdocs` — run `microsoftdocs --help` to see available tools + - `notion` — run `notion --help` to see available tools + - `sentry` — run `sentry --help` to see available tools + - `serena` — run `serena --help` to see available tools + - `tavily` — run `tavily --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1113,6 +1156,12 @@ jobs: } } GH_AW_MCP_CONFIG_6b8f5add28aae19f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 54cb928c794..6dabc965be8 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -199,6 +199,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_c0b73803c180c67c_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -618,6 +645,12 @@ jobs: } } GH_AW_MCP_CONFIG_47f8b33c70b74959_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/metrics-collector.lock.yml b/.github/workflows/metrics-collector.lock.yml index b30ac1b66dd..8e2482aaed4 100644 --- a/.github/workflows/metrics-collector.lock.yml +++ b/.github/workflows/metrics-collector.lock.yml @@ -159,6 +159,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/agentic_workflows_guide.md" cat "${RUNNER_TEMP}/gh-aw/prompts/repo_memory_prompt.md" cat << 'GH_AW_PROMPT_d850707bdb59dc40_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -493,6 +521,12 @@ jobs: } } GH_AW_MCP_CONFIG_5c9a9fd6c01a3192_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/notion-issue-summary.lock.yml b/.github/workflows/notion-issue-summary.lock.yml index dbc5b9a4af4..db409b88095 100644 --- a/.github/workflows/notion-issue-summary.lock.yml +++ b/.github/workflows/notion-issue-summary.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: missing_tool, missing_data, noop, notion_add_comment + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `notion` — run `notion --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -587,6 +615,12 @@ jobs: } } GH_AW_MCP_CONFIG_e39f260422a5657b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/org-health-report.lock.yml b/.github/workflows/org-health-report.lock.yml index 883a9b6bc92..0f14ad0d743 100644 --- a/.github/workflows/org-health-report.lock.yml +++ b/.github/workflows/org-health-report.lock.yml @@ -169,6 +169,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -648,6 +676,12 @@ jobs: } } GH_AW_MCP_CONFIG_5f628ad6754dfa0e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pdf-summary.lock.yml b/.github/workflows/pdf-summary.lock.yml index 6ed56e6163a..2dde718d3c7 100644 --- a/.github/workflows/pdf-summary.lock.yml +++ b/.github/workflows/pdf-summary.lock.yml @@ -228,6 +228,35 @@ jobs: Tools: add_comment, create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `markitdown` — run `markitdown --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -716,6 +745,12 @@ jobs: } } GH_AW_MCP_CONFIG_3630b02970b0fa14_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/plan.lock.yml b/.github/workflows/plan.lock.yml index 1dd19cedd85..b30e0924f4f 100644 --- a/.github/workflows/plan.lock.yml +++ b/.github/workflows/plan.lock.yml @@ -200,6 +200,33 @@ jobs: Tools: create_issue(max:5), close_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -658,6 +685,12 @@ jobs: } } GH_AW_MCP_CONFIG_93e9bbbaf1b62840_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index 45b0ff645bb..607af8a96cd 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -226,6 +226,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -967,6 +995,12 @@ jobs: } } GH_AW_MCP_CONFIG_66acaa7ee379da27_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/portfolio-analyst.lock.yml b/.github/workflows/portfolio-analyst.lock.yml index 84991ff5be2..5795160795a 100644 --- a/.github/workflows/portfolio-analyst.lock.yml +++ b/.github/workflows/portfolio-analyst.lock.yml @@ -173,6 +173,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -740,6 +769,12 @@ jobs: } } GH_AW_MCP_CONFIG_90c67d3c6678dbe8_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pr-nitpick-reviewer.lock.yml b/.github/workflows/pr-nitpick-reviewer.lock.yml index 3bf10e7ea19..717815c7d5c 100644 --- a/.github/workflows/pr-nitpick-reviewer.lock.yml +++ b/.github/workflows/pr-nitpick-reviewer.lock.yml @@ -209,6 +209,34 @@ jobs: Tools: create_discussion, create_pull_request_review_comment(max:10), submit_pull_request_review, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -713,6 +741,12 @@ jobs: } } GH_AW_MCP_CONFIG_0eba254c4d20a470_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pr-triage-agent.lock.yml b/.github/workflows/pr-triage-agent.lock.yml index 022ac3662da..df20887afb9 100644 --- a/.github/workflows/pr-triage-agent.lock.yml +++ b/.github/workflows/pr-triage-agent.lock.yml @@ -162,6 +162,33 @@ jobs: Tools: add_comment(max:50), create_issue, add_labels(max:100), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -643,6 +670,12 @@ jobs: } } GH_AW_MCP_CONFIG_78e23fcc3b0e1c0b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/prompt-clustering-analysis.lock.yml b/.github/workflows/prompt-clustering-analysis.lock.yml index f55c308ec5c..78248eb10fa 100644 --- a/.github/workflows/prompt-clustering-analysis.lock.yml +++ b/.github/workflows/prompt-clustering-analysis.lock.yml @@ -177,6 +177,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -743,6 +772,12 @@ jobs: } } GH_AW_MCP_CONFIG_77d152322b306cbe_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/python-data-charts.lock.yml b/.github/workflows/python-data-charts.lock.yml index 3ed5f07e7da..96450c61ddf 100644 --- a/.github/workflows/python-data-charts.lock.yml +++ b/.github/workflows/python-data-charts.lock.yml @@ -169,6 +169,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -719,6 +748,12 @@ jobs: } } GH_AW_MCP_CONFIG_84c03101db8c2cf9_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index 11d933cbc9e..0c0091603ab 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -240,6 +240,36 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_a0c3414a8d08f8d7_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -875,6 +905,12 @@ jobs: } } GH_AW_MCP_CONFIG_c649e0fc30544e48_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index 6e19c45df69..cd977a10ce7 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -189,6 +189,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_5537490e8c05e0e7_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -635,6 +662,12 @@ jobs: } } GH_AW_MCP_CONFIG_56bd6f8525212f70_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml index 7bb716d3cee..48c028eba1a 100644 --- a/.github/workflows/release.lock.yml +++ b/.github/workflows/release.lock.yml @@ -177,6 +177,33 @@ jobs: Tools: update_release, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -605,6 +632,12 @@ jobs: } } GH_AW_MCP_CONFIG_c313bb4a07e4ca32_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml index 086e9dc83ea..be1f9372ef9 100644 --- a/.github/workflows/repo-audit-analyzer.lock.yml +++ b/.github/workflows/repo-audit-analyzer.lock.yml @@ -167,6 +167,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -603,6 +631,12 @@ jobs: } } GH_AW_MCP_CONFIG_19f430b340c0d1a7_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repo-tree-map.lock.yml b/.github/workflows/repo-tree-map.lock.yml index d65e084e0b9..4a14eb18074 100644 --- a/.github/workflows/repo-tree-map.lock.yml +++ b/.github/workflows/repo-tree-map.lock.yml @@ -160,6 +160,33 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -572,6 +599,12 @@ jobs: } } GH_AW_MCP_CONFIG_0d763efc0e9c7c1e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repository-quality-improver.lock.yml b/.github/workflows/repository-quality-improver.lock.yml index 5d305136cf9..05cefc84856 100644 --- a/.github/workflows/repository-quality-improver.lock.yml +++ b/.github/workflows/repository-quality-improver.lock.yml @@ -166,6 +166,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -664,6 +693,12 @@ jobs: } } GH_AW_MCP_CONFIG_6e8eee1df8ed1f5e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/research.lock.yml b/.github/workflows/research.lock.yml index ed4c058b508..4e56d302e9d 100644 --- a/.github/workflows/research.lock.yml +++ b/.github/workflows/research.lock.yml @@ -164,6 +164,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `tavily` — run `tavily --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -601,6 +629,12 @@ jobs: } } GH_AW_MCP_CONFIG_19a6ff64bafecf93_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/safe-output-health.lock.yml b/.github/workflows/safe-output-health.lock.yml index d418965564c..fc30f11f921 100644 --- a/.github/workflows/safe-output-health.lock.yml +++ b/.github/workflows/safe-output-health.lock.yml @@ -171,6 +171,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -688,6 +717,12 @@ jobs: } } GH_AW_MCP_CONFIG_fe83dd43c163a91a_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/schema-consistency-checker.lock.yml b/.github/workflows/schema-consistency-checker.lock.yml index 79e42d6c937..57ce3f097d5 100644 --- a/.github/workflows/schema-consistency-checker.lock.yml +++ b/.github/workflows/schema-consistency-checker.lock.yml @@ -165,6 +165,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -599,6 +627,12 @@ jobs: } } GH_AW_MCP_CONFIG_25341b3ac158b212_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/schema-feature-coverage.lock.yml b/.github/workflows/schema-feature-coverage.lock.yml index 94059d8203d..e872aea6b80 100644 --- a/.github/workflows/schema-feature-coverage.lock.yml +++ b/.github/workflows/schema-feature-coverage.lock.yml @@ -164,6 +164,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_98b78c552e118305_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -621,6 +648,12 @@ jobs: } } GH_AW_MCP_CONFIG_284f7123e1795d39_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/scout.lock.yml b/.github/workflows/scout.lock.yml index 15dd343edad..cace7b354dc 100644 --- a/.github/workflows/scout.lock.yml +++ b/.github/workflows/scout.lock.yml @@ -259,6 +259,39 @@ jobs: Tools: add_comment, add_labels, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `arxiv` — run `arxiv --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `deepwiki` — run `deepwiki --help` to see available tools + - `github` — run `github --help` to see available tools + - `markitdown` — run `markitdown --help` to see available tools + - `microsoftdocs` — run `microsoftdocs --help` to see available tools + - `tavily` — run `tavily --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -810,6 +843,12 @@ jobs: } } GH_AW_MCP_CONFIG_c538088c873f5c73_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/security-compliance.lock.yml b/.github/workflows/security-compliance.lock.yml index bc3adff777c..86679b60a33 100644 --- a/.github/workflows/security-compliance.lock.yml +++ b/.github/workflows/security-compliance.lock.yml @@ -169,6 +169,33 @@ jobs: Tools: create_issue(max:100), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -616,6 +643,12 @@ jobs: } } GH_AW_MCP_CONFIG_8ecaeb64faf4c6d2_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/security-review.lock.yml b/.github/workflows/security-review.lock.yml index 9e3dcb2246d..01405cc96f3 100644 --- a/.github/workflows/security-review.lock.yml +++ b/.github/workflows/security-review.lock.yml @@ -212,6 +212,35 @@ jobs: Tools: create_pull_request_review_comment(max:10), submit_pull_request_review, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -764,6 +793,12 @@ jobs: } } GH_AW_MCP_CONFIG_bda0e8027f180b5a_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/semantic-function-refactor.lock.yml b/.github/workflows/semantic-function-refactor.lock.yml index 330d1b5906a..598a1b3a167 100644 --- a/.github/workflows/semantic-function-refactor.lock.yml +++ b/.github/workflows/semantic-function-refactor.lock.yml @@ -164,6 +164,34 @@ jobs: Tools: create_issue, close_issue(max:10), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -663,6 +691,12 @@ jobs: } } GH_AW_MCP_CONFIG_8e9a6c2f4204cba3_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/sergo.lock.yml b/.github/workflows/sergo.lock.yml index 1a57431e3d9..272a6a002be 100644 --- a/.github/workflows/sergo.lock.yml +++ b/.github/workflows/sergo.lock.yml @@ -167,6 +167,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -662,6 +691,12 @@ jobs: } } GH_AW_MCP_CONFIG_fc9f4a3e84dd282e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index 1dcb094affc..f92b8a09fd2 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -178,6 +178,35 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_00fdac09910f5004_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -658,6 +687,12 @@ jobs: } } GH_AW_MCP_CONFIG_e80473f9ecc5ff8d_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-all-merged.lock.yml b/.github/workflows/smoke-agent-all-merged.lock.yml index 2bfde7b5488..44122c51ab0 100644 --- a/.github/workflows/smoke-agent-all-merged.lock.yml +++ b/.github/workflows/smoke-agent-all-merged.lock.yml @@ -195,6 +195,33 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -627,6 +654,12 @@ jobs: } } GH_AW_MCP_CONFIG_73cdc9322ab8c7cb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-all-none.lock.yml b/.github/workflows/smoke-agent-all-none.lock.yml index 950d9551707..5124120c1b2 100644 --- a/.github/workflows/smoke-agent-all-none.lock.yml +++ b/.github/workflows/smoke-agent-all-none.lock.yml @@ -195,6 +195,33 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -627,6 +654,12 @@ jobs: } } GH_AW_MCP_CONFIG_be500cd34233bd55_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-public-approved.lock.yml b/.github/workflows/smoke-agent-public-approved.lock.yml index cbc48a84835..9966220d532 100644 --- a/.github/workflows/smoke-agent-public-approved.lock.yml +++ b/.github/workflows/smoke-agent-public-approved.lock.yml @@ -200,6 +200,33 @@ jobs: Tools: add_comment(max:2), assign_to_agent, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -660,6 +687,12 @@ jobs: } } GH_AW_MCP_CONFIG_aed1dcf0af46bd24_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-public-none.lock.yml b/.github/workflows/smoke-agent-public-none.lock.yml index 72bad1a1d2b..45636c44e88 100644 --- a/.github/workflows/smoke-agent-public-none.lock.yml +++ b/.github/workflows/smoke-agent-public-none.lock.yml @@ -195,6 +195,33 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -627,6 +654,12 @@ jobs: } } GH_AW_MCP_CONFIG_2561f0fd9f0b6818_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-scoped-approved.lock.yml b/.github/workflows/smoke-agent-scoped-approved.lock.yml index e333511d628..a1339eca175 100644 --- a/.github/workflows/smoke-agent-scoped-approved.lock.yml +++ b/.github/workflows/smoke-agent-scoped-approved.lock.yml @@ -199,6 +199,33 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -637,6 +664,12 @@ jobs: } } GH_AW_MCP_CONFIG_eae6eef7ac15ae9a_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-call-workflow.lock.yml b/.github/workflows/smoke-call-workflow.lock.yml index f553a2b2bff..6338d3d6ae8 100644 --- a/.github/workflows/smoke-call-workflow.lock.yml +++ b/.github/workflows/smoke-call-workflow.lock.yml @@ -178,6 +178,33 @@ jobs: Tools: call_workflow, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -611,6 +638,12 @@ jobs: } } GH_AW_MCP_CONFIG_da60e4ff2622cb40_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index d87967f1d84..12b402184f0 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -239,6 +239,38 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_4ec99b0fd270d235_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + - `serena` — run `serena --help` to see available tools + - `tavily` — run `tavily --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -2065,6 +2097,12 @@ jobs: } } GH_AW_MCP_CONFIG_82ac77150d4b9330_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-codex.lock.yml b/.github/workflows/smoke-codex.lock.yml index cd8ccaa2938..bcf466f117a 100644 --- a/.github/workflows/smoke-codex.lock.yml +++ b/.github/workflows/smoke-codex.lock.yml @@ -227,6 +227,37 @@ jobs: Tools: add_comment(max:2), create_issue, add_labels, remove_labels, unassign_from_user, hide_comment(max:5), missing_tool, missing_data, noop, add_smoked_label + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1174,6 +1205,12 @@ jobs: } } GH_AW_MCP_CONFIG_c3d48ebeb7d5907a_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-copilot-arm.lock.yml b/.github/workflows/smoke-copilot-arm.lock.yml index 45b75bd5177..a4861a7626d 100644 --- a/.github/workflows/smoke-copilot-arm.lock.yml +++ b/.github/workflows/smoke-copilot-arm.lock.yml @@ -222,6 +222,37 @@ jobs: Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1527,6 +1558,12 @@ jobs: } } GH_AW_MCP_CONFIG_bbaab723be3e0d4f_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 65b9fcf3ca5..209c29b902e 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -229,6 +229,37 @@ jobs: Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, reply_to_pull_request_review_comment(max:5), add_labels, remove_labels, set_issue_type, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1577,6 +1608,12 @@ jobs: } } GH_AW_MCP_CONFIG_7d1672508c35ebcf_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-create-cross-repo-pr.lock.yml b/.github/workflows/smoke-create-cross-repo-pr.lock.yml index ee80a92c838..1d1bdd050e0 100644 --- a/.github/workflows/smoke-create-cross-repo-pr.lock.yml +++ b/.github/workflows/smoke-create-cross-repo-pr.lock.yml @@ -193,6 +193,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_b5851c5feae065c1_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -682,6 +709,12 @@ jobs: } } GH_AW_MCP_CONFIG_4e0fc3a9881a180e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-gemini.lock.yml b/.github/workflows/smoke-gemini.lock.yml index cee03969c71..5a59411a9dc 100644 --- a/.github/workflows/smoke-gemini.lock.yml +++ b/.github/workflows/smoke-gemini.lock.yml @@ -217,6 +217,34 @@ jobs: Tools: add_comment(max:2), create_issue, add_labels, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -821,6 +849,12 @@ jobs: } } GH_AW_MCP_CONFIG_dc3832e9686c5ff4_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index a91ce002702..8d13443234a 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -211,6 +211,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_8176b7650e805e07_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -651,6 +678,12 @@ jobs: } } GH_AW_MCP_CONFIG_21037b0628df299c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index ffd7cbd66b1..7f1207aacc7 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -210,6 +210,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ba7946ed4c54c799_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -809,6 +836,12 @@ jobs: } } GH_AW_MCP_CONFIG_5aaca792fea31195_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-service-ports.lock.yml b/.github/workflows/smoke-service-ports.lock.yml index f9bab96d08d..1b2f9da0f58 100644 --- a/.github/workflows/smoke-service-ports.lock.yml +++ b/.github/workflows/smoke-service-ports.lock.yml @@ -174,6 +174,33 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -585,6 +612,12 @@ jobs: } } GH_AW_MCP_CONFIG_4d3271670f04abd8_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-temporary-id.lock.yml b/.github/workflows/smoke-temporary-id.lock.yml index cd8007e3452..de63a414959 100644 --- a/.github/workflows/smoke-temporary-id.lock.yml +++ b/.github/workflows/smoke-temporary-id.lock.yml @@ -205,6 +205,33 @@ jobs: Tools: add_comment(max:2), create_issue(max:5), link_sub_issue(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -661,6 +688,12 @@ jobs: } } GH_AW_MCP_CONFIG_e916af4ce11580a1_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-test-tools.lock.yml b/.github/workflows/smoke-test-tools.lock.yml index c45ef51b970..4f10317f8cf 100644 --- a/.github/workflows/smoke-test-tools.lock.yml +++ b/.github/workflows/smoke-test-tools.lock.yml @@ -199,6 +199,33 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -627,6 +654,12 @@ jobs: } } GH_AW_MCP_CONFIG_4afe8cef8efb619c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-update-cross-repo-pr.lock.yml b/.github/workflows/smoke-update-cross-repo-pr.lock.yml index 1e79073f1c5..237d4dd0812 100644 --- a/.github/workflows/smoke-update-cross-repo-pr.lock.yml +++ b/.github/workflows/smoke-update-cross-repo-pr.lock.yml @@ -196,6 +196,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_6b3177d37c27b8e8_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -696,6 +724,12 @@ jobs: } } GH_AW_MCP_CONFIG_814ac3400c1a07dd_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-workflow-call-with-inputs.lock.yml b/.github/workflows/smoke-workflow-call-with-inputs.lock.yml index 8e9e4bc2180..437648d7ab2 100644 --- a/.github/workflows/smoke-workflow-call-with-inputs.lock.yml +++ b/.github/workflows/smoke-workflow-call-with-inputs.lock.yml @@ -205,6 +205,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_auto_create_issue.md" cat << 'GH_AW_PROMPT_35a5dccbd8d9d9f9_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -627,6 +654,12 @@ jobs: } } GH_AW_MCP_CONFIG_dfe9f89b71d5cca2_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-workflow-call.lock.yml b/.github/workflows/smoke-workflow-call.lock.yml index 64401791a90..850d60ad785 100644 --- a/.github/workflows/smoke-workflow-call.lock.yml +++ b/.github/workflows/smoke-workflow-call.lock.yml @@ -205,6 +205,33 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -611,6 +638,12 @@ jobs: } } GH_AW_MCP_CONFIG_93322c1ed722b990_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index 6765f447d00..b60e813c4d2 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -179,6 +179,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -718,6 +746,12 @@ jobs: } } GH_AW_MCP_CONFIG_ebcf5ba4522a9a8c_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/static-analysis-report.lock.yml b/.github/workflows/static-analysis-report.lock.yml index 9a0c1b24b74..832dcf69907 100644 --- a/.github/workflows/static-analysis-report.lock.yml +++ b/.github/workflows/static-analysis-report.lock.yml @@ -168,6 +168,35 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -693,6 +722,12 @@ jobs: } } GH_AW_MCP_CONFIG_d7f650b7f588b3cb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/step-name-alignment.lock.yml b/.github/workflows/step-name-alignment.lock.yml index dad3e4965bb..aa6d9390f0a 100644 --- a/.github/workflows/step-name-alignment.lock.yml +++ b/.github/workflows/step-name-alignment.lock.yml @@ -160,6 +160,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -599,6 +627,12 @@ jobs: } } GH_AW_MCP_CONFIG_5b790c46c781275b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/sub-issue-closer.lock.yml b/.github/workflows/sub-issue-closer.lock.yml index 570eda34a20..e7c4f54ebe1 100644 --- a/.github/workflows/sub-issue-closer.lock.yml +++ b/.github/workflows/sub-issue-closer.lock.yml @@ -156,6 +156,33 @@ jobs: Tools: add_comment(max:20), update_issue(max:20), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -614,6 +641,12 @@ jobs: } } GH_AW_MCP_CONFIG_7bbf5f57c18f1049_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/super-linter.lock.yml b/.github/workflows/super-linter.lock.yml index bbd865e8131..b29a85898e8 100644 --- a/.github/workflows/super-linter.lock.yml +++ b/.github/workflows/super-linter.lock.yml @@ -165,6 +165,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -620,6 +648,12 @@ jobs: } } GH_AW_MCP_CONFIG_9891f0fddf3fb195_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index caa51af168d..b75916d98d7 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -177,6 +177,35 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -777,6 +806,12 @@ jobs: } } GH_AW_MCP_CONFIG_b1b9da9c012c0a77_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/terminal-stylist.lock.yml b/.github/workflows/terminal-stylist.lock.yml index f23b6ff5d22..bd5e264574c 100644 --- a/.github/workflows/terminal-stylist.lock.yml +++ b/.github/workflows/terminal-stylist.lock.yml @@ -163,6 +163,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -636,6 +664,12 @@ jobs: } } GH_AW_MCP_CONFIG_494463c69bd7cc06_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index 00b594e2c0d..2acfada59eb 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -161,6 +161,34 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_fd59cc5c2d1fc082_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -601,6 +629,12 @@ jobs: } } GH_AW_MCP_CONFIG_7be545c29dd38aeb_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-dispatcher.lock.yml b/.github/workflows/test-dispatcher.lock.yml index 35001d73c56..d50af6f1cc4 100644 --- a/.github/workflows/test-dispatcher.lock.yml +++ b/.github/workflows/test-dispatcher.lock.yml @@ -152,6 +152,33 @@ jobs: Tools: dispatch_workflow, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -556,6 +583,12 @@ jobs: } } GH_AW_MCP_CONFIG_1c24b4097a736efa_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-project-url-default.lock.yml b/.github/workflows/test-project-url-default.lock.yml index fe96443646d..14fb1cb27c5 100644 --- a/.github/workflows/test-project-url-default.lock.yml +++ b/.github/workflows/test-project-url-default.lock.yml @@ -153,6 +153,33 @@ jobs: Tools: update_project(max:5), create_project_status_update, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -617,6 +644,12 @@ jobs: } } GH_AW_MCP_CONFIG_353cf85114406809_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-workflow.lock.yml b/.github/workflows/test-workflow.lock.yml index 6084c2e1a3d..c3b8c6935bb 100644 --- a/.github/workflows/test-workflow.lock.yml +++ b/.github/workflows/test-workflow.lock.yml @@ -151,6 +151,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_d2100dd9504f0ecb_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -380,6 +407,12 @@ jobs: } } GH_AW_MCP_CONFIG_6649ecbe0b98fcdc_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index 2bd7a647511..e22f0984ef9 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -220,6 +220,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_d35e31e70bc8be49_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -685,6 +712,12 @@ jobs: } } GH_AW_MCP_CONFIG_c9e3dc06238b8726_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/typist.lock.yml b/.github/workflows/typist.lock.yml index a2bc8cc6367..abdf84bc452 100644 --- a/.github/workflows/typist.lock.yml +++ b/.github/workflows/typist.lock.yml @@ -164,6 +164,34 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `serena` — run `serena --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -636,6 +664,12 @@ jobs: } } GH_AW_MCP_CONFIG_48c9b32d41e4a5f8_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index b49954f2809..524e1269a51 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -167,6 +167,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_37168e83c534310c_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -593,6 +620,12 @@ jobs: } } GH_AW_MCP_CONFIG_d099ccc6759c4ef8_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index 9a9cf2f00aa..80f28f21932 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -223,6 +223,36 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -820,6 +850,12 @@ jobs: } } GH_AW_MCP_CONFIG_35b9f7c27ddc03d3_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/update-astro.lock.yml b/.github/workflows/update-astro.lock.yml index 437974601a5..d69cc0de81b 100644 --- a/.github/workflows/update-astro.lock.yml +++ b/.github/workflows/update-astro.lock.yml @@ -168,6 +168,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_60089bbd806a2741_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -601,6 +628,12 @@ jobs: } } GH_AW_MCP_CONFIG_4fa1cfb31f5631b1_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/video-analyzer.lock.yml b/.github/workflows/video-analyzer.lock.yml index 4bcc315d10a..5670513d71b 100644 --- a/.github/workflows/video-analyzer.lock.yml +++ b/.github/workflows/video-analyzer.lock.yml @@ -162,6 +162,33 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -592,6 +619,12 @@ jobs: } } GH_AW_MCP_CONFIG_c4f6aa2564f8ee10_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-blog-post-writer.lock.yml b/.github/workflows/weekly-blog-post-writer.lock.yml index 9df7f5c86fe..a34c10b5c01 100644 --- a/.github/workflows/weekly-blog-post-writer.lock.yml +++ b/.github/workflows/weekly-blog-post-writer.lock.yml @@ -176,6 +176,35 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_37ff4ed646105a15_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + - `qmd` — run `qmd --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -773,6 +802,12 @@ jobs: } } GH_AW_MCP_CONFIG_76f2280dd63b606b_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index 37916047bd0..a75cc8c07ee 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -163,6 +163,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + - `playwright` — run `playwright --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -613,6 +641,12 @@ jobs: } } GH_AW_MCP_CONFIG_b498f891f99b13f5_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-issue-summary.lock.yml b/.github/workflows/weekly-issue-summary.lock.yml index 0bf2141c2b4..df70e658c0c 100644 --- a/.github/workflows/weekly-issue-summary.lock.yml +++ b/.github/workflows/weekly-issue-summary.lock.yml @@ -170,6 +170,34 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `cache-memory` — run `cache-memory --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -630,6 +658,12 @@ jobs: } } GH_AW_MCP_CONFIG_45402066e9c8035d_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index 6e55f4c9dfa..965993d25d6 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -164,6 +164,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_dd5ce0f0ce7b0ccb_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -584,6 +611,12 @@ jobs: } } GH_AW_MCP_CONFIG_9571fdea0e79c2ac_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-generator.lock.yml b/.github/workflows/workflow-generator.lock.yml index 5227266c94b..c4de0cb5681 100644 --- a/.github/workflows/workflow-generator.lock.yml +++ b/.github/workflows/workflow-generator.lock.yml @@ -196,6 +196,33 @@ jobs: Tools: update_issue, assign_to_agent, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -661,6 +688,12 @@ jobs: } } GH_AW_MCP_CONFIG_a89a20c6f3ef975e_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index bb5fe7e676b..87b286bc0b3 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -164,6 +164,33 @@ jobs: Tools: add_comment(max:15), create_issue(max:10), update_issue(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -682,6 +709,12 @@ jobs: } } GH_AW_MCP_CONFIG_65cf370b1871bead_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-normalizer.lock.yml b/.github/workflows/workflow-normalizer.lock.yml index 6d53254db2f..e54b186b833 100644 --- a/.github/workflows/workflow-normalizer.lock.yml +++ b/.github/workflows/workflow-normalizer.lock.yml @@ -164,6 +164,34 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `agentic-workflows` — run `agentic-workflows --help` to see available tools + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -659,6 +687,12 @@ jobs: } } GH_AW_MCP_CONFIG_b4cdeb8fad7b52fc_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-skill-extractor.lock.yml b/.github/workflows/workflow-skill-extractor.lock.yml index 5bc17bbb54d..4cca97e527b 100644 --- a/.github/workflows/workflow-skill-extractor.lock.yml +++ b/.github/workflows/workflow-skill-extractor.lock.yml @@ -160,6 +160,33 @@ jobs: Tools: create_issue(max:3), create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -607,6 +634,12 @@ jobs: } } GH_AW_MCP_CONFIG_c96a2c2698a1a0f4_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/actions/setup/sh/mount_mcp_as_cli.sh b/actions/setup/sh/mount_mcp_as_cli.sh new file mode 100755 index 00000000000..38e42d5c6e7 --- /dev/null +++ b/actions/setup/sh/mount_mcp_as_cli.sh @@ -0,0 +1,309 @@ +#!/usr/bin/env bash +# mount_mcp_as_cli.sh +# +# Mounts MCP servers as local CLI tools, allowing agents to call MCP tools +# directly from the command line using a familiar shell interface. +# +# Reads the manifest saved by start_mcp_gateway.sh, queries each server for +# its tool list, and generates a standalone CLI wrapper script for each server. +# +# Generated CLI wrapper usage: +# --help Show all available commands +# --help Show help for a specific command +# [--param value...] Execute a command +# +# Environment variables: +# MCP_GATEWAY_API_KEY API key for MCP gateway authentication (required) +# +# Outputs (GitHub Actions): +# mounted-servers Comma-separated list of mounted server names +# +# Side effects: +# - Creates /tmp/gh-aw/mcp-cli/bin/ with CLI wrapper scripts (chmod 555) +# - Creates /tmp/gh-aw/mcp-cli/tools/ with per-server tool JSON caches +# - Appends /tmp/gh-aw/mcp-cli/bin to $GITHUB_PATH + +set -eo pipefail + +MANIFEST="/tmp/gh-aw/mcp-cli/manifest.json" +CLI_BIN_DIR="/tmp/gh-aw/mcp-cli/bin" +TOOLS_DIR="/tmp/gh-aw/mcp-cli/tools" + +# Internal MCP infrastructure servers that should not be exposed as user-facing CLIs +INTERNAL_SERVERS=("safeoutputs" "mcp-scripts") + +is_internal_server() { + local name="$1" + for internal in "${INTERNAL_SERVERS[@]}"; do + if [ "$name" = "$internal" ]; then + return 0 + fi + done + return 1 +} + +if [ ! -f "$MANIFEST" ]; then + echo "No MCP CLI manifest found at $MANIFEST, skipping CLI mounting" + exit 0 +fi + +echo "Mounting MCP servers as CLI tools..." +mkdir -p "$CLI_BIN_DIR" "$TOOLS_DIR" + +MOUNTED_SERVERS=() + +while IFS= read -r server_entry; do + SERVER_NAME=$(echo "$server_entry" | jq -r '.name') + SERVER_URL=$(echo "$server_entry" | jq -r '.url') + + # Skip internal infrastructure servers + if is_internal_server "$SERVER_NAME"; then + echo "Skipping internal server: $SERVER_NAME" + continue + fi + + echo "Mounting MCP server '$SERVER_NAME' (url: $SERVER_URL)..." + + TOOLS_FILE="$TOOLS_DIR/$SERVER_NAME.json" + + # Query tools list from the MCP server via the gateway + # Step 1: Initialize to establish a session (required by stateful transports) + INIT_RESP=$(curl -s -i --max-time 15 -X POST "$SERVER_URL" \ + -H "Authorization: Bearer $MCP_GATEWAY_API_KEY" \ + -H "Content-Type: application/json" \ + -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"mcp-cli-mount","version":"1.0.0"},"protocolVersion":"2024-11-05"}}' \ + 2>/dev/null || echo "") + + SESSION_ID=$(echo "$INIT_RESP" | grep -i "^mcp-session-id:" | awk '{print $2}' | tr -d '\r' 2>/dev/null || echo "") + + # Step 2: Fetch the tool list + SESSION_HEADER_ARG=() + if [ -n "$SESSION_ID" ]; then + SESSION_HEADER_ARG=(-H "Mcp-Session-Id: $SESSION_ID") + fi + + TOOLS_RESP=$(curl -s --max-time 15 -X POST "$SERVER_URL" \ + -H "Authorization: Bearer $MCP_GATEWAY_API_KEY" \ + -H "Content-Type: application/json" \ + "${SESSION_HEADER_ARG[@]}" \ + -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \ + 2>/dev/null || echo "{}") + + # Save tools to cache file (empty array if unavailable) + if ! echo "$TOOLS_RESP" | jq -c '.result.tools // []' > "$TOOLS_FILE" 2>/dev/null; then + echo "[]" > "$TOOLS_FILE" + fi + chmod 644 "$TOOLS_FILE" + + TOOL_COUNT=$(jq '. | length' "$TOOLS_FILE" 2>/dev/null || echo "0") + echo " Found $TOOL_COUNT tool(s)" + + # Generate CLI wrapper script for this server + CLI_SCRIPT="$CLI_BIN_DIR/$SERVER_NAME" + + # Write header with values baked in at creation time + cat > "$CLI_SCRIPT" << SCRIPT_EOF +#!/usr/bin/env bash +# MCP CLI wrapper for: $SERVER_NAME +# Auto-generated by gh-aw. Do not modify. +# +# Usage: +# $SERVER_NAME --help Show all available commands +# $SERVER_NAME --help Show help for a specific command +# $SERVER_NAME [--param value...] Execute a command +# +# Connects to: $SERVER_URL + +SERVER_NAME="$SERVER_NAME" +SERVER_URL="$SERVER_URL" +TOOLS_FILE="$TOOLS_FILE" + +# API key injected from the workflow environment +API_KEY="\${MCP_GATEWAY_API_KEY:-}" +if [ -z "\$API_KEY" ]; then + echo "Error: MCP_GATEWAY_API_KEY environment variable is not set" >&2 + exit 1 +fi + +load_tools() { + if [ -f "\$TOOLS_FILE" ]; then + cat "\$TOOLS_FILE" + else + echo "[]" + fi +} + +show_help() { + local tools + tools=\$(load_tools) + echo "Usage: \$SERVER_NAME [options]" + echo "" + echo "Available commands:" + if command -v jq &>/dev/null && echo "\$tools" | jq -e 'length > 0' >/dev/null 2>&1; then + echo "\$tools" | jq -r '.[] | " \(.name)\t\(.description // "No description")"' \ + | column -t -s \$'\t' 2>/dev/null \ + || echo "\$tools" | jq -r '.[] | " \(.name) \(.description // "")"' + else + echo " (tool list unavailable)" + fi + echo "" + echo "Run '\$SERVER_NAME --help' for more information on a command." +} + +show_tool_help() { + local tool_name="\$1" + local tools tool + tools=\$(load_tools) + tool=\$(echo "\$tools" | jq -r ".[] | select(.name == \"\$tool_name\")" 2>/dev/null || echo "") + + if [ -z "\$tool" ]; then + echo "Error: Unknown command '\$tool_name'" >&2 + echo "Run '\$SERVER_NAME --help' to see available commands." >&2 + exit 1 + fi + + echo "Command: \$tool_name" + echo "Description: \$(echo "\$tool" | jq -r '.description // "No description"')" + + local has_props + has_props=\$(echo "\$tool" | jq -r 'has("inputSchema") and ((.inputSchema.properties // {}) | length > 0)') + + if [ "\$has_props" = "true" ]; then + echo "" + echo "Options:" + echo "\$tool" | jq -r '.inputSchema.properties | to_entries[] | + " --\(.key) \(.value.description // .value.type // "string")"' + local required + required=\$(echo "\$tool" | jq -r '(.inputSchema.required // []) | join(", ")') + if [ -n "\$required" ]; then + echo "" + echo "Required: \$required" + fi + fi +} + +call_tool() { + local tool_name="\$1" + shift + + # Parse --key value arguments into a JSON object + local args="{}" + while [[ \$# -gt 0 ]]; do + if [[ "\$1" == --* ]]; then + local key="\${1#--}" + if [[ \$# -ge 2 && "\$2" != --* ]]; then + local val="\$2" + args=\$(echo "\$args" | jq --arg k "\$key" --arg v "\$val" '. + {(\$k): \$v}') + shift 2 + else + args=\$(echo "\$args" | jq --arg k "\$key" '. + {(\$k): true}') + shift 1 + fi + else + shift + fi + done + + # Initialize MCP session to establish a stateful connection + local init_resp session_id + init_resp=\$(curl -s -i --max-time 30 -X POST "\$SERVER_URL" \ + -H "Authorization: Bearer \$API_KEY" \ + -H "Content-Type: application/json" \ + -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"mcp-cli","version":"1.0.0"},"protocolVersion":"2024-11-05"}}' \ + 2>/dev/null || echo "") + + session_id=\$(echo "\$init_resp" | grep -i "^mcp-session-id:" | awk '{print \$2}' | tr -d '\r' 2>/dev/null || echo "") + + # Build tool call request + local request + request=\$(jq -n --arg name "\$tool_name" --argjson args "\$args" \ + '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":\$name,"arguments":\$args}}') + + # Invoke the tool via the gateway + local session_header_args=() + if [ -n "\$session_id" ]; then + session_header_args=(-H "Mcp-Session-Id: \$session_id") + fi + + local response + response=\$(curl -s --max-time 120 -X POST "\$SERVER_URL" \ + -H "Authorization: Bearer \$API_KEY" \ + -H "Content-Type: application/json" \ + "\${session_header_args[@]}" \ + -d "\$request" \ + 2>/dev/null) + + # Surface JSON-RPC errors + if echo "\$response" | jq -e '.error' >/dev/null 2>&1; then + local err_msg err_code + err_msg=\$(echo "\$response" | jq -r '.error.message // "Unknown error"') + err_code=\$(echo "\$response" | jq -r '.error.code // ""') + if [ -n "\$err_code" ]; then + echo "Error [\$err_code]: \$err_msg" >&2 + else + echo "Error: \$err_msg" >&2 + fi + exit 1 + fi + + # Print result content + if echo "\$response" | jq -e '.result.content' >/dev/null 2>&1; then + echo "\$response" | jq -r '.result.content[] | + if .type == "text" then .text + elif .type == "image" then "[image data - \(.mimeType // "unknown")]" + else (. | tostring) + end' + elif echo "\$response" | jq -e '.result' >/dev/null 2>&1; then + echo "\$response" | jq -r '.result' + else + echo "\$response" + fi +} + +# Main entry point +if [[ \$# -eq 0 || "\$1" == "--help" || "\$1" == "-h" ]]; then + show_help + exit 0 +fi + +COMMAND="\$1" +shift + +if [[ "\$1" == "--help" || "\$1" == "-h" ]]; then + show_tool_help "\$COMMAND" + exit 0 +fi + +call_tool "\$COMMAND" "\$@" +SCRIPT_EOF + + chmod 755 "$CLI_SCRIPT" + MOUNTED_SERVERS+=("$SERVER_NAME") + echo " ✓ Mounted as: $CLI_SCRIPT" +done < <(jq -c '.servers[]' "$MANIFEST") + +if [ "${#MOUNTED_SERVERS[@]}" -eq 0 ]; then + echo "No MCP servers mounted as CLI tools" + exit 0 +fi + +# Lock the CLI bin directory to prevent modification by the agent +chmod 555 "$CLI_BIN_DIR" + +# Add CLI bin directory to PATH for subsequent steps +echo "$CLI_BIN_DIR" >> "$GITHUB_PATH" + +echo "" +echo "Successfully mounted ${#MOUNTED_SERVERS[@]} MCP server(s) as CLI tools:" +for name in "${MOUNTED_SERVERS[@]}"; do + echo " - $name" +done +echo "" +echo "CLI bin directory: $CLI_BIN_DIR (read-only)" +echo "Added to PATH: yes (takes effect in subsequent steps)" + +# Emit GitHub Actions step output with the list of mounted servers +printf "mounted-servers=%s\n" "$( + IFS=',' + echo "${MOUNTED_SERVERS[*]}" +)" >> "$GITHUB_OUTPUT" diff --git a/actions/setup/sh/start_mcp_gateway.sh b/actions/setup/sh/start_mcp_gateway.sh index 979fb86aa4d..67db98ada72 100755 --- a/actions/setup/sh/start_mcp_gateway.sh +++ b/actions/setup/sh/start_mcp_gateway.sh @@ -438,6 +438,22 @@ else fi echo "" +# Save CLI manifest for mount_mcp_as_cli.sh before gateway config is deleted +# The manifest contains server names and their local localhost URLs +echo "Saving MCP CLI manifest..." +mkdir -p /tmp/gh-aw/mcp-cli +if [ -f /tmp/gh-aw/mcp-config/gateway-output.json ] && \ + jq -e '.mcpServers' /tmp/gh-aw/mcp-config/gateway-output.json >/dev/null 2>&1; then + jq '{servers: [.mcpServers | to_entries[] | select(.value.url != null) | {name: .key, url: .value.url}]}' \ + /tmp/gh-aw/mcp-config/gateway-output.json > /tmp/gh-aw/mcp-cli/manifest.json + chmod 600 /tmp/gh-aw/mcp-cli/manifest.json + SERVER_COUNT=$(jq '.servers | length' /tmp/gh-aw/mcp-cli/manifest.json) + echo "CLI manifest saved with ${SERVER_COUNT} server(s)" +else + echo "WARNING: No mcpServers in gateway output, CLI manifest not created" +fi +echo "" + # Delete gateway configuration file after conversion and checks are complete echo "Cleaning up gateway configuration file..." if [ -f /tmp/gh-aw/mcp-config/gateway-output.json ]; then diff --git a/pkg/workflow/compiler_yaml_main_job.go b/pkg/workflow/compiler_yaml_main_job.go index 62f3d025243..6dfb7596f89 100644 --- a/pkg/workflow/compiler_yaml_main_job.go +++ b/pkg/workflow/compiler_yaml_main_job.go @@ -275,6 +275,9 @@ func (c *Compiler) generateMainJobSteps(yaml *strings.Builder, data *WorkflowDat return fmt.Errorf("failed to generate MCP setup: %w", err) } + // Mount MCP servers as CLI tools (runs after gateway is started) + c.generateMCPCLIMountStep(yaml, data) + // Stop-time safety checks are now handled by a dedicated job (stop_time_check) // No longer generated in the main job steps diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go new file mode 100644 index 00000000000..8bc9d7dc642 --- /dev/null +++ b/pkg/workflow/mcp_cli_mount.go @@ -0,0 +1,140 @@ +package workflow + +import ( + "fmt" + "slices" + "sort" + "strings" +) + +// mcp_cli_mount.go generates a workflow step that mounts MCP servers as local CLI tools +// and produces the prompt section that informs the agent about these tools. +// +// After the MCP gateway is started, this step runs mount_mcp_as_cli.sh which: +// - Reads the CLI manifest saved by start_mcp_gateway.sh +// - Queries each server for its tools/list via JSON-RPC +// - Writes a standalone CLI wrapper script for each server to /tmp/gh-aw/mcp-cli/bin/ +// - Locks the bin directory (chmod 555) so the agent cannot modify the scripts +// - Adds the directory to $GITHUB_PATH + +// internalMCPServerNames lists the MCP servers that are internal infrastructure and +// should not be exposed as user-facing CLI tools. +var internalMCPServerNames = map[string]bool{ + "safeoutputs": true, + "mcp-scripts": true, +} + +// getMCPCLIServerNames returns the sorted list of MCP server names that will be +// mounted as CLI tools. It includes standard MCP tools (github, playwright, etc.) +// and custom MCP servers, but excludes internal infrastructure servers. +func getMCPCLIServerNames(data *WorkflowData) []string { + if data == nil { + return nil + } + + var servers []string + + // Collect user-facing standard MCP tools from the raw Tools map + for toolName, toolValue := range data.Tools { + if toolValue == false { + continue + } + // Only include tools that have MCP servers (skip bash, web-fetch, web-search, edit, etc.) + switch toolName { + case "github", "playwright", "qmd", "cache-memory", "agentic-workflows": + servers = append(servers, toolName) + default: + // Include custom MCP servers (not in the internal list) + if !internalMCPServerNames[toolName] { + if mcpConfig, ok := toolValue.(map[string]any); ok { + if hasMcp, _ := hasMCPConfig(mcpConfig); hasMcp { + servers = append(servers, toolName) + } + } + } + } + } + + // Also check ParsedTools.Custom for custom MCP servers + if data.ParsedTools != nil { + for name := range data.ParsedTools.Custom { + if !internalMCPServerNames[name] && !slices.Contains(servers, name) { + servers = append(servers, name) + } + } + } + + sort.Strings(servers) + return servers +} + +// generateMCPCLIMountStep generates the "Mount MCP servers as CLIs" workflow step. +// This step runs after the MCP gateway is started and creates executable CLI wrapper +// scripts for each MCP server in a read-only directory on $PATH. +func (c *Compiler) generateMCPCLIMountStep(yaml *strings.Builder, data *WorkflowData) { + servers := getMCPCLIServerNames(data) + if len(servers) == 0 { + return + } + + yaml.WriteString(" - name: Mount MCP servers as CLIs\n") + yaml.WriteString(" id: mount-mcp-clis\n") + yaml.WriteString(" continue-on-error: true\n") + yaml.WriteString(" env:\n") + yaml.WriteString(" MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }}\n") + yaml.WriteString(" run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh\n") +} + +// buildMCPCLIPromptSection returns a PromptSection describing the CLI tools available +// to the agent, or nil if there are no servers to mount. +func buildMCPCLIPromptSection(data *WorkflowData) *PromptSection { + servers := getMCPCLIServerNames(data) + if len(servers) == 0 { + return nil + } + + // Build the human-readable list of servers with example usage + var listLines []string + for _, name := range servers { + listLines = append(listLines, fmt.Sprintf("- `%s` — run `%s --help` to see available tools", name, name)) + } + serversList := strings.Join(listLines, "\n") + + // The prompt file uses a {MCP_CLI_SERVERS_LIST} placeholder; replace it inline + content := strings.ReplaceAll(mcpCLIToolsPromptTemplate, "{MCP_CLI_SERVERS_LIST}", serversList) + + return &PromptSection{ + Content: content, + IsFile: false, + } +} + +// mcpCLIToolsPromptTemplate is the inline prompt template for MCP CLI tools. +// It uses the {MCP_CLI_SERVERS_LIST} placeholder which is replaced at compile time. +const mcpCLIToolsPromptTemplate = `## MCP Tools Available as CLI Commands + +The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + +{MCP_CLI_SERVERS_LIST} + +### How to Use + +Each server is a standalone command in your PATH. Use them like any other shell command: + +` + "```bash" + ` +# Show all available tools for a server + --help + +# Show help for a specific tool + --help + +# Call a tool with parameters + --param1 value1 --param2 value2 +` + "```" + ` + +### Notes + +- Parameters are passed as ` + "`" + `--name value` + "`" + ` pairs (all values are treated as strings unless the tool accepts booleans, in which case ` + "`" + `--flag` + "`" + ` with no value sets it to ` + "`" + `true` + "`" + `) +- Results are printed to stdout; errors are printed to stderr +- The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly +` diff --git a/pkg/workflow/prompt_constants.go b/pkg/workflow/prompt_constants.go index 6e56b519eed..dac69f2b80e 100644 --- a/pkg/workflow/prompt_constants.go +++ b/pkg/workflow/prompt_constants.go @@ -27,6 +27,7 @@ const ( agenticWorkflowsGuideFile = "agentic_workflows_guide.md" githubMCPToolsPromptFile = "github_mcp_tools_prompt.md" githubMCPToolsWithSafeOutputsPromptFile = "github_mcp_tools_with_safeoutputs_prompt.md" + mcpCLIToolsPromptFile = "mcp_cli_tools_prompt.md" ) // GitHub context prompt is kept embedded because it contains GitHub Actions expressions diff --git a/pkg/workflow/prompts/mcp_cli_tools_prompt.md b/pkg/workflow/prompts/mcp_cli_tools_prompt.md new file mode 100644 index 00000000000..a2f141dfb0a --- /dev/null +++ b/pkg/workflow/prompts/mcp_cli_tools_prompt.md @@ -0,0 +1,26 @@ +## MCP Tools Available as CLI Commands + +The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + +{MCP_CLI_SERVERS_LIST} + +### How to Use + +Each server is a standalone command in your PATH. Use them like any other shell command: + +```bash +# Show all available tools for a server + --help + +# Show help for a specific tool + --help + +# Call a tool with parameters + --param1 value1 --param2 value2 +``` + +### Notes + +- Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) +- Results are printed to stdout; errors are printed to stderr +- The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly diff --git a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden index e777485f867..15468958bb0 100644 --- a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden +++ b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden @@ -113,6 +113,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_NORM_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -347,6 +374,12 @@ jobs: } } GH_AW_MCP_CONFIG_NORM_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden index 7c426adca49..83e106d05de 100644 --- a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden +++ b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden @@ -113,6 +113,33 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_NORM_EOF' + ## MCP Tools Available as CLI Commands + + The following MCP servers have been mounted as local CLI commands and are available directly from the shell: + + - `github` — run `github --help` to see available tools + + ### How to Use + + Each server is a standalone command in your PATH. Use them like any other shell command: + + ```bash + # Show all available tools for a server + --help + + # Show help for a specific tool + --help + + # Call a tool with parameters + --param1 value1 --param2 value2 + ``` + + ### Notes + + - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) + - Results are printed to stdout; errors are printed to stderr + - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -348,6 +375,12 @@ jobs: } } GH_AW_MCP_CONFIG_NORM_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/pkg/workflow/unified_prompt_step.go b/pkg/workflow/unified_prompt_step.go index 3de37295505..67d233b04f3 100644 --- a/pkg/workflow/unified_prompt_step.go +++ b/pkg/workflow/unified_prompt_step.go @@ -194,6 +194,13 @@ func (c *Compiler) collectPromptSections(data *WorkflowData) []PromptSection { // Per-tool sections: opening tag + tools list (inline), tool instruction files, closing tag sections = append(sections, buildSafeOutputsSections(data.SafeOutputs)...) } + + // 8a. MCP CLI tools instructions (if any MCP servers are mounted as CLIs) + if section := buildMCPCLIPromptSection(data); section != nil { + unifiedPromptLog.Printf("Adding MCP CLI tools section: servers=%v", getMCPCLIServerNames(data)) + sections = append(sections, *section) + } + // 9. GitHub context (if GitHub tool is enabled) if hasGitHubTool(data.ParsedTools) { unifiedPromptLog.Print("Adding GitHub context section") From f3d7205f4877dddf6c8985ed1bd30ac510c9faa1 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 14:45:48 +0000 Subject: [PATCH 02/19] refactor: convert mount_mcp_as_cli to github-script, wrap prompt in xml tags - Delete mount_mcp_as_cli.sh shell script - Add mount_mcp_as_cli.cjs using actions/github-script with core.info() logging - Update generateMCPCLIMountStep to use actions/github-script - Wrap MCP CLI prompt section in XML tags - Update golden fixtures and recompile lock files Agent-Logs-Url: https://github.com/github/gh-aw/sessions/1bf60ced-fb56-48d7-a2ce-b870a185cc27 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/ace-editor.lock.yml | 10 +- .../agent-performance-analyzer.lock.yml | 10 +- .../workflows/agent-persona-explorer.lock.yml | 10 +- .../agentic-observability-kit.lock.yml | 10 +- .github/workflows/ai-moderator.lock.yml | 10 +- .github/workflows/archie.lock.yml | 10 +- .github/workflows/artifacts-summary.lock.yml | 10 +- .github/workflows/audit-workflows.lock.yml | 10 +- .github/workflows/auto-triage-issues.lock.yml | 10 +- .github/workflows/blog-auditor.lock.yml | 10 +- .github/workflows/bot-detection.lock.yml | 10 +- .github/workflows/brave.lock.yml | 10 +- .../breaking-change-checker.lock.yml | 10 +- .github/workflows/changeset.lock.yml | 10 +- .github/workflows/ci-coach.lock.yml | 10 +- .github/workflows/ci-doctor.lock.yml | 10 +- .../claude-code-user-docs-review.lock.yml | 10 +- .../cli-consistency-checker.lock.yml | 10 +- .../workflows/cli-version-checker.lock.yml | 10 +- .github/workflows/cloclo.lock.yml | 10 +- .../workflows/code-scanning-fixer.lock.yml | 10 +- .github/workflows/code-simplifier.lock.yml | 10 +- .../codex-github-remote-mcp-test.lock.yml | 10 +- .../commit-changes-analyzer.lock.yml | 10 +- .../constraint-solving-potd.lock.yml | 10 +- .github/workflows/contribution-check.lock.yml | 10 +- .../workflows/copilot-agent-analysis.lock.yml | 10 +- .../copilot-cli-deep-research.lock.yml | 10 +- .../copilot-pr-merged-report.lock.yml | 10 +- .../copilot-pr-nlp-analysis.lock.yml | 10 +- .../copilot-pr-prompt-analysis.lock.yml | 10 +- .../copilot-session-insights.lock.yml | 10 +- .github/workflows/craft.lock.yml | 10 +- .../daily-architecture-diagram.lock.yml | 10 +- .../daily-assign-issue-to-user.lock.yml | 10 +- .github/workflows/daily-choice-test.lock.yml | 10 +- .../workflows/daily-cli-performance.lock.yml | 10 +- .../workflows/daily-cli-tools-tester.lock.yml | 10 +- .github/workflows/daily-code-metrics.lock.yml | 10 +- .../daily-community-attribution.lock.yml | 10 +- .../workflows/daily-compiler-quality.lock.yml | 10 +- .../daily-copilot-token-report.lock.yml | 10 +- .github/workflows/daily-doc-healer.lock.yml | 10 +- .github/workflows/daily-doc-updater.lock.yml | 10 +- .github/workflows/daily-fact.lock.yml | 10 +- .github/workflows/daily-file-diet.lock.yml | 10 +- .../workflows/daily-firewall-report.lock.yml | 10 +- .../workflows/daily-function-namer.lock.yml | 10 +- .../daily-integrity-analysis.lock.yml | 10 +- .../workflows/daily-issues-report.lock.yml | 10 +- .../daily-malicious-code-scan.lock.yml | 10 +- .../daily-mcp-concurrency-analysis.lock.yml | 10 +- .../daily-multi-device-docs-tester.lock.yml | 10 +- .github/workflows/daily-news.lock.yml | 10 +- .../daily-observability-report.lock.yml | 10 +- .../daily-performance-summary.lock.yml | 10 +- .github/workflows/daily-regulatory.lock.yml | 10 +- .../daily-rendering-scripts-verifier.lock.yml | 10 +- .../workflows/daily-repo-chronicle.lock.yml | 10 +- .../daily-safe-output-integrator.lock.yml | 10 +- .../daily-safe-output-optimizer.lock.yml | 10 +- .../daily-safe-outputs-conformance.lock.yml | 10 +- .../workflows/daily-secrets-analysis.lock.yml | 10 +- .../daily-security-red-team.lock.yml | 10 +- .github/workflows/daily-semgrep-scan.lock.yml | 10 +- .../daily-syntax-error-quality.lock.yml | 10 +- .../daily-team-evolution-insights.lock.yml | 10 +- .github/workflows/daily-team-status.lock.yml | 10 +- .../daily-testify-uber-super-expert.lock.yml | 10 +- .../workflows/daily-workflow-updater.lock.yml | 10 +- .github/workflows/dead-code-remover.lock.yml | 10 +- .github/workflows/deep-report.lock.yml | 10 +- .github/workflows/delight.lock.yml | 10 +- .github/workflows/dependabot-burner.lock.yml | 10 +- .../workflows/dependabot-go-checker.lock.yml | 10 +- .github/workflows/dev-hawk.lock.yml | 10 +- .github/workflows/dev.lock.yml | 10 +- .../developer-docs-consolidator.lock.yml | 10 +- .github/workflows/dictation-prompt.lock.yml | 10 +- .../workflows/discussion-task-miner.lock.yml | 10 +- .github/workflows/docs-noob-tester.lock.yml | 10 +- .github/workflows/draft-pr-cleanup.lock.yml | 10 +- .../duplicate-code-detector.lock.yml | 10 +- .../example-permissions-warning.lock.yml | 10 +- .../example-workflow-analyzer.lock.yml | 10 +- .github/workflows/firewall-escape.lock.yml | 10 +- .github/workflows/firewall.lock.yml | 10 +- .../workflows/functional-pragmatist.lock.yml | 10 +- .../github-mcp-structural-analysis.lock.yml | 10 +- .../github-mcp-tools-report.lock.yml | 10 +- .../github-remote-mcp-auth-test.lock.yml | 10 +- .../workflows/glossary-maintainer.lock.yml | 10 +- .github/workflows/go-fan.lock.yml | 10 +- .github/workflows/go-logger.lock.yml | 10 +- .../workflows/go-pattern-detector.lock.yml | 10 +- .github/workflows/gpclean.lock.yml | 10 +- .github/workflows/grumpy-reviewer.lock.yml | 10 +- .github/workflows/hourly-ci-cleaner.lock.yml | 10 +- .../workflows/instructions-janitor.lock.yml | 10 +- .github/workflows/issue-arborist.lock.yml | 10 +- .github/workflows/issue-monster.lock.yml | 10 +- .github/workflows/issue-triage-agent.lock.yml | 10 +- .github/workflows/jsweep.lock.yml | 10 +- .../workflows/layout-spec-maintainer.lock.yml | 10 +- .github/workflows/lockfile-stats.lock.yml | 10 +- .github/workflows/mcp-inspector.lock.yml | 10 +- .github/workflows/mergefest.lock.yml | 10 +- .github/workflows/metrics-collector.lock.yml | 10 +- .../workflows/notion-issue-summary.lock.yml | 10 +- .github/workflows/org-health-report.lock.yml | 10 +- .github/workflows/pdf-summary.lock.yml | 10 +- .github/workflows/plan.lock.yml | 10 +- .github/workflows/poem-bot.lock.yml | 10 +- .github/workflows/portfolio-analyst.lock.yml | 10 +- .../workflows/pr-nitpick-reviewer.lock.yml | 10 +- .github/workflows/pr-triage-agent.lock.yml | 10 +- .../prompt-clustering-analysis.lock.yml | 10 +- .github/workflows/python-data-charts.lock.yml | 10 +- .github/workflows/q.lock.yml | 10 +- .github/workflows/refiner.lock.yml | 10 +- .github/workflows/release.lock.yml | 10 +- .../workflows/repo-audit-analyzer.lock.yml | 10 +- .github/workflows/repo-tree-map.lock.yml | 10 +- .../repository-quality-improver.lock.yml | 10 +- .github/workflows/research.lock.yml | 10 +- .github/workflows/safe-output-health.lock.yml | 10 +- .../schema-consistency-checker.lock.yml | 10 +- .../schema-feature-coverage.lock.yml | 10 +- .github/workflows/scout.lock.yml | 10 +- .../workflows/security-compliance.lock.yml | 10 +- .github/workflows/security-review.lock.yml | 10 +- .../semantic-function-refactor.lock.yml | 10 +- .github/workflows/sergo.lock.yml | 10 +- .../workflows/slide-deck-maintainer.lock.yml | 10 +- .../workflows/smoke-agent-all-merged.lock.yml | 10 +- .../workflows/smoke-agent-all-none.lock.yml | 10 +- .../smoke-agent-public-approved.lock.yml | 10 +- .../smoke-agent-public-none.lock.yml | 10 +- .../smoke-agent-scoped-approved.lock.yml | 10 +- .../workflows/smoke-call-workflow.lock.yml | 10 +- .github/workflows/smoke-claude.lock.yml | 10 +- .github/workflows/smoke-codex.lock.yml | 10 +- .github/workflows/smoke-copilot-arm.lock.yml | 10 +- .github/workflows/smoke-copilot.lock.yml | 10 +- .../smoke-create-cross-repo-pr.lock.yml | 10 +- .github/workflows/smoke-gemini.lock.yml | 10 +- .github/workflows/smoke-multi-pr.lock.yml | 10 +- .github/workflows/smoke-project.lock.yml | 10 +- .../workflows/smoke-service-ports.lock.yml | 10 +- .github/workflows/smoke-temporary-id.lock.yml | 10 +- .github/workflows/smoke-test-tools.lock.yml | 10 +- .../smoke-update-cross-repo-pr.lock.yml | 10 +- .../smoke-workflow-call-with-inputs.lock.yml | 10 +- .../workflows/smoke-workflow-call.lock.yml | 10 +- .../workflows/stale-repo-identifier.lock.yml | 10 +- .../workflows/static-analysis-report.lock.yml | 10 +- .../workflows/step-name-alignment.lock.yml | 10 +- .github/workflows/sub-issue-closer.lock.yml | 10 +- .github/workflows/super-linter.lock.yml | 10 +- .../workflows/technical-doc-writer.lock.yml | 10 +- .github/workflows/terminal-stylist.lock.yml | 10 +- .../test-create-pr-error-handling.lock.yml | 10 +- .github/workflows/test-dispatcher.lock.yml | 10 +- .../test-project-url-default.lock.yml | 10 +- .github/workflows/test-workflow.lock.yml | 10 +- .github/workflows/tidy.lock.yml | 10 +- .github/workflows/typist.lock.yml | 10 +- .../workflows/ubuntu-image-analyzer.lock.yml | 10 +- .github/workflows/unbloat-docs.lock.yml | 10 +- .github/workflows/update-astro.lock.yml | 10 +- .github/workflows/video-analyzer.lock.yml | 10 +- .../weekly-blog-post-writer.lock.yml | 10 +- .../weekly-editors-health-check.lock.yml | 10 +- .../workflows/weekly-issue-summary.lock.yml | 10 +- .../weekly-safe-outputs-spec-review.lock.yml | 10 +- .github/workflows/workflow-generator.lock.yml | 10 +- .../workflow-health-manager.lock.yml | 10 +- .../workflows/workflow-normalizer.lock.yml | 10 +- .../workflow-skill-extractor.lock.yml | 10 +- actions/setup/js/mount_mcp_as_cli.cjs | 419 ++++++++++++++++++ actions/setup/sh/mount_mcp_as_cli.sh | 309 ------------- pkg/workflow/mcp_cli_mount.go | 17 +- .../basic-copilot.golden | 10 +- .../with-imports.golden | 10 +- 184 files changed, 2061 insertions(+), 494 deletions(-) create mode 100644 actions/setup/js/mount_mcp_as_cli.cjs delete mode 100755 actions/setup/sh/mount_mcp_as_cli.sh diff --git a/.github/workflows/ace-editor.lock.yml b/.github/workflows/ace-editor.lock.yml index 56d3deaaa67..41515d64a4d 100644 --- a/.github/workflows/ace-editor.lock.yml +++ b/.github/workflows/ace-editor.lock.yml @@ -189,6 +189,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_3b0f91d4e2fcc9d9_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -215,6 +216,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -443,7 +445,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agent-performance-analyzer.lock.yml b/.github/workflows/agent-performance-analyzer.lock.yml index 910c1ab54b0..cd938b34965 100644 --- a/.github/workflows/agent-performance-analyzer.lock.yml +++ b/.github/workflows/agent-performance-analyzer.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: add_comment(max:10), create_issue(max:5), create_discussion(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -760,7 +762,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agent-persona-explorer.lock.yml b/.github/workflows/agent-persona-explorer.lock.yml index 81a9e86b57c..1a8bda48281 100644 --- a/.github/workflows/agent-persona-explorer.lock.yml +++ b/.github/workflows/agent-persona-explorer.lock.yml @@ -169,6 +169,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -197,6 +198,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -714,7 +716,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agentic-observability-kit.lock.yml b/.github/workflows/agentic-observability-kit.lock.yml index f7fe0933080..ca62f6e6720 100644 --- a/.github/workflows/agentic-observability-kit.lock.yml +++ b/.github/workflows/agentic-observability-kit.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_issue, create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -720,7 +722,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ai-moderator.lock.yml b/.github/workflows/ai-moderator.lock.yml index 38b4697951c..4ddba695dd9 100644 --- a/.github/workflows/ai-moderator.lock.yml +++ b/.github/workflows/ai-moderator.lock.yml @@ -203,6 +203,7 @@ jobs: Tools: add_labels, hide_comment(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -230,6 +231,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -703,7 +705,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/archie.lock.yml b/.github/workflows/archie.lock.yml index 4af0967db42..0620d70dc3f 100644 --- a/.github/workflows/archie.lock.yml +++ b/.github/workflows/archie.lock.yml @@ -206,6 +206,7 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -233,6 +234,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -721,7 +723,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/artifacts-summary.lock.yml b/.github/workflows/artifacts-summary.lock.yml index 771f72d78cf..7318027f71e 100644 --- a/.github/workflows/artifacts-summary.lock.yml +++ b/.github/workflows/artifacts-summary.lock.yml @@ -154,6 +154,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -180,6 +181,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -600,7 +602,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/audit-workflows.lock.yml b/.github/workflows/audit-workflows.lock.yml index 4d1773dfcbe..ae4bcf11c7a 100644 --- a/.github/workflows/audit-workflows.lock.yml +++ b/.github/workflows/audit-workflows.lock.yml @@ -177,6 +177,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -205,6 +206,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -783,7 +785,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index f5881637756..61254ccbcbd 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -172,6 +172,7 @@ jobs: Tools: create_discussion, add_labels(max:10), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -198,6 +199,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -636,7 +638,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/blog-auditor.lock.yml b/.github/workflows/blog-auditor.lock.yml index 36362009e56..752e5e5917f 100644 --- a/.github/workflows/blog-auditor.lock.yml +++ b/.github/workflows/blog-auditor.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -639,7 +641,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/bot-detection.lock.yml b/.github/workflows/bot-detection.lock.yml index da74a6b1804..011ce0cd923 100644 --- a/.github/workflows/bot-detection.lock.yml +++ b/.github/workflows/bot-detection.lock.yml @@ -162,6 +162,7 @@ jobs: Tools: create_issue, update_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -684,7 +686,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/brave.lock.yml b/.github/workflows/brave.lock.yml index b8fc92d2418..fa601826b94 100644 --- a/.github/workflows/brave.lock.yml +++ b/.github/workflows/brave.lock.yml @@ -196,6 +196,7 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -223,6 +224,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -667,7 +669,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/breaking-change-checker.lock.yml b/.github/workflows/breaking-change-checker.lock.yml index b96c3411a79..6d9e6df621d 100644 --- a/.github/workflows/breaking-change-checker.lock.yml +++ b/.github/workflows/breaking-change-checker.lock.yml @@ -158,6 +158,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -184,6 +185,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -615,7 +617,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index b6f9cd9fe1a..90091a55f29 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -208,6 +208,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_913c1d056bceed0c_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -234,6 +235,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -722,7 +724,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index d8b794edc40..76acf777a33 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -166,6 +166,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_c3b070ffe5979e04_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -193,6 +194,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -690,7 +692,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ci-doctor.lock.yml b/.github/workflows/ci-doctor.lock.yml index 25c0d423b8c..44d31a08930 100644 --- a/.github/workflows/ci-doctor.lock.yml +++ b/.github/workflows/ci-doctor.lock.yml @@ -222,6 +222,7 @@ jobs: Tools: add_comment, create_issue, update_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -249,6 +250,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -843,7 +845,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/claude-code-user-docs-review.lock.yml b/.github/workflows/claude-code-user-docs-review.lock.yml index ed9776f91f6..5848e5595f0 100644 --- a/.github/workflows/claude-code-user-docs-review.lock.yml +++ b/.github/workflows/claude-code-user-docs-review.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -636,7 +638,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cli-consistency-checker.lock.yml b/.github/workflows/cli-consistency-checker.lock.yml index 88337024660..b7947af6e7d 100644 --- a/.github/workflows/cli-consistency-checker.lock.yml +++ b/.github/workflows/cli-consistency-checker.lock.yml @@ -149,6 +149,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -175,6 +176,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -603,7 +605,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cli-version-checker.lock.yml b/.github/workflows/cli-version-checker.lock.yml index d84db4ef343..71f67c09767 100644 --- a/.github/workflows/cli-version-checker.lock.yml +++ b/.github/workflows/cli-version-checker.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -644,7 +646,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index 85b39f6b6dd..96e3b47c977 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -257,6 +257,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_910c108d300753ae_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -287,6 +288,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -944,7 +946,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index 154e218705d..772bcd8accf 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -161,6 +161,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ea41311dd97f7585_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -672,7 +674,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index b59ee3ed26e..97f1c8c733c 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -168,6 +168,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_958f7037a674f6ba_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -194,6 +195,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -627,7 +629,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/codex-github-remote-mcp-test.lock.yml b/.github/workflows/codex-github-remote-mcp-test.lock.yml index 610ac910acf..24e08f2def1 100644 --- a/.github/workflows/codex-github-remote-mcp-test.lock.yml +++ b/.github/workflows/codex-github-remote-mcp-test.lock.yml @@ -151,6 +151,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_3d136f493b7edd72_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -177,6 +178,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -431,7 +433,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/commit-changes-analyzer.lock.yml b/.github/workflows/commit-changes-analyzer.lock.yml index bc6a18ee1be..6f236e424f4 100644 --- a/.github/workflows/commit-changes-analyzer.lock.yml +++ b/.github/workflows/commit-changes-analyzer.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -189,6 +190,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -610,7 +612,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/constraint-solving-potd.lock.yml b/.github/workflows/constraint-solving-potd.lock.yml index 78b33d332a9..d2f02a42d2f 100644 --- a/.github/workflows/constraint-solving-potd.lock.yml +++ b/.github/workflows/constraint-solving-potd.lock.yml @@ -158,6 +158,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -185,6 +186,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -607,7 +609,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/contribution-check.lock.yml b/.github/workflows/contribution-check.lock.yml index 3b1123c7fde..4806d98ce01 100644 --- a/.github/workflows/contribution-check.lock.yml +++ b/.github/workflows/contribution-check.lock.yml @@ -159,6 +159,7 @@ jobs: Tools: add_comment(max:10), create_issue, add_labels(max:4), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -185,6 +186,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -650,7 +652,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-agent-analysis.lock.yml b/.github/workflows/copilot-agent-analysis.lock.yml index 57bf012de22..89a7575917c 100644 --- a/.github/workflows/copilot-agent-analysis.lock.yml +++ b/.github/workflows/copilot-agent-analysis.lock.yml @@ -171,6 +171,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -198,6 +199,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -675,7 +677,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-cli-deep-research.lock.yml b/.github/workflows/copilot-cli-deep-research.lock.yml index cfad61e183a..d4f49d2daf7 100644 --- a/.github/workflows/copilot-cli-deep-research.lock.yml +++ b/.github/workflows/copilot-cli-deep-research.lock.yml @@ -155,6 +155,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -181,6 +182,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -627,7 +629,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-merged-report.lock.yml b/.github/workflows/copilot-pr-merged-report.lock.yml index 6e2202d7846..9340a9176f6 100644 --- a/.github/workflows/copilot-pr-merged-report.lock.yml +++ b/.github/workflows/copilot-pr-merged-report.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -765,7 +767,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-nlp-analysis.lock.yml b/.github/workflows/copilot-pr-nlp-analysis.lock.yml index fa7d2a8ee91..678dd74d972 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.lock.yml +++ b/.github/workflows/copilot-pr-nlp-analysis.lock.yml @@ -168,6 +168,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -722,7 +724,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-prompt-analysis.lock.yml b/.github/workflows/copilot-pr-prompt-analysis.lock.yml index cdfe9a8d32f..e3eb83c14d5 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.lock.yml +++ b/.github/workflows/copilot-pr-prompt-analysis.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -669,7 +671,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-session-insights.lock.yml b/.github/workflows/copilot-session-insights.lock.yml index b6cde92b53d..b7ba315c834 100644 --- a/.github/workflows/copilot-session-insights.lock.yml +++ b/.github/workflows/copilot-session-insights.lock.yml @@ -177,6 +177,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -204,6 +205,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -726,7 +728,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index 998643c5f7d..4f623c0c8a1 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -195,6 +195,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_c7b97f63987d3f1e_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -221,6 +222,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -671,7 +673,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-architecture-diagram.lock.yml b/.github/workflows/daily-architecture-diagram.lock.yml index a33a49d077d..0b6db06a121 100644 --- a/.github/workflows/daily-architecture-diagram.lock.yml +++ b/.github/workflows/daily-architecture-diagram.lock.yml @@ -160,6 +160,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f5a79467418a74fe_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -671,7 +673,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-assign-issue-to-user.lock.yml b/.github/workflows/daily-assign-issue-to-user.lock.yml index 308342621b9..245c408125a 100644 --- a/.github/workflows/daily-assign-issue-to-user.lock.yml +++ b/.github/workflows/daily-assign-issue-to-user.lock.yml @@ -148,6 +148,7 @@ jobs: Tools: add_comment, assign_to_user, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -174,6 +175,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -606,7 +608,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-choice-test.lock.yml b/.github/workflows/daily-choice-test.lock.yml index a508b6a7613..8dba9ab3036 100644 --- a/.github/workflows/daily-choice-test.lock.yml +++ b/.github/workflows/daily-choice-test.lock.yml @@ -157,6 +157,7 @@ jobs: Tools: missing_tool, missing_data, noop, test_environment + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -183,6 +184,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -604,7 +606,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-cli-performance.lock.yml b/.github/workflows/daily-cli-performance.lock.yml index 50b5d299dd0..4382f3795a6 100644 --- a/.github/workflows/daily-cli-performance.lock.yml +++ b/.github/workflows/daily-cli-performance.lock.yml @@ -184,6 +184,7 @@ jobs: Tools: add_comment(max:5), create_issue(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -210,6 +211,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -826,7 +828,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-cli-tools-tester.lock.yml b/.github/workflows/daily-cli-tools-tester.lock.yml index 76e1f0b8a6e..e288c092b2b 100644 --- a/.github/workflows/daily-cli-tools-tester.lock.yml +++ b/.github/workflows/daily-cli-tools-tester.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -693,7 +695,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-code-metrics.lock.yml b/.github/workflows/daily-code-metrics.lock.yml index cf9e8f856e0..1b361b987ea 100644 --- a/.github/workflows/daily-code-metrics.lock.yml +++ b/.github/workflows/daily-code-metrics.lock.yml @@ -172,6 +172,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -199,6 +200,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -702,7 +704,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-community-attribution.lock.yml b/.github/workflows/daily-community-attribution.lock.yml index e22a890baaa..4cc6f0fa01f 100644 --- a/.github/workflows/daily-community-attribution.lock.yml +++ b/.github/workflows/daily-community-attribution.lock.yml @@ -165,6 +165,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_3a6544334ea882c2_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -652,7 +654,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-compiler-quality.lock.yml b/.github/workflows/daily-compiler-quality.lock.yml index d98810cef0c..ec03f30a235 100644 --- a/.github/workflows/daily-compiler-quality.lock.yml +++ b/.github/workflows/daily-compiler-quality.lock.yml @@ -160,6 +160,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -692,7 +694,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-copilot-token-report.lock.yml b/.github/workflows/daily-copilot-token-report.lock.yml index 0e92b4a2868..6b567a28aec 100644 --- a/.github/workflows/daily-copilot-token-report.lock.yml +++ b/.github/workflows/daily-copilot-token-report.lock.yml @@ -168,6 +168,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -744,7 +746,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-doc-healer.lock.yml b/.github/workflows/daily-doc-healer.lock.yml index 01489c7efc8..be655c21791 100644 --- a/.github/workflows/daily-doc-healer.lock.yml +++ b/.github/workflows/daily-doc-healer.lock.yml @@ -172,6 +172,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_1ab69342d96baba9_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -200,6 +201,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -757,7 +759,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index a12729b9a44..e5db6d8f8f8 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -171,6 +171,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f28225f88d7db532_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -199,6 +200,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -721,7 +723,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-fact.lock.yml b/.github/workflows/daily-fact.lock.yml index db30e473290..fb646372b3d 100644 --- a/.github/workflows/daily-fact.lock.yml +++ b/.github/workflows/daily-fact.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -696,7 +698,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-file-diet.lock.yml b/.github/workflows/daily-file-diet.lock.yml index 4b958233d7c..c539a6cb628 100644 --- a/.github/workflows/daily-file-diet.lock.yml +++ b/.github/workflows/daily-file-diet.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -682,7 +684,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-firewall-report.lock.yml b/.github/workflows/daily-firewall-report.lock.yml index 4d9b0351b82..796c8f31edd 100644 --- a/.github/workflows/daily-firewall-report.lock.yml +++ b/.github/workflows/daily-firewall-report.lock.yml @@ -172,6 +172,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -200,6 +201,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -755,7 +757,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-function-namer.lock.yml b/.github/workflows/daily-function-namer.lock.yml index 7b6d2945714..01dc324e327 100644 --- a/.github/workflows/daily-function-namer.lock.yml +++ b/.github/workflows/daily-function-namer.lock.yml @@ -166,6 +166,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -194,6 +195,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -701,7 +703,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-integrity-analysis.lock.yml b/.github/workflows/daily-integrity-analysis.lock.yml index e45d43e9ceb..33eb9655685 100644 --- a/.github/workflows/daily-integrity-analysis.lock.yml +++ b/.github/workflows/daily-integrity-analysis.lock.yml @@ -172,6 +172,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -200,6 +201,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -772,7 +774,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-issues-report.lock.yml b/.github/workflows/daily-issues-report.lock.yml index 4c71e5b3324..7e07c7bdaf9 100644 --- a/.github/workflows/daily-issues-report.lock.yml +++ b/.github/workflows/daily-issues-report.lock.yml @@ -178,6 +178,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -205,6 +206,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -752,7 +754,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-malicious-code-scan.lock.yml b/.github/workflows/daily-malicious-code-scan.lock.yml index d96de2b2d7f..79a3b251170 100644 --- a/.github/workflows/daily-malicious-code-scan.lock.yml +++ b/.github/workflows/daily-malicious-code-scan.lock.yml @@ -154,6 +154,7 @@ jobs: Tools: create_code_scanning_alert, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -180,6 +181,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -613,7 +615,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml index a85de50a956..d0043e5a44c 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml +++ b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml @@ -159,6 +159,7 @@ jobs: Tools: create_issue(max:5), create_agent_session(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -713,7 +715,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml index 5860eefc2a8..d29c3ea6715 100644 --- a/.github/workflows/daily-multi-device-docs-tester.lock.yml +++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml @@ -170,6 +170,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -197,6 +198,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -673,7 +675,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-news.lock.yml b/.github/workflows/daily-news.lock.yml index 0d565c509fb..f2d76d35b7e 100644 --- a/.github/workflows/daily-news.lock.yml +++ b/.github/workflows/daily-news.lock.yml @@ -167,6 +167,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -795,7 +797,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml index c5d5eade1fe..6e7a48582d5 100644 --- a/.github/workflows/daily-observability-report.lock.yml +++ b/.github/workflows/daily-observability-report.lock.yml @@ -170,6 +170,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -197,6 +198,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -734,7 +736,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-performance-summary.lock.yml b/.github/workflows/daily-performance-summary.lock.yml index 248fbafd8d1..1d0be241a76 100644 --- a/.github/workflows/daily-performance-summary.lock.yml +++ b/.github/workflows/daily-performance-summary.lock.yml @@ -169,6 +169,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1152,7 +1154,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-regulatory.lock.yml b/.github/workflows/daily-regulatory.lock.yml index 563a020f4cb..ccdfe6cf107 100644 --- a/.github/workflows/daily-regulatory.lock.yml +++ b/.github/workflows/daily-regulatory.lock.yml @@ -162,6 +162,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1084,7 +1086,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 5f8841c4eb9..015da5d6743 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -176,6 +176,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_526dda5557e006b5_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -204,6 +205,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -732,7 +734,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml index 94c306943a5..2eee7be83c6 100644 --- a/.github/workflows/daily-repo-chronicle.lock.yml +++ b/.github/workflows/daily-repo-chronicle.lock.yml @@ -161,6 +161,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -672,7 +674,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-output-integrator.lock.yml b/.github/workflows/daily-safe-output-integrator.lock.yml index 18d856a154c..70407c5ecc0 100644 --- a/.github/workflows/daily-safe-output-integrator.lock.yml +++ b/.github/workflows/daily-safe-output-integrator.lock.yml @@ -157,6 +157,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_de84013d0b3384a0_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -183,6 +184,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -614,7 +616,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-output-optimizer.lock.yml b/.github/workflows/daily-safe-output-optimizer.lock.yml index ac03105cd4e..b76f1533fae 100644 --- a/.github/workflows/daily-safe-output-optimizer.lock.yml +++ b/.github/workflows/daily-safe-output-optimizer.lock.yml @@ -174,6 +174,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -202,6 +203,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -735,7 +737,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-outputs-conformance.lock.yml b/.github/workflows/daily-safe-outputs-conformance.lock.yml index 3eb51a2ea9d..587d08d9052 100644 --- a/.github/workflows/daily-safe-outputs-conformance.lock.yml +++ b/.github/workflows/daily-safe-outputs-conformance.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: create_issue(max:10), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -613,7 +615,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-secrets-analysis.lock.yml b/.github/workflows/daily-secrets-analysis.lock.yml index 5efe61d44bb..6bdede23c29 100644 --- a/.github/workflows/daily-secrets-analysis.lock.yml +++ b/.github/workflows/daily-secrets-analysis.lock.yml @@ -154,6 +154,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -180,6 +181,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -602,7 +604,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-security-red-team.lock.yml b/.github/workflows/daily-security-red-team.lock.yml index c27dcb1ce8b..01f63afeb87 100644 --- a/.github/workflows/daily-security-red-team.lock.yml +++ b/.github/workflows/daily-security-red-team.lock.yml @@ -162,6 +162,7 @@ jobs: Tools: create_issue(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -617,7 +619,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-semgrep-scan.lock.yml b/.github/workflows/daily-semgrep-scan.lock.yml index 498799075dd..97ab174a8cd 100644 --- a/.github/workflows/daily-semgrep-scan.lock.yml +++ b/.github/workflows/daily-semgrep-scan.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: create_code_scanning_alert, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -640,7 +642,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-syntax-error-quality.lock.yml b/.github/workflows/daily-syntax-error-quality.lock.yml index 4f3e0980de0..a984e0b0d5e 100644 --- a/.github/workflows/daily-syntax-error-quality.lock.yml +++ b/.github/workflows/daily-syntax-error-quality.lock.yml @@ -153,6 +153,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -179,6 +180,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -618,7 +620,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-team-evolution-insights.lock.yml b/.github/workflows/daily-team-evolution-insights.lock.yml index c479c6345c5..ca6700e62b0 100644 --- a/.github/workflows/daily-team-evolution-insights.lock.yml +++ b/.github/workflows/daily-team-evolution-insights.lock.yml @@ -162,6 +162,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -610,7 +612,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-team-status.lock.yml b/.github/workflows/daily-team-status.lock.yml index a7474e8beae..a112788fb28 100644 --- a/.github/workflows/daily-team-status.lock.yml +++ b/.github/workflows/daily-team-status.lock.yml @@ -169,6 +169,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -622,7 +624,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-testify-uber-super-expert.lock.yml b/.github/workflows/daily-testify-uber-super-expert.lock.yml index 07e9d17f0d4..a4c987816e0 100644 --- a/.github/workflows/daily-testify-uber-super-expert.lock.yml +++ b/.github/workflows/daily-testify-uber-super-expert.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -706,7 +708,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index d13708d24ce..d1c26b1664d 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -153,6 +153,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ca1bb6eca19a6937_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -179,6 +180,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -607,7 +609,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dead-code-remover.lock.yml b/.github/workflows/dead-code-remover.lock.yml index 2c1be840c0e..f2f6afd11db 100644 --- a/.github/workflows/dead-code-remover.lock.yml +++ b/.github/workflows/dead-code-remover.lock.yml @@ -165,6 +165,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_bdef07df3fcaf856_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -659,7 +661,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/deep-report.lock.yml b/.github/workflows/deep-report.lock.yml index bc65132e9a8..0ee814992f6 100644 --- a/.github/workflows/deep-report.lock.yml +++ b/.github/workflows/deep-report.lock.yml @@ -175,6 +175,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -203,6 +204,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -811,7 +813,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/delight.lock.yml b/.github/workflows/delight.lock.yml index d422c60bbcb..7057bac3f07 100644 --- a/.github/workflows/delight.lock.yml +++ b/.github/workflows/delight.lock.yml @@ -158,6 +158,7 @@ jobs: Tools: create_issue(max:2), create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -184,6 +185,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -666,7 +668,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dependabot-burner.lock.yml b/.github/workflows/dependabot-burner.lock.yml index 6580cf0f8ab..5b82f84357b 100644 --- a/.github/workflows/dependabot-burner.lock.yml +++ b/.github/workflows/dependabot-burner.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -614,7 +616,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dependabot-go-checker.lock.yml b/.github/workflows/dependabot-go-checker.lock.yml index 6d1a39ffb23..3ec41899510 100644 --- a/.github/workflows/dependabot-go-checker.lock.yml +++ b/.github/workflows/dependabot-go-checker.lock.yml @@ -159,6 +159,7 @@ jobs: Tools: create_issue(max:10), close_issue(max:20), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -185,6 +186,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -632,7 +634,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dev-hawk.lock.yml b/.github/workflows/dev-hawk.lock.yml index 23d8b5c2da9..d2e8a8e60a5 100644 --- a/.github/workflows/dev-hawk.lock.yml +++ b/.github/workflows/dev-hawk.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -695,7 +697,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dev.lock.yml b/.github/workflows/dev.lock.yml index 85b29c91ec9..2605e6e47ee 100644 --- a/.github/workflows/dev.lock.yml +++ b/.github/workflows/dev.lock.yml @@ -217,6 +217,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -244,6 +245,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -742,7 +744,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index 7fe47df9631..cf18896bcad 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -175,6 +175,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_b38f5e32f9abeaa2_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -204,6 +205,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -835,7 +837,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index b34fca863df..ce1430d7e96 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -163,6 +163,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_af0c22aa486b1fca_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -692,7 +694,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/discussion-task-miner.lock.yml b/.github/workflows/discussion-task-miner.lock.yml index 8d27f478352..1f2b45b7677 100644 --- a/.github/workflows/discussion-task-miner.lock.yml +++ b/.github/workflows/discussion-task-miner.lock.yml @@ -158,6 +158,7 @@ jobs: Tools: add_comment(max:3), create_issue(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -184,6 +185,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -656,7 +658,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/docs-noob-tester.lock.yml b/.github/workflows/docs-noob-tester.lock.yml index 0ea534a47ac..ab6976903d8 100644 --- a/.github/workflows/docs-noob-tester.lock.yml +++ b/.github/workflows/docs-noob-tester.lock.yml @@ -160,6 +160,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -643,7 +645,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/draft-pr-cleanup.lock.yml b/.github/workflows/draft-pr-cleanup.lock.yml index 9d110e9cf21..cbb374a4a7e 100644 --- a/.github/workflows/draft-pr-cleanup.lock.yml +++ b/.github/workflows/draft-pr-cleanup.lock.yml @@ -149,6 +149,7 @@ jobs: Tools: add_comment(max:20), close_pull_request(max:10), add_labels(max:20), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -175,6 +176,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -625,7 +627,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/duplicate-code-detector.lock.yml b/.github/workflows/duplicate-code-detector.lock.yml index 58b5a08944d..f73fa39b5e5 100644 --- a/.github/workflows/duplicate-code-detector.lock.yml +++ b/.github/workflows/duplicate-code-detector.lock.yml @@ -168,6 +168,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -730,7 +732,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/example-permissions-warning.lock.yml b/.github/workflows/example-permissions-warning.lock.yml index 6ea1f88c554..d6cc054be0f 100644 --- a/.github/workflows/example-permissions-warning.lock.yml +++ b/.github/workflows/example-permissions-warning.lock.yml @@ -148,6 +148,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_5c3619dea31e9804_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -174,6 +175,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -411,7 +413,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/example-workflow-analyzer.lock.yml b/.github/workflows/example-workflow-analyzer.lock.yml index af5f37962a3..a362e55581f 100644 --- a/.github/workflows/example-workflow-analyzer.lock.yml +++ b/.github/workflows/example-workflow-analyzer.lock.yml @@ -166,6 +166,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -193,6 +194,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -685,7 +687,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/firewall-escape.lock.yml b/.github/workflows/firewall-escape.lock.yml index cf1f948e563..74c0ec2bac7 100644 --- a/.github/workflows/firewall-escape.lock.yml +++ b/.github/workflows/firewall-escape.lock.yml @@ -176,6 +176,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -203,6 +204,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -667,7 +669,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/firewall.lock.yml b/.github/workflows/firewall.lock.yml index 6da9652d2f2..46ddb261df3 100644 --- a/.github/workflows/firewall.lock.yml +++ b/.github/workflows/firewall.lock.yml @@ -148,6 +148,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_51f527cfa56efa24_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -174,6 +175,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -413,7 +415,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index 74f5e75e7df..3c7eb3fce34 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -163,6 +163,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_c168a14d0fc28a2f_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -189,6 +190,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -619,7 +621,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-mcp-structural-analysis.lock.yml b/.github/workflows/github-mcp-structural-analysis.lock.yml index 734dca2c233..f6839282afe 100644 --- a/.github/workflows/github-mcp-structural-analysis.lock.yml +++ b/.github/workflows/github-mcp-structural-analysis.lock.yml @@ -169,6 +169,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -681,7 +683,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index 88c86b467e9..9f98ab4256a 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -169,6 +169,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_1af95d393f4b398a_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -676,7 +678,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-remote-mcp-auth-test.lock.yml b/.github/workflows/github-remote-mcp-auth-test.lock.yml index 94293e28f7e..c6e6d3f67ba 100644 --- a/.github/workflows/github-remote-mcp-auth-test.lock.yml +++ b/.github/workflows/github-remote-mcp-auth-test.lock.yml @@ -161,6 +161,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -618,7 +620,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index fda74b797b3..31b8719137f 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -175,6 +175,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_6e15d7474d90bf3a_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -204,6 +205,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -822,7 +824,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-fan.lock.yml b/.github/workflows/go-fan.lock.yml index 9397165ebd3..e70bd99f3ba 100644 --- a/.github/workflows/go-fan.lock.yml +++ b/.github/workflows/go-fan.lock.yml @@ -168,6 +168,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -698,7 +700,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index 873db050507..519dac4827c 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -169,6 +169,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_6d6cb0d29893f634_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -802,7 +804,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-pattern-detector.lock.yml b/.github/workflows/go-pattern-detector.lock.yml index 6e45c44578a..e52b706a056 100644 --- a/.github/workflows/go-pattern-detector.lock.yml +++ b/.github/workflows/go-pattern-detector.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -638,7 +640,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/gpclean.lock.yml b/.github/workflows/gpclean.lock.yml index c10a07bdb70..423e53c75ee 100644 --- a/.github/workflows/gpclean.lock.yml +++ b/.github/workflows/gpclean.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -643,7 +645,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/grumpy-reviewer.lock.yml b/.github/workflows/grumpy-reviewer.lock.yml index 72e54442b7c..4fe25ed9993 100644 --- a/.github/workflows/grumpy-reviewer.lock.yml +++ b/.github/workflows/grumpy-reviewer.lock.yml @@ -215,6 +215,7 @@ jobs: Tools: create_pull_request_review_comment(max:5), submit_pull_request_review, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -242,6 +243,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -752,7 +754,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index 0a8f8f2ae9d..c2dc8a5e779 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -170,6 +170,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_73077ac1efa7ed06_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -671,7 +673,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index 48fa0f3799f..71eb7d748f4 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -164,6 +164,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_efd5c992561c134e_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -639,7 +641,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-arborist.lock.yml b/.github/workflows/issue-arborist.lock.yml index f565bec8251..d30c512ddd3 100644 --- a/.github/workflows/issue-arborist.lock.yml +++ b/.github/workflows/issue-arborist.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_issue(max:5), create_discussion, link_sub_issue(max:50), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -716,7 +718,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-monster.lock.yml b/.github/workflows/issue-monster.lock.yml index 70b9f470f76..21669aa895c 100644 --- a/.github/workflows/issue-monster.lock.yml +++ b/.github/workflows/issue-monster.lock.yml @@ -529,6 +529,7 @@ jobs: Tools: add_comment(max:3), assign_to_agent(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -555,6 +556,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1001,7 +1003,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-triage-agent.lock.yml b/.github/workflows/issue-triage-agent.lock.yml index 13b51381d50..f8059d98766 100644 --- a/.github/workflows/issue-triage-agent.lock.yml +++ b/.github/workflows/issue-triage-agent.lock.yml @@ -160,6 +160,7 @@ jobs: Tools: add_comment, add_labels, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -186,6 +187,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -601,7 +603,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index 1c1dbf92cbb..1808daf573e 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -168,6 +168,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_eac1fdf49c0156e5_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -717,7 +719,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index 3a4458093e1..924734161f9 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -163,6 +163,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f721fba8c5d6f4ce_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -189,6 +190,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -623,7 +625,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/lockfile-stats.lock.yml b/.github/workflows/lockfile-stats.lock.yml index e942578e5b2..8012584196a 100644 --- a/.github/workflows/lockfile-stats.lock.yml +++ b/.github/workflows/lockfile-stats.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -632,7 +634,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/mcp-inspector.lock.yml b/.github/workflows/mcp-inspector.lock.yml index 18015939f48..41078ffe8ba 100644 --- a/.github/workflows/mcp-inspector.lock.yml +++ b/.github/workflows/mcp-inspector.lock.yml @@ -200,6 +200,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop, notion_add_comment, post_to_slack_channel + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -242,6 +243,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1161,7 +1163,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 6dabc965be8..78fce35e3f4 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -199,6 +199,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_c0b73803c180c67c_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -225,6 +226,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -650,7 +652,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/metrics-collector.lock.yml b/.github/workflows/metrics-collector.lock.yml index 8e2482aaed4..ea1199bf0b1 100644 --- a/.github/workflows/metrics-collector.lock.yml +++ b/.github/workflows/metrics-collector.lock.yml @@ -159,6 +159,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/agentic_workflows_guide.md" cat "${RUNNER_TEMP}/gh-aw/prompts/repo_memory_prompt.md" cat << 'GH_AW_PROMPT_d850707bdb59dc40_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -186,6 +187,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -526,7 +528,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/notion-issue-summary.lock.yml b/.github/workflows/notion-issue-summary.lock.yml index db409b88095..11d11d74154 100644 --- a/.github/workflows/notion-issue-summary.lock.yml +++ b/.github/workflows/notion-issue-summary.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: missing_tool, missing_data, noop, notion_add_comment + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -620,7 +622,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/org-health-report.lock.yml b/.github/workflows/org-health-report.lock.yml index 0f14ad0d743..c19dd0d64bd 100644 --- a/.github/workflows/org-health-report.lock.yml +++ b/.github/workflows/org-health-report.lock.yml @@ -169,6 +169,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -681,7 +683,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pdf-summary.lock.yml b/.github/workflows/pdf-summary.lock.yml index 2dde718d3c7..2e7ad9aa129 100644 --- a/.github/workflows/pdf-summary.lock.yml +++ b/.github/workflows/pdf-summary.lock.yml @@ -228,6 +228,7 @@ jobs: Tools: add_comment, create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -256,6 +257,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -750,7 +752,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/plan.lock.yml b/.github/workflows/plan.lock.yml index b30e0924f4f..367a87ad0c7 100644 --- a/.github/workflows/plan.lock.yml +++ b/.github/workflows/plan.lock.yml @@ -200,6 +200,7 @@ jobs: Tools: create_issue(max:5), close_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -226,6 +227,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -690,7 +692,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index 607af8a96cd..c4111066d31 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -226,6 +226,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -253,6 +254,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1000,7 +1002,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/portfolio-analyst.lock.yml b/.github/workflows/portfolio-analyst.lock.yml index 5795160795a..8d19a71b3be 100644 --- a/.github/workflows/portfolio-analyst.lock.yml +++ b/.github/workflows/portfolio-analyst.lock.yml @@ -173,6 +173,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -201,6 +202,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -774,7 +776,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pr-nitpick-reviewer.lock.yml b/.github/workflows/pr-nitpick-reviewer.lock.yml index 717815c7d5c..a9473df46d9 100644 --- a/.github/workflows/pr-nitpick-reviewer.lock.yml +++ b/.github/workflows/pr-nitpick-reviewer.lock.yml @@ -209,6 +209,7 @@ jobs: Tools: create_discussion, create_pull_request_review_comment(max:10), submit_pull_request_review, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -236,6 +237,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -746,7 +748,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pr-triage-agent.lock.yml b/.github/workflows/pr-triage-agent.lock.yml index df20887afb9..be04bb9d4e2 100644 --- a/.github/workflows/pr-triage-agent.lock.yml +++ b/.github/workflows/pr-triage-agent.lock.yml @@ -162,6 +162,7 @@ jobs: Tools: add_comment(max:50), create_issue, add_labels(max:100), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -675,7 +677,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/prompt-clustering-analysis.lock.yml b/.github/workflows/prompt-clustering-analysis.lock.yml index 78248eb10fa..09e7cfcdea4 100644 --- a/.github/workflows/prompt-clustering-analysis.lock.yml +++ b/.github/workflows/prompt-clustering-analysis.lock.yml @@ -177,6 +177,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -205,6 +206,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -777,7 +779,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/python-data-charts.lock.yml b/.github/workflows/python-data-charts.lock.yml index 96450c61ddf..1c538b0421f 100644 --- a/.github/workflows/python-data-charts.lock.yml +++ b/.github/workflows/python-data-charts.lock.yml @@ -169,6 +169,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -197,6 +198,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -753,7 +755,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index 0c0091603ab..e84f44df5eb 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -240,6 +240,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_a0c3414a8d08f8d7_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -269,6 +270,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -910,7 +912,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index cd977a10ce7..89cb2d6faa2 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -189,6 +189,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_5537490e8c05e0e7_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -215,6 +216,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -667,7 +669,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml index 48c028eba1a..e909b077f1b 100644 --- a/.github/workflows/release.lock.yml +++ b/.github/workflows/release.lock.yml @@ -177,6 +177,7 @@ jobs: Tools: update_release, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -203,6 +204,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -637,7 +639,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml index be1f9372ef9..6e266c3e270 100644 --- a/.github/workflows/repo-audit-analyzer.lock.yml +++ b/.github/workflows/repo-audit-analyzer.lock.yml @@ -167,6 +167,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -194,6 +195,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -636,7 +638,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repo-tree-map.lock.yml b/.github/workflows/repo-tree-map.lock.yml index 4a14eb18074..e489884a398 100644 --- a/.github/workflows/repo-tree-map.lock.yml +++ b/.github/workflows/repo-tree-map.lock.yml @@ -160,6 +160,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -186,6 +187,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -604,7 +606,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repository-quality-improver.lock.yml b/.github/workflows/repository-quality-improver.lock.yml index 05cefc84856..e61db6592c4 100644 --- a/.github/workflows/repository-quality-improver.lock.yml +++ b/.github/workflows/repository-quality-improver.lock.yml @@ -166,6 +166,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -194,6 +195,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -698,7 +700,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/research.lock.yml b/.github/workflows/research.lock.yml index 4e56d302e9d..aee35f4b7be 100644 --- a/.github/workflows/research.lock.yml +++ b/.github/workflows/research.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -634,7 +636,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/safe-output-health.lock.yml b/.github/workflows/safe-output-health.lock.yml index fc30f11f921..5b7dbf4a4bf 100644 --- a/.github/workflows/safe-output-health.lock.yml +++ b/.github/workflows/safe-output-health.lock.yml @@ -171,6 +171,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -199,6 +200,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -722,7 +724,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/schema-consistency-checker.lock.yml b/.github/workflows/schema-consistency-checker.lock.yml index 57ce3f097d5..b3d301f0bbf 100644 --- a/.github/workflows/schema-consistency-checker.lock.yml +++ b/.github/workflows/schema-consistency-checker.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -632,7 +634,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/schema-feature-coverage.lock.yml b/.github/workflows/schema-feature-coverage.lock.yml index e872aea6b80..3e13728152e 100644 --- a/.github/workflows/schema-feature-coverage.lock.yml +++ b/.github/workflows/schema-feature-coverage.lock.yml @@ -164,6 +164,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_98b78c552e118305_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -653,7 +655,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/scout.lock.yml b/.github/workflows/scout.lock.yml index cace7b354dc..e95e9834ae6 100644 --- a/.github/workflows/scout.lock.yml +++ b/.github/workflows/scout.lock.yml @@ -259,6 +259,7 @@ jobs: Tools: add_comment, add_labels, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -291,6 +292,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -848,7 +850,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/security-compliance.lock.yml b/.github/workflows/security-compliance.lock.yml index 86679b60a33..47a7097576f 100644 --- a/.github/workflows/security-compliance.lock.yml +++ b/.github/workflows/security-compliance.lock.yml @@ -169,6 +169,7 @@ jobs: Tools: create_issue(max:100), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -648,7 +650,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/security-review.lock.yml b/.github/workflows/security-review.lock.yml index 01405cc96f3..66c1f292263 100644 --- a/.github/workflows/security-review.lock.yml +++ b/.github/workflows/security-review.lock.yml @@ -212,6 +212,7 @@ jobs: Tools: create_pull_request_review_comment(max:10), submit_pull_request_review, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -240,6 +241,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -798,7 +800,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/semantic-function-refactor.lock.yml b/.github/workflows/semantic-function-refactor.lock.yml index 598a1b3a167..a9d1ac08d46 100644 --- a/.github/workflows/semantic-function-refactor.lock.yml +++ b/.github/workflows/semantic-function-refactor.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: create_issue, close_issue(max:10), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -696,7 +698,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/sergo.lock.yml b/.github/workflows/sergo.lock.yml index 272a6a002be..28684290d26 100644 --- a/.github/workflows/sergo.lock.yml +++ b/.github/workflows/sergo.lock.yml @@ -167,6 +167,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -195,6 +196,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -696,7 +698,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index f92b8a09fd2..24f26440184 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -178,6 +178,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_00fdac09910f5004_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -206,6 +207,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -692,7 +694,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-all-merged.lock.yml b/.github/workflows/smoke-agent-all-merged.lock.yml index 44122c51ab0..3b29da15aa2 100644 --- a/.github/workflows/smoke-agent-all-merged.lock.yml +++ b/.github/workflows/smoke-agent-all-merged.lock.yml @@ -195,6 +195,7 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -221,6 +222,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -659,7 +661,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-all-none.lock.yml b/.github/workflows/smoke-agent-all-none.lock.yml index 5124120c1b2..62723e057e7 100644 --- a/.github/workflows/smoke-agent-all-none.lock.yml +++ b/.github/workflows/smoke-agent-all-none.lock.yml @@ -195,6 +195,7 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -221,6 +222,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -659,7 +661,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-public-approved.lock.yml b/.github/workflows/smoke-agent-public-approved.lock.yml index 9966220d532..177f3c8dbed 100644 --- a/.github/workflows/smoke-agent-public-approved.lock.yml +++ b/.github/workflows/smoke-agent-public-approved.lock.yml @@ -200,6 +200,7 @@ jobs: Tools: add_comment(max:2), assign_to_agent, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -226,6 +227,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -692,7 +694,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-public-none.lock.yml b/.github/workflows/smoke-agent-public-none.lock.yml index 45636c44e88..57ef283a1fe 100644 --- a/.github/workflows/smoke-agent-public-none.lock.yml +++ b/.github/workflows/smoke-agent-public-none.lock.yml @@ -195,6 +195,7 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -221,6 +222,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -659,7 +661,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-scoped-approved.lock.yml b/.github/workflows/smoke-agent-scoped-approved.lock.yml index a1339eca175..caf4c46a90e 100644 --- a/.github/workflows/smoke-agent-scoped-approved.lock.yml +++ b/.github/workflows/smoke-agent-scoped-approved.lock.yml @@ -199,6 +199,7 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -225,6 +226,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -669,7 +671,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-call-workflow.lock.yml b/.github/workflows/smoke-call-workflow.lock.yml index 6338d3d6ae8..6a53d318277 100644 --- a/.github/workflows/smoke-call-workflow.lock.yml +++ b/.github/workflows/smoke-call-workflow.lock.yml @@ -178,6 +178,7 @@ jobs: Tools: call_workflow, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -204,6 +205,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -643,7 +645,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index 12b402184f0..c7c0518bdf1 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -239,6 +239,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_4ec99b0fd270d235_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -270,6 +271,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -2102,7 +2104,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-codex.lock.yml b/.github/workflows/smoke-codex.lock.yml index bcf466f117a..bbad49814b3 100644 --- a/.github/workflows/smoke-codex.lock.yml +++ b/.github/workflows/smoke-codex.lock.yml @@ -227,6 +227,7 @@ jobs: Tools: add_comment(max:2), create_issue, add_labels, remove_labels, unassign_from_user, hide_comment(max:5), missing_tool, missing_data, noop, add_smoked_label + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -257,6 +258,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1210,7 +1212,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-copilot-arm.lock.yml b/.github/workflows/smoke-copilot-arm.lock.yml index a4861a7626d..66e1069302d 100644 --- a/.github/workflows/smoke-copilot-arm.lock.yml +++ b/.github/workflows/smoke-copilot-arm.lock.yml @@ -222,6 +222,7 @@ jobs: Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -252,6 +253,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1563,7 +1565,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 209c29b902e..58692bfd8ae 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -229,6 +229,7 @@ jobs: Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, reply_to_pull_request_review_comment(max:5), add_labels, remove_labels, set_issue_type, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -259,6 +260,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -1613,7 +1615,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-create-cross-repo-pr.lock.yml b/.github/workflows/smoke-create-cross-repo-pr.lock.yml index 1d1bdd050e0..4752359ec66 100644 --- a/.github/workflows/smoke-create-cross-repo-pr.lock.yml +++ b/.github/workflows/smoke-create-cross-repo-pr.lock.yml @@ -193,6 +193,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_b5851c5feae065c1_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -219,6 +220,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -714,7 +716,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-gemini.lock.yml b/.github/workflows/smoke-gemini.lock.yml index 5a59411a9dc..10490b0e2a8 100644 --- a/.github/workflows/smoke-gemini.lock.yml +++ b/.github/workflows/smoke-gemini.lock.yml @@ -217,6 +217,7 @@ jobs: Tools: add_comment(max:2), create_issue, add_labels, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -244,6 +245,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -854,7 +856,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index 8d13443234a..142af52f9f4 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -211,6 +211,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_8176b7650e805e07_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -237,6 +238,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -683,7 +685,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index 7f1207aacc7..1f29d5f2e9c 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -210,6 +210,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ba7946ed4c54c799_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -236,6 +237,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -841,7 +843,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-service-ports.lock.yml b/.github/workflows/smoke-service-ports.lock.yml index 1b2f9da0f58..77ec6ca8acb 100644 --- a/.github/workflows/smoke-service-ports.lock.yml +++ b/.github/workflows/smoke-service-ports.lock.yml @@ -174,6 +174,7 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -200,6 +201,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -617,7 +619,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-temporary-id.lock.yml b/.github/workflows/smoke-temporary-id.lock.yml index de63a414959..de91eae73fd 100644 --- a/.github/workflows/smoke-temporary-id.lock.yml +++ b/.github/workflows/smoke-temporary-id.lock.yml @@ -205,6 +205,7 @@ jobs: Tools: add_comment(max:2), create_issue(max:5), link_sub_issue(max:3), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -231,6 +232,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -693,7 +695,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-test-tools.lock.yml b/.github/workflows/smoke-test-tools.lock.yml index 4f10317f8cf..e8e2401ce86 100644 --- a/.github/workflows/smoke-test-tools.lock.yml +++ b/.github/workflows/smoke-test-tools.lock.yml @@ -199,6 +199,7 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -225,6 +226,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -659,7 +661,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-update-cross-repo-pr.lock.yml b/.github/workflows/smoke-update-cross-repo-pr.lock.yml index 237d4dd0812..6fd188f48d6 100644 --- a/.github/workflows/smoke-update-cross-repo-pr.lock.yml +++ b/.github/workflows/smoke-update-cross-repo-pr.lock.yml @@ -196,6 +196,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_6b3177d37c27b8e8_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -223,6 +224,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -729,7 +731,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-workflow-call-with-inputs.lock.yml b/.github/workflows/smoke-workflow-call-with-inputs.lock.yml index 437648d7ab2..57aa24b7a2d 100644 --- a/.github/workflows/smoke-workflow-call-with-inputs.lock.yml +++ b/.github/workflows/smoke-workflow-call-with-inputs.lock.yml @@ -205,6 +205,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_auto_create_issue.md" cat << 'GH_AW_PROMPT_35a5dccbd8d9d9f9_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -231,6 +232,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -659,7 +661,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-workflow-call.lock.yml b/.github/workflows/smoke-workflow-call.lock.yml index 850d60ad785..1f387833183 100644 --- a/.github/workflows/smoke-workflow-call.lock.yml +++ b/.github/workflows/smoke-workflow-call.lock.yml @@ -205,6 +205,7 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -231,6 +232,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -643,7 +645,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index b60e813c4d2..8797fffdf8d 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -179,6 +179,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -206,6 +207,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -751,7 +753,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/static-analysis-report.lock.yml b/.github/workflows/static-analysis-report.lock.yml index 832dcf69907..18d4cbd14e3 100644 --- a/.github/workflows/static-analysis-report.lock.yml +++ b/.github/workflows/static-analysis-report.lock.yml @@ -168,6 +168,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -196,6 +197,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -727,7 +729,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/step-name-alignment.lock.yml b/.github/workflows/step-name-alignment.lock.yml index aa6d9390f0a..042d2889948 100644 --- a/.github/workflows/step-name-alignment.lock.yml +++ b/.github/workflows/step-name-alignment.lock.yml @@ -160,6 +160,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -187,6 +188,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -632,7 +634,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/sub-issue-closer.lock.yml b/.github/workflows/sub-issue-closer.lock.yml index e7c4f54ebe1..5c5667e1adc 100644 --- a/.github/workflows/sub-issue-closer.lock.yml +++ b/.github/workflows/sub-issue-closer.lock.yml @@ -156,6 +156,7 @@ jobs: Tools: add_comment(max:20), update_issue(max:20), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -182,6 +183,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -646,7 +648,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/super-linter.lock.yml b/.github/workflows/super-linter.lock.yml index b29a85898e8..6c5053efd29 100644 --- a/.github/workflows/super-linter.lock.yml +++ b/.github/workflows/super-linter.lock.yml @@ -165,6 +165,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -192,6 +193,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -653,7 +655,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index b75916d98d7..ef7a2faf2ce 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -177,6 +177,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -205,6 +206,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -811,7 +813,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/terminal-stylist.lock.yml b/.github/workflows/terminal-stylist.lock.yml index bd5e264574c..0f6fb8ae993 100644 --- a/.github/workflows/terminal-stylist.lock.yml +++ b/.github/workflows/terminal-stylist.lock.yml @@ -163,6 +163,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -669,7 +671,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index 2acfada59eb..7e678531cb0 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -161,6 +161,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_fd59cc5c2d1fc082_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -634,7 +636,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-dispatcher.lock.yml b/.github/workflows/test-dispatcher.lock.yml index d50af6f1cc4..e84d9a5f4d8 100644 --- a/.github/workflows/test-dispatcher.lock.yml +++ b/.github/workflows/test-dispatcher.lock.yml @@ -152,6 +152,7 @@ jobs: Tools: dispatch_workflow, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -178,6 +179,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -588,7 +590,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-project-url-default.lock.yml b/.github/workflows/test-project-url-default.lock.yml index 14fb1cb27c5..d1e858fb0bd 100644 --- a/.github/workflows/test-project-url-default.lock.yml +++ b/.github/workflows/test-project-url-default.lock.yml @@ -153,6 +153,7 @@ jobs: Tools: update_project(max:5), create_project_status_update, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -179,6 +180,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -649,7 +651,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-workflow.lock.yml b/.github/workflows/test-workflow.lock.yml index c3b8c6935bb..7d30c187701 100644 --- a/.github/workflows/test-workflow.lock.yml +++ b/.github/workflows/test-workflow.lock.yml @@ -151,6 +151,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_d2100dd9504f0ecb_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -177,6 +178,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -412,7 +414,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index e22f0984ef9..1ebf43d2a43 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -220,6 +220,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_d35e31e70bc8be49_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -246,6 +247,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -717,7 +719,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/typist.lock.yml b/.github/workflows/typist.lock.yml index abdf84bc452..c82888410ff 100644 --- a/.github/workflows/typist.lock.yml +++ b/.github/workflows/typist.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -669,7 +671,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index 524e1269a51..6f5e6658ece 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -167,6 +167,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_37168e83c534310c_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -193,6 +194,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -625,7 +627,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index 80f28f21932..6ac96f85fab 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -223,6 +223,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -252,6 +253,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -855,7 +857,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/update-astro.lock.yml b/.github/workflows/update-astro.lock.yml index d69cc0de81b..09b6813c714 100644 --- a/.github/workflows/update-astro.lock.yml +++ b/.github/workflows/update-astro.lock.yml @@ -168,6 +168,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_60089bbd806a2741_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -194,6 +195,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -633,7 +635,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/video-analyzer.lock.yml b/.github/workflows/video-analyzer.lock.yml index 5670513d71b..0ebd25cdfa8 100644 --- a/.github/workflows/video-analyzer.lock.yml +++ b/.github/workflows/video-analyzer.lock.yml @@ -162,6 +162,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -188,6 +189,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -624,7 +626,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-blog-post-writer.lock.yml b/.github/workflows/weekly-blog-post-writer.lock.yml index a34c10b5c01..8616a341465 100644 --- a/.github/workflows/weekly-blog-post-writer.lock.yml +++ b/.github/workflows/weekly-blog-post-writer.lock.yml @@ -176,6 +176,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_37ff4ed646105a15_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -204,6 +205,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -807,7 +809,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index a75cc8c07ee..1433d536ace 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -163,6 +163,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -646,7 +648,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-issue-summary.lock.yml b/.github/workflows/weekly-issue-summary.lock.yml index df70e658c0c..9dd22e51851 100644 --- a/.github/workflows/weekly-issue-summary.lock.yml +++ b/.github/workflows/weekly-issue-summary.lock.yml @@ -170,6 +170,7 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -197,6 +198,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -663,7 +665,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index 965993d25d6..63fe22a2d90 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -164,6 +164,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_dd5ce0f0ce7b0ccb_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -616,7 +618,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-generator.lock.yml b/.github/workflows/workflow-generator.lock.yml index c4de0cb5681..eb03c71a72e 100644 --- a/.github/workflows/workflow-generator.lock.yml +++ b/.github/workflows/workflow-generator.lock.yml @@ -196,6 +196,7 @@ jobs: Tools: update_issue, assign_to_agent, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -222,6 +223,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -693,7 +695,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index 87b286bc0b3..ca3198a267d 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: add_comment(max:15), create_issue(max:10), update_issue(max:5), missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -190,6 +191,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -714,7 +716,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-normalizer.lock.yml b/.github/workflows/workflow-normalizer.lock.yml index e54b186b833..85a526a9cda 100644 --- a/.github/workflows/workflow-normalizer.lock.yml +++ b/.github/workflows/workflow-normalizer.lock.yml @@ -164,6 +164,7 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -191,6 +192,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -692,7 +694,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-skill-extractor.lock.yml b/.github/workflows/workflow-skill-extractor.lock.yml index 4cca97e527b..a39520a1004 100644 --- a/.github/workflows/workflow-skill-extractor.lock.yml +++ b/.github/workflows/workflow-skill-extractor.lock.yml @@ -160,6 +160,7 @@ jobs: Tools: create_issue(max:3), create_discussion, missing_tool, missing_data, noop + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -186,6 +187,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -639,7 +641,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs new file mode 100644 index 00000000000..d4c84da7d2c --- /dev/null +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -0,0 +1,419 @@ +// @ts-check +/// + +/** + * mount_mcp_as_cli.cjs + * + * Mounts MCP servers as local CLI tools by reading the manifest written by + * start_mcp_gateway.sh, querying each server for its tool list, and generating + * a standalone bash wrapper script per server in /tmp/gh-aw/mcp-cli/bin/. + * + * The bin directory is locked (chmod 555) so the agent cannot modify or inject + * scripts. The directory is added to PATH via core.addPath(). + * + * Generated CLI wrapper usage: + * --help Show all available commands + * --help Show help for a specific command + * [--param value ...] Execute a command + */ + +const fs = require("fs"); +const http = require("http"); +const path = require("path"); + +const MANIFEST_FILE = "/tmp/gh-aw/mcp-cli/manifest.json"; +const CLI_BIN_DIR = "/tmp/gh-aw/mcp-cli/bin"; +const TOOLS_DIR = "/tmp/gh-aw/mcp-cli/tools"; + +/** MCP servers that are internal infrastructure and should not be user-facing CLIs */ +const INTERNAL_SERVERS = new Set(["safeoutputs", "mcp-scripts"]); + +/** + * Make an HTTP POST request with a JSON body and return the parsed response. + * + * @param {string} urlStr - Full URL to POST to + * @param {Record} headers - Request headers + * @param {unknown} body - Request body (will be JSON-serialized) + * @param {number} [timeoutMs=15000] - Request timeout in milliseconds + * @returns {Promise<{statusCode: number, body: unknown, headers: Record}>} + */ +function httpPostJSON(urlStr, headers, body, timeoutMs = 15000) { + return new Promise((resolve, reject) => { + const parsedUrl = new URL(urlStr); + const bodyStr = JSON.stringify(body); + + const options = { + hostname: parsedUrl.hostname, + port: parsedUrl.port || 80, + path: parsedUrl.pathname + parsedUrl.search, + method: "POST", + headers: { + "Content-Type": "application/json", + "Content-Length": Buffer.byteLength(bodyStr), + ...headers, + }, + }; + + const req = http.request(options, res => { + let data = ""; + res.on("data", chunk => { + data += chunk; + }); + res.on("end", () => { + let parsed; + try { + parsed = JSON.parse(data); + } catch { + parsed = data; + } + resolve({ + statusCode: res.statusCode || 0, + body: parsed, + headers: /** @type {Record} */ res.headers, + }); + }); + }); + + req.on("error", err => { + reject(err); + }); + + req.setTimeout(timeoutMs, () => { + req.destroy(); + reject(new Error(`HTTP request timed out after ${timeoutMs}ms`)); + }); + + req.write(bodyStr); + req.end(); + }); +} + +/** + * Query the tools list from an MCP server via JSON-RPC. + * Follows the standard MCP handshake: initialize → tools/list. + * + * @param {string} serverUrl - HTTP URL of the MCP server endpoint + * @param {string} apiKey - Bearer token for gateway authentication + * @param {typeof import("@actions/core")} core - GitHub Actions core + * @returns {Promise>} + */ +async function fetchMCPTools(serverUrl, apiKey, core) { + const authHeaders = { Authorization: apiKey }; + + // Step 1: initialize – establish the session and capture Mcp-Session-Id if present + let sessionHeader = {}; + try { + const initResp = await httpPostJSON( + serverUrl, + authHeaders, + { + jsonrpc: "2.0", + id: 1, + method: "initialize", + params: { + capabilities: {}, + clientInfo: { name: "mcp-cli-mount", version: "1.0.0" }, + protocolVersion: "2024-11-05", + }, + }, + 15000 + ); + const sessionId = initResp.headers["mcp-session-id"]; + if (sessionId && typeof sessionId === "string") { + sessionHeader = { "Mcp-Session-Id": sessionId }; + } + } catch (err) { + core.warning(` initialize failed for ${serverUrl}: ${err instanceof Error ? err.message : String(err)}`); + return []; + } + + // Step 2: tools/list – get the available tool definitions + try { + const listResp = await httpPostJSON(serverUrl, { ...authHeaders, ...sessionHeader }, { jsonrpc: "2.0", id: 2, method: "tools/list" }, 15000); + const respBody = /** @type {Record} */ listResp.body; + if (respBody && respBody.result && typeof respBody.result === "object") { + const result = /** @type {Record} */ respBody.result; + if (Array.isArray(result.tools)) { + return /** @type {Array<{name: string, description?: string, inputSchema?: unknown}>} */ result.tools; + } + } + return []; + } catch (err) { + core.warning(` tools/list failed for ${serverUrl}: ${err instanceof Error ? err.message : String(err)}`); + return []; + } +} + +/** + * Generate the bash wrapper script content for a given MCP server. + * The generated script is a self-contained CLI that delegates all calls + * to the MCP gateway via curl. + * + * @param {string} serverName - Name of the MCP server + * @param {string} serverUrl - HTTP URL of the MCP server endpoint + * @param {string} toolsFile - Path to the cached tools JSON file + * @returns {string} Content of the bash wrapper script + */ +function generateCLIWrapperScript(serverName, serverUrl, toolsFile) { + // We use a template literal but avoid single quotes in the embedded bash + // to keep the heredoc-free approach clean. The API key is read at runtime + // from the MCP_GATEWAY_API_KEY environment variable. + return `#!/usr/bin/env bash +# MCP CLI wrapper for: ${serverName} +# Auto-generated by gh-aw. Do not modify. +# +# Usage: +# ${serverName} --help Show all available commands +# ${serverName} --help Show help for a specific command +# ${serverName} [--param value...] Execute a command + +SERVER_NAME="${serverName}" +SERVER_URL="${serverUrl}" +TOOLS_FILE="${toolsFile}" + +API_KEY="\${MCP_GATEWAY_API_KEY:-}" +if [ -z "\$API_KEY" ]; then + echo "Error: MCP_GATEWAY_API_KEY environment variable is not set" >&2 + exit 1 +fi + +load_tools() { + if [ -f "\$TOOLS_FILE" ]; then + cat "\$TOOLS_FILE" + else + echo "[]" + fi +} + +show_help() { + local tools + tools=\$(load_tools) + echo "Usage: \$SERVER_NAME [options]" + echo "" + echo "Available commands:" + if command -v jq &>/dev/null && echo "\$tools" | jq -e "length > 0" >/dev/null 2>&1; then + echo "\$tools" | jq -r ".[] | \\" \(.name)\\t\(.description // \\"No description\\")\\"" \\ + | column -t -s $'\\t' 2>/dev/null \\ + || echo "\$tools" | jq -r ".[] | \\" \(.name) \(.description // \\"\\")\\"" + else + echo " (tool list unavailable)" + fi + echo "" + echo "Run '\$SERVER_NAME --help' for more information on a command." +} + +show_tool_help() { + local tool_name="\$1" + local tools tool + tools=\$(load_tools) + tool=\$(echo "\$tools" | jq -r ".[] | select(.name == \\"\$tool_name\\")" 2>/dev/null || echo "") + + if [ -z "\$tool" ]; then + echo "Error: Unknown command '"\$tool_name"'" >&2 + echo "Run '"\$SERVER_NAME" --help' to see available commands." >&2 + exit 1 + fi + + echo "Command: \$tool_name" + echo "Description: \$(echo "\$tool" | jq -r ".description // \\"No description\\"")" + + local has_props + has_props=\$(echo "\$tool" | jq -r "has(\\"inputSchema\\") and ((.inputSchema.properties // {}) | length > 0)") + + if [ "\$has_props" = "true" ]; then + echo "" + echo "Options:" + echo "\$tool" | jq -r ".inputSchema.properties | to_entries[] | \\" --\(.key) \(.value.description // .value.type // \\"string\\")\\"" + local required + required=\$(echo "\$tool" | jq -r "(.inputSchema.required // []) | join(\\", \\")") + if [ -n "\$required" ]; then + echo "" + echo "Required: \$required" + fi + fi +} + +call_tool() { + local tool_name="\$1" + shift + + local args="{}" + while [[ \$# -gt 0 ]]; do + if [[ "\$1" == --* ]]; then + local key="\${1#--}" + if [[ \$# -ge 2 && "\$2" != --* ]]; then + local val="\$2" + args=\$(echo "\$args" | jq --arg k "\$key" --arg v "\$val" ". + {(\$k): \$v}") + shift 2 + else + args=\$(echo "\$args" | jq --arg k "\$key" ". + {(\$k): true}") + shift 1 + fi + else + shift + fi + done + + local init_resp session_id session_header_args + init_resp=\$(curl -s -i --max-time 30 -X POST "\$SERVER_URL" \\ + -H "Authorization: \$API_KEY" \\ + -H "Content-Type: application/json" \\ + -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"mcp-cli","version":"1.0.0"},"protocolVersion":"2024-11-05"}}' \\ + 2>/dev/null || echo "") + + session_id=\$(echo "\$init_resp" | grep -i "^mcp-session-id:" | awk "{print \$2}" | tr -d "\\r" 2>/dev/null || echo "") + + session_header_args=() + if [ -n "\$session_id" ]; then + session_header_args=(-H "Mcp-Session-Id: \$session_id") + fi + + local request + request=\$(jq -n --arg name "\$tool_name" --argjson args "\$args" \\ + "{\\"jsonrpc\\":\\"2.0\\",\\"id\\":2,\\"method\\":\\"tools/call\\",\\"params\\":{\\"name\\":\$name,\\"arguments\\":\$args}}") + + local response + response=\$(curl -s --max-time 120 -X POST "\$SERVER_URL" \\ + -H "Authorization: \$API_KEY" \\ + -H "Content-Type: application/json" \\ + "\${session_header_args[@]}" \\ + -d "\$request" \\ + 2>/dev/null) + + if echo "\$response" | jq -e ".error" >/dev/null 2>&1; then + local err_msg err_code + err_msg=\$(echo "\$response" | jq -r ".error.message // \\"Unknown error\\"") + err_code=\$(echo "\$response" | jq -r ".error.code // \\"\\"" ) + if [ -n "\$err_code" ]; then + echo "Error [\$err_code]: \$err_msg" >&2 + else + echo "Error: \$err_msg" >&2 + fi + exit 1 + fi + + if echo "\$response" | jq -e ".result.content" >/dev/null 2>&1; then + echo "\$response" | jq -r ".result.content[] | + if .type == \\"text\\" then .text + elif .type == \\"image\\" then \\"[image data - \(.mimeType // \\"unknown\\")]\\"" + else (. | tostring) + end" + elif echo "\$response" | jq -e ".result" >/dev/null 2>&1; then + echo "\$response" | jq -r ".result" + else + echo "\$response" + fi +} + +if [[ \$# -eq 0 || "\$1" == "--help" || "\$1" == "-h" ]]; then + show_help + exit 0 +fi + +COMMAND="\$1" +shift + +if [[ "\$1" == "--help" || "\$1" == "-h" ]]; then + show_tool_help "\$COMMAND" + exit 0 +fi + +call_tool "\$COMMAND" "\$@" +`; +} + +/** + * Mount MCP servers as CLI tools by reading the manifest and generating wrapper scripts. + * + * @returns {Promise} + */ +async function main() { + const core = global.core; + + core.info("Mounting MCP servers as CLI tools..."); + + if (!fs.existsSync(MANIFEST_FILE)) { + core.info("No MCP CLI manifest found, skipping CLI mounting"); + return; + } + + /** @type {{servers: Array<{name: string, url: string}>}} */ + let manifest; + try { + manifest = JSON.parse(fs.readFileSync(MANIFEST_FILE, "utf8")); + } catch (err) { + core.warning(`Failed to read MCP CLI manifest: ${err instanceof Error ? err.message : String(err)}`); + return; + } + + const servers = (manifest.servers || []).filter(s => !INTERNAL_SERVERS.has(s.name)); + + if (servers.length === 0) { + core.info("No user-facing MCP servers in manifest, skipping CLI mounting"); + return; + } + + fs.mkdirSync(CLI_BIN_DIR, { recursive: true }); + fs.mkdirSync(TOOLS_DIR, { recursive: true }); + + const apiKey = process.env.MCP_GATEWAY_API_KEY || ""; + if (!apiKey) { + core.warning("MCP_GATEWAY_API_KEY is not set; generated CLI wrappers will fail at runtime"); + } + + const mountedServers = []; + + for (const server of servers) { + const { name, url } = server; + core.info(`Mounting MCP server '${name}' (url: ${url})...`); + + const toolsFile = path.join(TOOLS_DIR, `${name}.json`); + + // Query tools from the server + const tools = await fetchMCPTools(url, apiKey, core); + core.info(` Found ${tools.length} tool(s)`); + + // Cache the tool list + try { + fs.writeFileSync(toolsFile, JSON.stringify(tools, null, 2), { mode: 0o644 }); + } catch (err) { + core.warning(` Failed to write tools cache for ${name}: ${err instanceof Error ? err.message : String(err)}`); + } + + // Write the CLI wrapper script + const scriptPath = path.join(CLI_BIN_DIR, name); + try { + fs.writeFileSync(scriptPath, generateCLIWrapperScript(name, url, toolsFile), { mode: 0o755 }); + mountedServers.push(name); + core.info(` ✓ Mounted as: ${scriptPath}`); + } catch (err) { + core.warning(` Failed to write CLI wrapper for ${name}: ${err instanceof Error ? err.message : String(err)}`); + } + } + + if (mountedServers.length === 0) { + core.info("No MCP servers were successfully mounted as CLI tools"); + return; + } + + // Lock the bin directory so the agent cannot modify or inject scripts + try { + fs.chmodSync(CLI_BIN_DIR, 0o555); + core.info(`CLI bin directory locked (read-only): ${CLI_BIN_DIR}`); + } catch (err) { + core.warning(`Failed to lock CLI bin directory: ${err instanceof Error ? err.message : String(err)}`); + } + + // Add the bin directory to PATH for subsequent steps + core.addPath(CLI_BIN_DIR); + + core.info(""); + core.info(`Successfully mounted ${mountedServers.length} MCP server(s) as CLI tools:`); + for (const name of mountedServers) { + core.info(` - ${name}`); + } + core.info(`CLI bin directory added to PATH: ${CLI_BIN_DIR}`); + core.setOutput("mounted-servers", mountedServers.join(",")); +} + +module.exports = { main, fetchMCPTools, generateCLIWrapperScript }; diff --git a/actions/setup/sh/mount_mcp_as_cli.sh b/actions/setup/sh/mount_mcp_as_cli.sh deleted file mode 100755 index 38e42d5c6e7..00000000000 --- a/actions/setup/sh/mount_mcp_as_cli.sh +++ /dev/null @@ -1,309 +0,0 @@ -#!/usr/bin/env bash -# mount_mcp_as_cli.sh -# -# Mounts MCP servers as local CLI tools, allowing agents to call MCP tools -# directly from the command line using a familiar shell interface. -# -# Reads the manifest saved by start_mcp_gateway.sh, queries each server for -# its tool list, and generates a standalone CLI wrapper script for each server. -# -# Generated CLI wrapper usage: -# --help Show all available commands -# --help Show help for a specific command -# [--param value...] Execute a command -# -# Environment variables: -# MCP_GATEWAY_API_KEY API key for MCP gateway authentication (required) -# -# Outputs (GitHub Actions): -# mounted-servers Comma-separated list of mounted server names -# -# Side effects: -# - Creates /tmp/gh-aw/mcp-cli/bin/ with CLI wrapper scripts (chmod 555) -# - Creates /tmp/gh-aw/mcp-cli/tools/ with per-server tool JSON caches -# - Appends /tmp/gh-aw/mcp-cli/bin to $GITHUB_PATH - -set -eo pipefail - -MANIFEST="/tmp/gh-aw/mcp-cli/manifest.json" -CLI_BIN_DIR="/tmp/gh-aw/mcp-cli/bin" -TOOLS_DIR="/tmp/gh-aw/mcp-cli/tools" - -# Internal MCP infrastructure servers that should not be exposed as user-facing CLIs -INTERNAL_SERVERS=("safeoutputs" "mcp-scripts") - -is_internal_server() { - local name="$1" - for internal in "${INTERNAL_SERVERS[@]}"; do - if [ "$name" = "$internal" ]; then - return 0 - fi - done - return 1 -} - -if [ ! -f "$MANIFEST" ]; then - echo "No MCP CLI manifest found at $MANIFEST, skipping CLI mounting" - exit 0 -fi - -echo "Mounting MCP servers as CLI tools..." -mkdir -p "$CLI_BIN_DIR" "$TOOLS_DIR" - -MOUNTED_SERVERS=() - -while IFS= read -r server_entry; do - SERVER_NAME=$(echo "$server_entry" | jq -r '.name') - SERVER_URL=$(echo "$server_entry" | jq -r '.url') - - # Skip internal infrastructure servers - if is_internal_server "$SERVER_NAME"; then - echo "Skipping internal server: $SERVER_NAME" - continue - fi - - echo "Mounting MCP server '$SERVER_NAME' (url: $SERVER_URL)..." - - TOOLS_FILE="$TOOLS_DIR/$SERVER_NAME.json" - - # Query tools list from the MCP server via the gateway - # Step 1: Initialize to establish a session (required by stateful transports) - INIT_RESP=$(curl -s -i --max-time 15 -X POST "$SERVER_URL" \ - -H "Authorization: Bearer $MCP_GATEWAY_API_KEY" \ - -H "Content-Type: application/json" \ - -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"mcp-cli-mount","version":"1.0.0"},"protocolVersion":"2024-11-05"}}' \ - 2>/dev/null || echo "") - - SESSION_ID=$(echo "$INIT_RESP" | grep -i "^mcp-session-id:" | awk '{print $2}' | tr -d '\r' 2>/dev/null || echo "") - - # Step 2: Fetch the tool list - SESSION_HEADER_ARG=() - if [ -n "$SESSION_ID" ]; then - SESSION_HEADER_ARG=(-H "Mcp-Session-Id: $SESSION_ID") - fi - - TOOLS_RESP=$(curl -s --max-time 15 -X POST "$SERVER_URL" \ - -H "Authorization: Bearer $MCP_GATEWAY_API_KEY" \ - -H "Content-Type: application/json" \ - "${SESSION_HEADER_ARG[@]}" \ - -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \ - 2>/dev/null || echo "{}") - - # Save tools to cache file (empty array if unavailable) - if ! echo "$TOOLS_RESP" | jq -c '.result.tools // []' > "$TOOLS_FILE" 2>/dev/null; then - echo "[]" > "$TOOLS_FILE" - fi - chmod 644 "$TOOLS_FILE" - - TOOL_COUNT=$(jq '. | length' "$TOOLS_FILE" 2>/dev/null || echo "0") - echo " Found $TOOL_COUNT tool(s)" - - # Generate CLI wrapper script for this server - CLI_SCRIPT="$CLI_BIN_DIR/$SERVER_NAME" - - # Write header with values baked in at creation time - cat > "$CLI_SCRIPT" << SCRIPT_EOF -#!/usr/bin/env bash -# MCP CLI wrapper for: $SERVER_NAME -# Auto-generated by gh-aw. Do not modify. -# -# Usage: -# $SERVER_NAME --help Show all available commands -# $SERVER_NAME --help Show help for a specific command -# $SERVER_NAME [--param value...] Execute a command -# -# Connects to: $SERVER_URL - -SERVER_NAME="$SERVER_NAME" -SERVER_URL="$SERVER_URL" -TOOLS_FILE="$TOOLS_FILE" - -# API key injected from the workflow environment -API_KEY="\${MCP_GATEWAY_API_KEY:-}" -if [ -z "\$API_KEY" ]; then - echo "Error: MCP_GATEWAY_API_KEY environment variable is not set" >&2 - exit 1 -fi - -load_tools() { - if [ -f "\$TOOLS_FILE" ]; then - cat "\$TOOLS_FILE" - else - echo "[]" - fi -} - -show_help() { - local tools - tools=\$(load_tools) - echo "Usage: \$SERVER_NAME [options]" - echo "" - echo "Available commands:" - if command -v jq &>/dev/null && echo "\$tools" | jq -e 'length > 0' >/dev/null 2>&1; then - echo "\$tools" | jq -r '.[] | " \(.name)\t\(.description // "No description")"' \ - | column -t -s \$'\t' 2>/dev/null \ - || echo "\$tools" | jq -r '.[] | " \(.name) \(.description // "")"' - else - echo " (tool list unavailable)" - fi - echo "" - echo "Run '\$SERVER_NAME --help' for more information on a command." -} - -show_tool_help() { - local tool_name="\$1" - local tools tool - tools=\$(load_tools) - tool=\$(echo "\$tools" | jq -r ".[] | select(.name == \"\$tool_name\")" 2>/dev/null || echo "") - - if [ -z "\$tool" ]; then - echo "Error: Unknown command '\$tool_name'" >&2 - echo "Run '\$SERVER_NAME --help' to see available commands." >&2 - exit 1 - fi - - echo "Command: \$tool_name" - echo "Description: \$(echo "\$tool" | jq -r '.description // "No description"')" - - local has_props - has_props=\$(echo "\$tool" | jq -r 'has("inputSchema") and ((.inputSchema.properties // {}) | length > 0)') - - if [ "\$has_props" = "true" ]; then - echo "" - echo "Options:" - echo "\$tool" | jq -r '.inputSchema.properties | to_entries[] | - " --\(.key) \(.value.description // .value.type // "string")"' - local required - required=\$(echo "\$tool" | jq -r '(.inputSchema.required // []) | join(", ")') - if [ -n "\$required" ]; then - echo "" - echo "Required: \$required" - fi - fi -} - -call_tool() { - local tool_name="\$1" - shift - - # Parse --key value arguments into a JSON object - local args="{}" - while [[ \$# -gt 0 ]]; do - if [[ "\$1" == --* ]]; then - local key="\${1#--}" - if [[ \$# -ge 2 && "\$2" != --* ]]; then - local val="\$2" - args=\$(echo "\$args" | jq --arg k "\$key" --arg v "\$val" '. + {(\$k): \$v}') - shift 2 - else - args=\$(echo "\$args" | jq --arg k "\$key" '. + {(\$k): true}') - shift 1 - fi - else - shift - fi - done - - # Initialize MCP session to establish a stateful connection - local init_resp session_id - init_resp=\$(curl -s -i --max-time 30 -X POST "\$SERVER_URL" \ - -H "Authorization: Bearer \$API_KEY" \ - -H "Content-Type: application/json" \ - -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"mcp-cli","version":"1.0.0"},"protocolVersion":"2024-11-05"}}' \ - 2>/dev/null || echo "") - - session_id=\$(echo "\$init_resp" | grep -i "^mcp-session-id:" | awk '{print \$2}' | tr -d '\r' 2>/dev/null || echo "") - - # Build tool call request - local request - request=\$(jq -n --arg name "\$tool_name" --argjson args "\$args" \ - '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":\$name,"arguments":\$args}}') - - # Invoke the tool via the gateway - local session_header_args=() - if [ -n "\$session_id" ]; then - session_header_args=(-H "Mcp-Session-Id: \$session_id") - fi - - local response - response=\$(curl -s --max-time 120 -X POST "\$SERVER_URL" \ - -H "Authorization: Bearer \$API_KEY" \ - -H "Content-Type: application/json" \ - "\${session_header_args[@]}" \ - -d "\$request" \ - 2>/dev/null) - - # Surface JSON-RPC errors - if echo "\$response" | jq -e '.error' >/dev/null 2>&1; then - local err_msg err_code - err_msg=\$(echo "\$response" | jq -r '.error.message // "Unknown error"') - err_code=\$(echo "\$response" | jq -r '.error.code // ""') - if [ -n "\$err_code" ]; then - echo "Error [\$err_code]: \$err_msg" >&2 - else - echo "Error: \$err_msg" >&2 - fi - exit 1 - fi - - # Print result content - if echo "\$response" | jq -e '.result.content' >/dev/null 2>&1; then - echo "\$response" | jq -r '.result.content[] | - if .type == "text" then .text - elif .type == "image" then "[image data - \(.mimeType // "unknown")]" - else (. | tostring) - end' - elif echo "\$response" | jq -e '.result' >/dev/null 2>&1; then - echo "\$response" | jq -r '.result' - else - echo "\$response" - fi -} - -# Main entry point -if [[ \$# -eq 0 || "\$1" == "--help" || "\$1" == "-h" ]]; then - show_help - exit 0 -fi - -COMMAND="\$1" -shift - -if [[ "\$1" == "--help" || "\$1" == "-h" ]]; then - show_tool_help "\$COMMAND" - exit 0 -fi - -call_tool "\$COMMAND" "\$@" -SCRIPT_EOF - - chmod 755 "$CLI_SCRIPT" - MOUNTED_SERVERS+=("$SERVER_NAME") - echo " ✓ Mounted as: $CLI_SCRIPT" -done < <(jq -c '.servers[]' "$MANIFEST") - -if [ "${#MOUNTED_SERVERS[@]}" -eq 0 ]; then - echo "No MCP servers mounted as CLI tools" - exit 0 -fi - -# Lock the CLI bin directory to prevent modification by the agent -chmod 555 "$CLI_BIN_DIR" - -# Add CLI bin directory to PATH for subsequent steps -echo "$CLI_BIN_DIR" >> "$GITHUB_PATH" - -echo "" -echo "Successfully mounted ${#MOUNTED_SERVERS[@]} MCP server(s) as CLI tools:" -for name in "${MOUNTED_SERVERS[@]}"; do - echo " - $name" -done -echo "" -echo "CLI bin directory: $CLI_BIN_DIR (read-only)" -echo "Added to PATH: yes (takes effect in subsequent steps)" - -# Emit GitHub Actions step output with the list of mounted servers -printf "mounted-servers=%s\n" "$( - IFS=',' - echo "${MOUNTED_SERVERS[*]}" -)" >> "$GITHUB_OUTPUT" diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go index 8bc9d7dc642..34a39231a7e 100644 --- a/pkg/workflow/mcp_cli_mount.go +++ b/pkg/workflow/mcp_cli_mount.go @@ -10,12 +10,13 @@ import ( // mcp_cli_mount.go generates a workflow step that mounts MCP servers as local CLI tools // and produces the prompt section that informs the agent about these tools. // -// After the MCP gateway is started, this step runs mount_mcp_as_cli.sh which: +// After the MCP gateway is started, this step runs mount_mcp_as_cli.cjs via +// actions/github-script which: // - Reads the CLI manifest saved by start_mcp_gateway.sh // - Queries each server for its tools/list via JSON-RPC // - Writes a standalone CLI wrapper script for each server to /tmp/gh-aw/mcp-cli/bin/ // - Locks the bin directory (chmod 555) so the agent cannot modify the scripts -// - Adds the directory to $GITHUB_PATH +// - Adds the directory to PATH via core.addPath() // internalMCPServerNames lists the MCP servers that are internal infrastructure and // should not be exposed as user-facing CLI tools. @@ -82,7 +83,13 @@ func (c *Compiler) generateMCPCLIMountStep(yaml *strings.Builder, data *Workflow yaml.WriteString(" continue-on-error: true\n") yaml.WriteString(" env:\n") yaml.WriteString(" MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }}\n") - yaml.WriteString(" run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh\n") + fmt.Fprintf(yaml, " uses: %s\n", GetActionPin("actions/github-script")) + yaml.WriteString(" with:\n") + yaml.WriteString(" script: |\n") + yaml.WriteString(" const { setupGlobals } = require('" + SetupActionDestination + "/setup_globals.cjs');\n") + yaml.WriteString(" setupGlobals(core, github, context, exec, io);\n") + yaml.WriteString(" const { main } = require('" + SetupActionDestination + "/mount_mcp_as_cli.cjs');\n") + yaml.WriteString(" await main();\n") } // buildMCPCLIPromptSection returns a PromptSection describing the CLI tools available @@ -111,7 +118,8 @@ func buildMCPCLIPromptSection(data *WorkflowData) *PromptSection { // mcpCLIToolsPromptTemplate is the inline prompt template for MCP CLI tools. // It uses the {MCP_CLI_SERVERS_LIST} placeholder which is replaced at compile time. -const mcpCLIToolsPromptTemplate = `## MCP Tools Available as CLI Commands +const mcpCLIToolsPromptTemplate = ` +## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -137,4 +145,5 @@ Each server is a standalone command in your PATH. Use them like any other shell - Parameters are passed as ` + "`" + `--name value` + "`" + ` pairs (all values are treated as strings unless the tool accepts booleans, in which case ` + "`" + `--flag` + "`" + ` with no value sets it to ` + "`" + `true` + "`" + `) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + ` diff --git a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden index 15468958bb0..350c1b3e8cf 100644 --- a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden +++ b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden @@ -113,6 +113,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_NORM_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -139,6 +140,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -379,7 +381,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden index 83e106d05de..b31f2b1a065 100644 --- a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden +++ b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden @@ -113,6 +113,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_NORM_EOF' + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: @@ -139,6 +140,7 @@ jobs: - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + The following GitHub context information is available for this workflow: @@ -380,7 +382,13 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - run: bash ${RUNNER_TEMP}/gh-aw/actions/mount_mcp_as_cli.sh + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: From a6cfa9157392dc0d083016e57774b33c9428eab2 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 15:05:54 +0000 Subject: [PATCH 03/19] feat: add tools.mount-as-clis flag, enable in smoke-copilot, filter from MCP config - Add MountAsCLIs bool field to ToolsConfig (tools_types.go, tools_parser.go) - Add mount-as-clis to JSON schema with description - getMCPCLIServerNames() returns nil unless mount-as-clis: true (opt-in) - composeCLIMountFilter() excludes CLI-mounted servers from MCP gateway config - Remove cache-memory from CLI mount candidates (file share, not MCP server) - Enable mount-as-clis: true in smoke-copilot.md - Update golden fixtures and recompile 179 lock files Agent-Logs-Url: https://github.com/github/gh-aw/sessions/126c5d4d-9ac8-4c4b-86ac-42eed55ea418 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/ace-editor.lock.yml | 41 ------ .../agent-performance-analyzer.lock.yml | 42 ------ .../workflows/agent-persona-explorer.lock.yml | 43 ------ .../agentic-observability-kit.lock.yml | 42 ------ .github/workflows/ai-moderator.lock.yml | 42 ------ .github/workflows/archie.lock.yml | 42 ------ .github/workflows/artifacts-summary.lock.yml | 41 ------ .github/workflows/audit-workflows.lock.yml | 43 ------ .github/workflows/auto-triage-issues.lock.yml | 41 ------ .github/workflows/blog-auditor.lock.yml | 42 ------ .github/workflows/bot-detection.lock.yml | 41 ------ .github/workflows/brave.lock.yml | 42 ------ .../breaking-change-checker.lock.yml | 41 ------ .github/workflows/changeset.lock.yml | 41 ------ .github/workflows/ci-coach.lock.yml | 42 ------ .github/workflows/ci-doctor.lock.yml | 42 ------ .../claude-code-user-docs-review.lock.yml | 42 ------ .../cli-consistency-checker.lock.yml | 41 ------ .../workflows/cli-version-checker.lock.yml | 42 ------ .github/workflows/cloclo.lock.yml | 45 ------ .../workflows/code-scanning-fixer.lock.yml | 42 ------ .github/workflows/code-simplifier.lock.yml | 41 ------ .../codex-github-remote-mcp-test.lock.yml | 41 ------ .../commit-changes-analyzer.lock.yml | 41 ------ .../constraint-solving-potd.lock.yml | 42 ------ .github/workflows/contribution-check.lock.yml | 41 ------ .../workflows/copilot-agent-analysis.lock.yml | 42 ------ .../copilot-cli-deep-research.lock.yml | 41 ------ .../copilot-pr-merged-report.lock.yml | 42 ------ .../copilot-pr-nlp-analysis.lock.yml | 42 ------ .../copilot-pr-prompt-analysis.lock.yml | 42 ------ .../copilot-session-insights.lock.yml | 42 ------ .github/workflows/craft.lock.yml | 41 ------ .../daily-architecture-diagram.lock.yml | 42 ------ .../daily-assign-issue-to-user.lock.yml | 41 ------ .github/workflows/daily-choice-test.lock.yml | 41 ------ .../workflows/daily-cli-performance.lock.yml | 41 ------ .../workflows/daily-cli-tools-tester.lock.yml | 42 ------ .github/workflows/daily-code-metrics.lock.yml | 42 ------ .../daily-community-attribution.lock.yml | 41 ------ .../workflows/daily-compiler-quality.lock.yml | 43 ------ .../daily-copilot-token-report.lock.yml | 42 ------ .github/workflows/daily-doc-healer.lock.yml | 43 ------ .github/workflows/daily-doc-updater.lock.yml | 43 ------ .github/workflows/daily-fact.lock.yml | 41 ------ .github/workflows/daily-file-diet.lock.yml | 42 ------ .../workflows/daily-firewall-report.lock.yml | 43 ------ .../workflows/daily-function-namer.lock.yml | 43 ------ .../daily-integrity-analysis.lock.yml | 43 ------ .../workflows/daily-issues-report.lock.yml | 42 ------ .../daily-malicious-code-scan.lock.yml | 41 ------ .../daily-mcp-concurrency-analysis.lock.yml | 43 ------ .../daily-multi-device-docs-tester.lock.yml | 42 ------ .github/workflows/daily-news.lock.yml | 43 ------ .../daily-observability-report.lock.yml | 42 ------ .../daily-performance-summary.lock.yml | 42 ------ .github/workflows/daily-regulatory.lock.yml | 41 ------ .../daily-rendering-scripts-verifier.lock.yml | 43 ------ .../workflows/daily-repo-chronicle.lock.yml | 42 ------ .../daily-safe-output-integrator.lock.yml | 41 ------ .../daily-safe-output-optimizer.lock.yml | 43 ------ .../daily-safe-outputs-conformance.lock.yml | 41 ------ .../workflows/daily-secrets-analysis.lock.yml | 41 ------ .../daily-security-red-team.lock.yml | 41 ------ .github/workflows/daily-semgrep-scan.lock.yml | 42 ------ .../daily-syntax-error-quality.lock.yml | 41 ------ .../daily-team-evolution-insights.lock.yml | 41 ------ .github/workflows/daily-team-status.lock.yml | 41 ------ .../daily-testify-uber-super-expert.lock.yml | 42 ------ .../workflows/daily-workflow-updater.lock.yml | 41 ------ .github/workflows/dead-code-remover.lock.yml | 42 ------ .github/workflows/deep-report.lock.yml | 43 ------ .github/workflows/delight.lock.yml | 41 ------ .github/workflows/dependabot-burner.lock.yml | 41 ------ .../workflows/dependabot-go-checker.lock.yml | 41 ------ .github/workflows/dev-hawk.lock.yml | 42 ------ .github/workflows/dev.lock.yml | 42 ------ .../developer-docs-consolidator.lock.yml | 44 ------ .github/workflows/dictation-prompt.lock.yml | 42 ------ .../workflows/discussion-task-miner.lock.yml | 41 ------ .github/workflows/docs-noob-tester.lock.yml | 42 ------ .github/workflows/draft-pr-cleanup.lock.yml | 41 ------ .../duplicate-code-detector.lock.yml | 42 ------ .../example-permissions-warning.lock.yml | 41 ------ .../example-workflow-analyzer.lock.yml | 42 ------ .github/workflows/firewall-escape.lock.yml | 42 ------ .github/workflows/firewall.lock.yml | 41 ------ .../workflows/functional-pragmatist.lock.yml | 41 ------ .../github-mcp-structural-analysis.lock.yml | 42 ------ .../github-mcp-tools-report.lock.yml | 42 ------ .../github-remote-mcp-auth-test.lock.yml | 41 ------ .../workflows/glossary-maintainer.lock.yml | 44 ------ .github/workflows/go-fan.lock.yml | 43 ------ .github/workflows/go-logger.lock.yml | 42 ------ .../workflows/go-pattern-detector.lock.yml | 42 ------ .github/workflows/gpclean.lock.yml | 42 ------ .github/workflows/grumpy-reviewer.lock.yml | 42 ------ .github/workflows/hourly-ci-cleaner.lock.yml | 41 ------ .../workflows/instructions-janitor.lock.yml | 42 ------ .github/workflows/issue-arborist.lock.yml | 41 ------ .github/workflows/issue-monster.lock.yml | 41 ------ .github/workflows/issue-triage-agent.lock.yml | 41 ------ .github/workflows/jsweep.lock.yml | 43 ------ .../workflows/layout-spec-maintainer.lock.yml | 41 ------ .github/workflows/lockfile-stats.lock.yml | 42 ------ .github/workflows/mcp-inspector.lock.yml | 57 -------- .github/workflows/mergefest.lock.yml | 41 ------ .github/workflows/metrics-collector.lock.yml | 42 ------ .../workflows/notion-issue-summary.lock.yml | 42 ------ .github/workflows/org-health-report.lock.yml | 42 ------ .github/workflows/pdf-summary.lock.yml | 43 ------ .github/workflows/plan.lock.yml | 41 ------ .github/workflows/poem-bot.lock.yml | 42 ------ .github/workflows/portfolio-analyst.lock.yml | 43 ------ .../workflows/pr-nitpick-reviewer.lock.yml | 42 ------ .github/workflows/pr-triage-agent.lock.yml | 41 ------ .../prompt-clustering-analysis.lock.yml | 43 ------ .github/workflows/python-data-charts.lock.yml | 43 ------ .github/workflows/q.lock.yml | 44 ------ .github/workflows/refiner.lock.yml | 41 ------ .github/workflows/release.lock.yml | 41 ------ .../workflows/repo-audit-analyzer.lock.yml | 42 ------ .github/workflows/repo-tree-map.lock.yml | 41 ------ .../repository-quality-improver.lock.yml | 43 ------ .github/workflows/research.lock.yml | 42 ------ .github/workflows/safe-output-health.lock.yml | 43 ------ .../schema-consistency-checker.lock.yml | 42 ------ .../schema-feature-coverage.lock.yml | 41 ------ .github/workflows/scout.lock.yml | 47 ------ .../workflows/security-compliance.lock.yml | 41 ------ .github/workflows/security-review.lock.yml | 43 ------ .../semantic-function-refactor.lock.yml | 42 ------ .github/workflows/sergo.lock.yml | 43 ------ .../workflows/slide-deck-maintainer.lock.yml | 43 ------ .../workflows/smoke-agent-all-merged.lock.yml | 41 ------ .../workflows/smoke-agent-all-none.lock.yml | 41 ------ .../smoke-agent-public-approved.lock.yml | 41 ------ .../smoke-agent-public-none.lock.yml | 41 ------ .../smoke-agent-scoped-approved.lock.yml | 41 ------ .../workflows/smoke-call-workflow.lock.yml | 41 ------ .github/workflows/smoke-claude.lock.yml | 46 ------ .github/workflows/smoke-codex.lock.yml | 45 ------ .github/workflows/smoke-copilot-arm.lock.yml | 45 ------ .github/workflows/smoke-copilot.lock.yml | 136 ++++-------------- .github/workflows/smoke-copilot.md | 1 + .../smoke-create-cross-repo-pr.lock.yml | 41 ------ .github/workflows/smoke-gemini.lock.yml | 42 ------ .github/workflows/smoke-multi-pr.lock.yml | 41 ------ .github/workflows/smoke-project.lock.yml | 41 ------ .../workflows/smoke-service-ports.lock.yml | 41 ------ .github/workflows/smoke-temporary-id.lock.yml | 41 ------ .github/workflows/smoke-test-tools.lock.yml | 41 ------ .../smoke-update-cross-repo-pr.lock.yml | 42 ------ .../smoke-workflow-call-with-inputs.lock.yml | 41 ------ .../workflows/smoke-workflow-call.lock.yml | 41 ------ .../workflows/stale-repo-identifier.lock.yml | 42 ------ .../workflows/static-analysis-report.lock.yml | 43 ------ .../workflows/step-name-alignment.lock.yml | 42 ------ .github/workflows/sub-issue-closer.lock.yml | 41 ------ .github/workflows/super-linter.lock.yml | 42 ------ .../workflows/technical-doc-writer.lock.yml | 43 ------ .github/workflows/terminal-stylist.lock.yml | 42 ------ .../test-create-pr-error-handling.lock.yml | 42 ------ .github/workflows/test-dispatcher.lock.yml | 41 ------ .../test-project-url-default.lock.yml | 41 ------ .github/workflows/test-workflow.lock.yml | 41 ------ .github/workflows/tidy.lock.yml | 41 ------ .github/workflows/typist.lock.yml | 42 ------ .../workflows/ubuntu-image-analyzer.lock.yml | 41 ------ .github/workflows/unbloat-docs.lock.yml | 44 ------ .github/workflows/update-astro.lock.yml | 41 ------ .github/workflows/video-analyzer.lock.yml | 41 ------ .../weekly-blog-post-writer.lock.yml | 43 ------ .../weekly-editors-health-check.lock.yml | 42 ------ .../workflows/weekly-issue-summary.lock.yml | 42 ------ .../weekly-safe-outputs-spec-review.lock.yml | 41 ------ .github/workflows/workflow-generator.lock.yml | 41 ------ .../workflow-health-manager.lock.yml | 41 ------ .../workflows/workflow-normalizer.lock.yml | 42 ------ .../workflow-skill-extractor.lock.yml | 41 ------ pkg/parser/schemas/main_workflow_schema.json | 12 +- pkg/workflow/mcp_cli_mount.go | 11 +- pkg/workflow/mcp_rendering.go | 31 +++- .../basic-copilot.golden | 41 ------ .../with-imports.golden | 41 ------ pkg/workflow/tools_parser.go | 9 ++ pkg/workflow/tools_types.go | 7 + 187 files changed, 94 insertions(+), 7663 deletions(-) diff --git a/.github/workflows/ace-editor.lock.yml b/.github/workflows/ace-editor.lock.yml index 41515d64a4d..32ef931ae78 100644 --- a/.github/workflows/ace-editor.lock.yml +++ b/.github/workflows/ace-editor.lock.yml @@ -189,35 +189,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_3b0f91d4e2fcc9d9_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -440,18 +411,6 @@ jobs: } } GH_AW_MCP_CONFIG_20e6f2291791c37c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agent-performance-analyzer.lock.yml b/.github/workflows/agent-performance-analyzer.lock.yml index cd938b34965..ecafc156c9a 100644 --- a/.github/workflows/agent-performance-analyzer.lock.yml +++ b/.github/workflows/agent-performance-analyzer.lock.yml @@ -161,36 +161,6 @@ jobs: Tools: add_comment(max:10), create_issue(max:5), create_discussion(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -757,18 +727,6 @@ jobs: } } GH_AW_MCP_CONFIG_d9c841c74e91f91c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agent-persona-explorer.lock.yml b/.github/workflows/agent-persona-explorer.lock.yml index 1a8bda48281..41b173ebb2c 100644 --- a/.github/workflows/agent-persona-explorer.lock.yml +++ b/.github/workflows/agent-persona-explorer.lock.yml @@ -169,37 +169,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -711,18 +680,6 @@ jobs: } } GH_AW_MCP_CONFIG_5ae1cb25093c05e1_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/agentic-observability-kit.lock.yml b/.github/workflows/agentic-observability-kit.lock.yml index ca62f6e6720..ebf498667b9 100644 --- a/.github/workflows/agentic-observability-kit.lock.yml +++ b/.github/workflows/agentic-observability-kit.lock.yml @@ -165,36 +165,6 @@ jobs: Tools: create_issue, create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -717,18 +687,6 @@ jobs: } } GH_AW_MCP_CONFIG_072a2a06a610d9da_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ai-moderator.lock.yml b/.github/workflows/ai-moderator.lock.yml index 4ddba695dd9..49555223573 100644 --- a/.github/workflows/ai-moderator.lock.yml +++ b/.github/workflows/ai-moderator.lock.yml @@ -203,36 +203,6 @@ jobs: Tools: add_labels, hide_comment(max:5), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -700,18 +670,6 @@ jobs: } } GH_AW_MCP_CONFIG_9cfc9d89b67815ed_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/archie.lock.yml b/.github/workflows/archie.lock.yml index 0620d70dc3f..469cc14b252 100644 --- a/.github/workflows/archie.lock.yml +++ b/.github/workflows/archie.lock.yml @@ -206,36 +206,6 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -718,18 +688,6 @@ jobs: } } GH_AW_MCP_CONFIG_1aecf03afd94e396_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/artifacts-summary.lock.yml b/.github/workflows/artifacts-summary.lock.yml index 7318027f71e..0d36efee638 100644 --- a/.github/workflows/artifacts-summary.lock.yml +++ b/.github/workflows/artifacts-summary.lock.yml @@ -154,35 +154,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -597,18 +568,6 @@ jobs: } } GH_AW_MCP_CONFIG_089491fa939a5dc3_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/audit-workflows.lock.yml b/.github/workflows/audit-workflows.lock.yml index ae4bcf11c7a..200489f7112 100644 --- a/.github/workflows/audit-workflows.lock.yml +++ b/.github/workflows/audit-workflows.lock.yml @@ -177,37 +177,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -780,18 +749,6 @@ jobs: } } GH_AW_MCP_CONFIG_dc00d5b21f5764cd_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/auto-triage-issues.lock.yml b/.github/workflows/auto-triage-issues.lock.yml index 61254ccbcbd..7b279f549cb 100644 --- a/.github/workflows/auto-triage-issues.lock.yml +++ b/.github/workflows/auto-triage-issues.lock.yml @@ -172,35 +172,6 @@ jobs: Tools: create_discussion, add_labels(max:10), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -633,18 +604,6 @@ jobs: } } GH_AW_MCP_CONFIG_17800b88a17b863b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/blog-auditor.lock.yml b/.github/workflows/blog-auditor.lock.yml index 752e5e5917f..51f721f5959 100644 --- a/.github/workflows/blog-auditor.lock.yml +++ b/.github/workflows/blog-auditor.lock.yml @@ -164,36 +164,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -636,18 +606,6 @@ jobs: } } GH_AW_MCP_CONFIG_582c8214644aae0b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/bot-detection.lock.yml b/.github/workflows/bot-detection.lock.yml index 011ce0cd923..86ab6b0092d 100644 --- a/.github/workflows/bot-detection.lock.yml +++ b/.github/workflows/bot-detection.lock.yml @@ -162,35 +162,6 @@ jobs: Tools: create_issue, update_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -681,18 +652,6 @@ jobs: } } GH_AW_MCP_CONFIG_fbf069f346e13146_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/brave.lock.yml b/.github/workflows/brave.lock.yml index fa601826b94..a2e6dd30c37 100644 --- a/.github/workflows/brave.lock.yml +++ b/.github/workflows/brave.lock.yml @@ -196,36 +196,6 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `brave-search` — run `brave-search --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -664,18 +634,6 @@ jobs: } } GH_AW_MCP_CONFIG_bdc9ed36a6083efb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/breaking-change-checker.lock.yml b/.github/workflows/breaking-change-checker.lock.yml index 6d9e6df621d..aec82c35007 100644 --- a/.github/workflows/breaking-change-checker.lock.yml +++ b/.github/workflows/breaking-change-checker.lock.yml @@ -158,35 +158,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -612,18 +583,6 @@ jobs: } } GH_AW_MCP_CONFIG_1c57e2cab2f2caf9_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/changeset.lock.yml b/.github/workflows/changeset.lock.yml index 90091a55f29..bd245b8a8b6 100644 --- a/.github/workflows/changeset.lock.yml +++ b/.github/workflows/changeset.lock.yml @@ -208,35 +208,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_913c1d056bceed0c_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -719,18 +690,6 @@ jobs: } } GH_AW_MCP_CONFIG_03abdce85ee0b9b7_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ci-coach.lock.yml b/.github/workflows/ci-coach.lock.yml index 76acf777a33..fa7523977af 100644 --- a/.github/workflows/ci-coach.lock.yml +++ b/.github/workflows/ci-coach.lock.yml @@ -166,36 +166,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_c3b070ffe5979e04_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -687,18 +657,6 @@ jobs: } } GH_AW_MCP_CONFIG_d174788768fb96df_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ci-doctor.lock.yml b/.github/workflows/ci-doctor.lock.yml index 44d31a08930..40ca9abfbfd 100644 --- a/.github/workflows/ci-doctor.lock.yml +++ b/.github/workflows/ci-doctor.lock.yml @@ -222,36 +222,6 @@ jobs: Tools: add_comment, create_issue, update_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -840,18 +810,6 @@ jobs: } } GH_AW_MCP_CONFIG_a6198c3e524b5cdb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/claude-code-user-docs-review.lock.yml b/.github/workflows/claude-code-user-docs-review.lock.yml index 5848e5595f0..39cbd71ec93 100644 --- a/.github/workflows/claude-code-user-docs-review.lock.yml +++ b/.github/workflows/claude-code-user-docs-review.lock.yml @@ -165,36 +165,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -633,18 +603,6 @@ jobs: } } GH_AW_MCP_CONFIG_82bfc77fc848bc07_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cli-consistency-checker.lock.yml b/.github/workflows/cli-consistency-checker.lock.yml index b7947af6e7d..55eef3e4f78 100644 --- a/.github/workflows/cli-consistency-checker.lock.yml +++ b/.github/workflows/cli-consistency-checker.lock.yml @@ -149,35 +149,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -600,18 +571,6 @@ jobs: } } GH_AW_MCP_CONFIG_0aa423252227dacb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cli-version-checker.lock.yml b/.github/workflows/cli-version-checker.lock.yml index 71f67c09767..4f9f647ca50 100644 --- a/.github/workflows/cli-version-checker.lock.yml +++ b/.github/workflows/cli-version-checker.lock.yml @@ -165,36 +165,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -641,18 +611,6 @@ jobs: } } GH_AW_MCP_CONFIG_68bf802d1e480d49_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/cloclo.lock.yml b/.github/workflows/cloclo.lock.yml index 96e3b47c977..974deb724ce 100644 --- a/.github/workflows/cloclo.lock.yml +++ b/.github/workflows/cloclo.lock.yml @@ -257,39 +257,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_910c108d300753ae_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -941,18 +908,6 @@ jobs: } } GH_AW_MCP_CONFIG_16ec4d0414e29855_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/code-scanning-fixer.lock.yml b/.github/workflows/code-scanning-fixer.lock.yml index 772bcd8accf..22766d599ef 100644 --- a/.github/workflows/code-scanning-fixer.lock.yml +++ b/.github/workflows/code-scanning-fixer.lock.yml @@ -161,36 +161,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ea41311dd97f7585_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -669,18 +639,6 @@ jobs: } } GH_AW_MCP_CONFIG_a60fb1ebbfa2b26b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/code-simplifier.lock.yml b/.github/workflows/code-simplifier.lock.yml index 97f1c8c733c..864ae344686 100644 --- a/.github/workflows/code-simplifier.lock.yml +++ b/.github/workflows/code-simplifier.lock.yml @@ -168,35 +168,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_958f7037a674f6ba_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -624,18 +595,6 @@ jobs: } } GH_AW_MCP_CONFIG_7a76b439cf427b72_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/codex-github-remote-mcp-test.lock.yml b/.github/workflows/codex-github-remote-mcp-test.lock.yml index 24e08f2def1..d0f79ec94af 100644 --- a/.github/workflows/codex-github-remote-mcp-test.lock.yml +++ b/.github/workflows/codex-github-remote-mcp-test.lock.yml @@ -151,35 +151,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_3d136f493b7edd72_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -428,18 +399,6 @@ jobs: } } GH_AW_MCP_CONFIG_c685301f8ea8b6a0_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/commit-changes-analyzer.lock.yml b/.github/workflows/commit-changes-analyzer.lock.yml index 6f236e424f4..413b2344e6e 100644 --- a/.github/workflows/commit-changes-analyzer.lock.yml +++ b/.github/workflows/commit-changes-analyzer.lock.yml @@ -163,35 +163,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -607,18 +578,6 @@ jobs: } } GH_AW_MCP_CONFIG_96c724bdb02bb676_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/constraint-solving-potd.lock.yml b/.github/workflows/constraint-solving-potd.lock.yml index d2f02a42d2f..1c2674560b6 100644 --- a/.github/workflows/constraint-solving-potd.lock.yml +++ b/.github/workflows/constraint-solving-potd.lock.yml @@ -158,36 +158,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -604,18 +574,6 @@ jobs: } } GH_AW_MCP_CONFIG_ac4bca1b70cc519b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/contribution-check.lock.yml b/.github/workflows/contribution-check.lock.yml index 4806d98ce01..7bb38b8cab3 100644 --- a/.github/workflows/contribution-check.lock.yml +++ b/.github/workflows/contribution-check.lock.yml @@ -159,35 +159,6 @@ jobs: Tools: add_comment(max:10), create_issue, add_labels(max:4), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -647,18 +618,6 @@ jobs: } } GH_AW_MCP_CONFIG_2eaf8996402089a2_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-agent-analysis.lock.yml b/.github/workflows/copilot-agent-analysis.lock.yml index 89a7575917c..1bcbf9ff460 100644 --- a/.github/workflows/copilot-agent-analysis.lock.yml +++ b/.github/workflows/copilot-agent-analysis.lock.yml @@ -171,36 +171,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -672,18 +642,6 @@ jobs: } } GH_AW_MCP_CONFIG_1a79405c65a64208_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-cli-deep-research.lock.yml b/.github/workflows/copilot-cli-deep-research.lock.yml index d4f49d2daf7..16f3f6831f5 100644 --- a/.github/workflows/copilot-cli-deep-research.lock.yml +++ b/.github/workflows/copilot-cli-deep-research.lock.yml @@ -155,35 +155,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -624,18 +595,6 @@ jobs: } } GH_AW_MCP_CONFIG_f96a821409b6a483_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-merged-report.lock.yml b/.github/workflows/copilot-pr-merged-report.lock.yml index 9340a9176f6..9d537199f5d 100644 --- a/.github/workflows/copilot-pr-merged-report.lock.yml +++ b/.github/workflows/copilot-pr-merged-report.lock.yml @@ -161,36 +161,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -762,18 +732,6 @@ jobs: } } GH_AW_MCP_CONFIG_214c4b63db1c096a_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-nlp-analysis.lock.yml b/.github/workflows/copilot-pr-nlp-analysis.lock.yml index 678dd74d972..2cdfc7d9673 100644 --- a/.github/workflows/copilot-pr-nlp-analysis.lock.yml +++ b/.github/workflows/copilot-pr-nlp-analysis.lock.yml @@ -168,36 +168,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -719,18 +689,6 @@ jobs: } } GH_AW_MCP_CONFIG_909ba834faadfa85_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-pr-prompt-analysis.lock.yml b/.github/workflows/copilot-pr-prompt-analysis.lock.yml index e3eb83c14d5..289c028e8ed 100644 --- a/.github/workflows/copilot-pr-prompt-analysis.lock.yml +++ b/.github/workflows/copilot-pr-prompt-analysis.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -666,18 +636,6 @@ jobs: } } GH_AW_MCP_CONFIG_7efc8a9b8bd1094b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/copilot-session-insights.lock.yml b/.github/workflows/copilot-session-insights.lock.yml index b7ba315c834..c9233c57614 100644 --- a/.github/workflows/copilot-session-insights.lock.yml +++ b/.github/workflows/copilot-session-insights.lock.yml @@ -177,36 +177,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -723,18 +693,6 @@ jobs: } } GH_AW_MCP_CONFIG_81cb9bf6bbab9ca6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/craft.lock.yml b/.github/workflows/craft.lock.yml index 4f623c0c8a1..25a6d45f55f 100644 --- a/.github/workflows/craft.lock.yml +++ b/.github/workflows/craft.lock.yml @@ -195,35 +195,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_c7b97f63987d3f1e_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -668,18 +639,6 @@ jobs: } } GH_AW_MCP_CONFIG_1b2dccce30014d92_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-architecture-diagram.lock.yml b/.github/workflows/daily-architecture-diagram.lock.yml index 0b6db06a121..79b9ae1f013 100644 --- a/.github/workflows/daily-architecture-diagram.lock.yml +++ b/.github/workflows/daily-architecture-diagram.lock.yml @@ -160,36 +160,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f5a79467418a74fe_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -668,18 +638,6 @@ jobs: } } GH_AW_MCP_CONFIG_ada8a355f17974cb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-assign-issue-to-user.lock.yml b/.github/workflows/daily-assign-issue-to-user.lock.yml index 245c408125a..0a1473f884f 100644 --- a/.github/workflows/daily-assign-issue-to-user.lock.yml +++ b/.github/workflows/daily-assign-issue-to-user.lock.yml @@ -148,35 +148,6 @@ jobs: Tools: add_comment, assign_to_user, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -603,18 +574,6 @@ jobs: } } GH_AW_MCP_CONFIG_905ec6d74bd3cef6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-choice-test.lock.yml b/.github/workflows/daily-choice-test.lock.yml index 8dba9ab3036..0f2a77f8b13 100644 --- a/.github/workflows/daily-choice-test.lock.yml +++ b/.github/workflows/daily-choice-test.lock.yml @@ -157,35 +157,6 @@ jobs: Tools: missing_tool, missing_data, noop, test_environment - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -601,18 +572,6 @@ jobs: } } GH_AW_MCP_CONFIG_9df20f616181b904_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-cli-performance.lock.yml b/.github/workflows/daily-cli-performance.lock.yml index 4382f3795a6..88b08b8a9cc 100644 --- a/.github/workflows/daily-cli-performance.lock.yml +++ b/.github/workflows/daily-cli-performance.lock.yml @@ -184,35 +184,6 @@ jobs: Tools: add_comment(max:5), create_issue(max:3), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -823,18 +794,6 @@ jobs: } } GH_AW_MCP_CONFIG_be21b238233abce6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-cli-tools-tester.lock.yml b/.github/workflows/daily-cli-tools-tester.lock.yml index e288c092b2b..b9f89545c3a 100644 --- a/.github/workflows/daily-cli-tools-tester.lock.yml +++ b/.github/workflows/daily-cli-tools-tester.lock.yml @@ -164,36 +164,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -690,18 +660,6 @@ jobs: } } GH_AW_MCP_CONFIG_f87695436f43f2f4_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-code-metrics.lock.yml b/.github/workflows/daily-code-metrics.lock.yml index 1b361b987ea..4220be6f4bb 100644 --- a/.github/workflows/daily-code-metrics.lock.yml +++ b/.github/workflows/daily-code-metrics.lock.yml @@ -172,36 +172,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -699,18 +669,6 @@ jobs: } } GH_AW_MCP_CONFIG_ac39fbd4537408b6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-community-attribution.lock.yml b/.github/workflows/daily-community-attribution.lock.yml index 4cc6f0fa01f..1ae1484f1e2 100644 --- a/.github/workflows/daily-community-attribution.lock.yml +++ b/.github/workflows/daily-community-attribution.lock.yml @@ -165,35 +165,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_3a6544334ea882c2_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -649,18 +620,6 @@ jobs: } } GH_AW_MCP_CONFIG_929cc945f361fa8d_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-compiler-quality.lock.yml b/.github/workflows/daily-compiler-quality.lock.yml index ec03f30a235..44229f73dd8 100644 --- a/.github/workflows/daily-compiler-quality.lock.yml +++ b/.github/workflows/daily-compiler-quality.lock.yml @@ -160,37 +160,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -689,18 +658,6 @@ jobs: } } GH_AW_MCP_CONFIG_8679f4bc190a1edd_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-copilot-token-report.lock.yml b/.github/workflows/daily-copilot-token-report.lock.yml index 6b567a28aec..e8125167ca8 100644 --- a/.github/workflows/daily-copilot-token-report.lock.yml +++ b/.github/workflows/daily-copilot-token-report.lock.yml @@ -168,36 +168,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -741,18 +711,6 @@ jobs: } } GH_AW_MCP_CONFIG_fcc05da5cd1839db_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-doc-healer.lock.yml b/.github/workflows/daily-doc-healer.lock.yml index be655c21791..7407192eb4c 100644 --- a/.github/workflows/daily-doc-healer.lock.yml +++ b/.github/workflows/daily-doc-healer.lock.yml @@ -172,37 +172,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_1ab69342d96baba9_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -754,18 +723,6 @@ jobs: } } GH_AW_MCP_CONFIG_9095aa0893fa6ab9_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-doc-updater.lock.yml b/.github/workflows/daily-doc-updater.lock.yml index e5db6d8f8f8..354ca5a1387 100644 --- a/.github/workflows/daily-doc-updater.lock.yml +++ b/.github/workflows/daily-doc-updater.lock.yml @@ -171,37 +171,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f28225f88d7db532_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -718,18 +687,6 @@ jobs: } } GH_AW_MCP_CONFIG_eec8b6fe34c3336b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-fact.lock.yml b/.github/workflows/daily-fact.lock.yml index fb646372b3d..cfd000e42f5 100644 --- a/.github/workflows/daily-fact.lock.yml +++ b/.github/workflows/daily-fact.lock.yml @@ -161,35 +161,6 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -693,18 +664,6 @@ jobs: } } GH_AW_MCP_CONFIG_baecbbeef522d057_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-file-diet.lock.yml b/.github/workflows/daily-file-diet.lock.yml index c539a6cb628..7a1be41b0c1 100644 --- a/.github/workflows/daily-file-diet.lock.yml +++ b/.github/workflows/daily-file-diet.lock.yml @@ -161,36 +161,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -679,18 +649,6 @@ jobs: } } GH_AW_MCP_CONFIG_1fb97ead37ab5212_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-firewall-report.lock.yml b/.github/workflows/daily-firewall-report.lock.yml index 796c8f31edd..dca6285ff82 100644 --- a/.github/workflows/daily-firewall-report.lock.yml +++ b/.github/workflows/daily-firewall-report.lock.yml @@ -172,37 +172,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -752,18 +721,6 @@ jobs: } } GH_AW_MCP_CONFIG_b63e8ed128cf6d89_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-function-namer.lock.yml b/.github/workflows/daily-function-namer.lock.yml index 01dc324e327..be5317bfdbb 100644 --- a/.github/workflows/daily-function-namer.lock.yml +++ b/.github/workflows/daily-function-namer.lock.yml @@ -166,37 +166,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -698,18 +667,6 @@ jobs: } } GH_AW_MCP_CONFIG_5419bcbc3315f546_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-integrity-analysis.lock.yml b/.github/workflows/daily-integrity-analysis.lock.yml index 33eb9655685..abdc93ced10 100644 --- a/.github/workflows/daily-integrity-analysis.lock.yml +++ b/.github/workflows/daily-integrity-analysis.lock.yml @@ -172,37 +172,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -769,18 +738,6 @@ jobs: } } GH_AW_MCP_CONFIG_a90c815e7f132927_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-issues-report.lock.yml b/.github/workflows/daily-issues-report.lock.yml index 7e07c7bdaf9..26e8994b8d6 100644 --- a/.github/workflows/daily-issues-report.lock.yml +++ b/.github/workflows/daily-issues-report.lock.yml @@ -178,36 +178,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -749,18 +719,6 @@ jobs: } } GH_AW_MCP_CONFIG_77f821b27d834424_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-malicious-code-scan.lock.yml b/.github/workflows/daily-malicious-code-scan.lock.yml index 79a3b251170..d7a5841ffb1 100644 --- a/.github/workflows/daily-malicious-code-scan.lock.yml +++ b/.github/workflows/daily-malicious-code-scan.lock.yml @@ -154,35 +154,6 @@ jobs: Tools: create_code_scanning_alert, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -610,18 +581,6 @@ jobs: } } GH_AW_MCP_CONFIG_83683437db802e24_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml index d0043e5a44c..1eb0b86c816 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.lock.yml +++ b/.github/workflows/daily-mcp-concurrency-analysis.lock.yml @@ -159,37 +159,6 @@ jobs: Tools: create_issue(max:5), create_agent_session(max:3), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -710,18 +679,6 @@ jobs: } } GH_AW_MCP_CONFIG_0491dbbd83e23c4f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml index d29c3ea6715..1b63cb7ddcf 100644 --- a/.github/workflows/daily-multi-device-docs-tester.lock.yml +++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml @@ -170,36 +170,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -670,18 +640,6 @@ jobs: } } GH_AW_MCP_CONFIG_dee616c5c06308f2_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-news.lock.yml b/.github/workflows/daily-news.lock.yml index f2d76d35b7e..d0f80461697 100644 --- a/.github/workflows/daily-news.lock.yml +++ b/.github/workflows/daily-news.lock.yml @@ -167,37 +167,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `tavily` — run `tavily --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -792,18 +761,6 @@ jobs: } } GH_AW_MCP_CONFIG_3abca47eab86dbce_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-observability-report.lock.yml b/.github/workflows/daily-observability-report.lock.yml index 6e7a48582d5..6fd2199bd7b 100644 --- a/.github/workflows/daily-observability-report.lock.yml +++ b/.github/workflows/daily-observability-report.lock.yml @@ -170,36 +170,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -731,18 +701,6 @@ jobs: } } GH_AW_MCP_CONFIG_3af8d89e5baa648f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-performance-summary.lock.yml b/.github/workflows/daily-performance-summary.lock.yml index 1d0be241a76..b032a8d989e 100644 --- a/.github/workflows/daily-performance-summary.lock.yml +++ b/.github/workflows/daily-performance-summary.lock.yml @@ -169,36 +169,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1149,18 +1119,6 @@ jobs: } } GH_AW_MCP_CONFIG_d1eb31902b227a1b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-regulatory.lock.yml b/.github/workflows/daily-regulatory.lock.yml index ccdfe6cf107..208960540df 100644 --- a/.github/workflows/daily-regulatory.lock.yml +++ b/.github/workflows/daily-regulatory.lock.yml @@ -162,35 +162,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1081,18 +1052,6 @@ jobs: } } GH_AW_MCP_CONFIG_39191bed09b411d6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-rendering-scripts-verifier.lock.yml b/.github/workflows/daily-rendering-scripts-verifier.lock.yml index 015da5d6743..597b51f719a 100644 --- a/.github/workflows/daily-rendering-scripts-verifier.lock.yml +++ b/.github/workflows/daily-rendering-scripts-verifier.lock.yml @@ -176,37 +176,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_526dda5557e006b5_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -729,18 +698,6 @@ jobs: } } GH_AW_MCP_CONFIG_0d1f10a17b7edb5f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml index 2eee7be83c6..8e55694b0e5 100644 --- a/.github/workflows/daily-repo-chronicle.lock.yml +++ b/.github/workflows/daily-repo-chronicle.lock.yml @@ -161,36 +161,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -669,18 +639,6 @@ jobs: } } GH_AW_MCP_CONFIG_ac24495438e56c9e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-output-integrator.lock.yml b/.github/workflows/daily-safe-output-integrator.lock.yml index 70407c5ecc0..194d6e7847c 100644 --- a/.github/workflows/daily-safe-output-integrator.lock.yml +++ b/.github/workflows/daily-safe-output-integrator.lock.yml @@ -157,35 +157,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_de84013d0b3384a0_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -611,18 +582,6 @@ jobs: } } GH_AW_MCP_CONFIG_904546420bba2ac6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-output-optimizer.lock.yml b/.github/workflows/daily-safe-output-optimizer.lock.yml index b76f1533fae..ef177a2b179 100644 --- a/.github/workflows/daily-safe-output-optimizer.lock.yml +++ b/.github/workflows/daily-safe-output-optimizer.lock.yml @@ -174,37 +174,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -732,18 +701,6 @@ jobs: } } GH_AW_MCP_CONFIG_f1008ce58891551c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-safe-outputs-conformance.lock.yml b/.github/workflows/daily-safe-outputs-conformance.lock.yml index 587d08d9052..1b61bd46015 100644 --- a/.github/workflows/daily-safe-outputs-conformance.lock.yml +++ b/.github/workflows/daily-safe-outputs-conformance.lock.yml @@ -161,35 +161,6 @@ jobs: Tools: create_issue(max:10), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -610,18 +581,6 @@ jobs: } } GH_AW_MCP_CONFIG_ed0c97f560af7ab9_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-secrets-analysis.lock.yml b/.github/workflows/daily-secrets-analysis.lock.yml index 6bdede23c29..00e09af8017 100644 --- a/.github/workflows/daily-secrets-analysis.lock.yml +++ b/.github/workflows/daily-secrets-analysis.lock.yml @@ -154,35 +154,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -599,18 +570,6 @@ jobs: } } GH_AW_MCP_CONFIG_b987c38bcb160a34_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-security-red-team.lock.yml b/.github/workflows/daily-security-red-team.lock.yml index 01f63afeb87..0017fd47e84 100644 --- a/.github/workflows/daily-security-red-team.lock.yml +++ b/.github/workflows/daily-security-red-team.lock.yml @@ -162,35 +162,6 @@ jobs: Tools: create_issue(max:5), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -614,18 +585,6 @@ jobs: } } GH_AW_MCP_CONFIG_1d39cb685714b3c4_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-semgrep-scan.lock.yml b/.github/workflows/daily-semgrep-scan.lock.yml index 97ab174a8cd..02d216138f5 100644 --- a/.github/workflows/daily-semgrep-scan.lock.yml +++ b/.github/workflows/daily-semgrep-scan.lock.yml @@ -161,36 +161,6 @@ jobs: Tools: create_code_scanning_alert, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `semgrep` — run `semgrep --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -637,18 +607,6 @@ jobs: } } GH_AW_MCP_CONFIG_1b17b4ed5633b171_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-syntax-error-quality.lock.yml b/.github/workflows/daily-syntax-error-quality.lock.yml index a984e0b0d5e..1095aec7773 100644 --- a/.github/workflows/daily-syntax-error-quality.lock.yml +++ b/.github/workflows/daily-syntax-error-quality.lock.yml @@ -153,35 +153,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -615,18 +586,6 @@ jobs: } } GH_AW_MCP_CONFIG_427d7ff0f3021689_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-team-evolution-insights.lock.yml b/.github/workflows/daily-team-evolution-insights.lock.yml index ca6700e62b0..f53ad2834c9 100644 --- a/.github/workflows/daily-team-evolution-insights.lock.yml +++ b/.github/workflows/daily-team-evolution-insights.lock.yml @@ -162,35 +162,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -607,18 +578,6 @@ jobs: } } GH_AW_MCP_CONFIG_9c5bdf2d6f07f6fd_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-team-status.lock.yml b/.github/workflows/daily-team-status.lock.yml index a112788fb28..525d420ff54 100644 --- a/.github/workflows/daily-team-status.lock.yml +++ b/.github/workflows/daily-team-status.lock.yml @@ -169,35 +169,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -619,18 +590,6 @@ jobs: } } GH_AW_MCP_CONFIG_a8ae48bfebeab6ac_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-testify-uber-super-expert.lock.yml b/.github/workflows/daily-testify-uber-super-expert.lock.yml index a4c987816e0..16908e21662 100644 --- a/.github/workflows/daily-testify-uber-super-expert.lock.yml +++ b/.github/workflows/daily-testify-uber-super-expert.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -703,18 +673,6 @@ jobs: } } GH_AW_MCP_CONFIG_9801a019b807be10_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/daily-workflow-updater.lock.yml b/.github/workflows/daily-workflow-updater.lock.yml index d1c26b1664d..09f60f84430 100644 --- a/.github/workflows/daily-workflow-updater.lock.yml +++ b/.github/workflows/daily-workflow-updater.lock.yml @@ -153,35 +153,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ca1bb6eca19a6937_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -604,18 +575,6 @@ jobs: } } GH_AW_MCP_CONFIG_ded3d43bff6f4a01_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dead-code-remover.lock.yml b/.github/workflows/dead-code-remover.lock.yml index f2f6afd11db..da7d51c22fa 100644 --- a/.github/workflows/dead-code-remover.lock.yml +++ b/.github/workflows/dead-code-remover.lock.yml @@ -165,36 +165,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_bdef07df3fcaf856_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -656,18 +626,6 @@ jobs: } } GH_AW_MCP_CONFIG_ac605b6dffd51016_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/deep-report.lock.yml b/.github/workflows/deep-report.lock.yml index 0ee814992f6..2cf8deff8bc 100644 --- a/.github/workflows/deep-report.lock.yml +++ b/.github/workflows/deep-report.lock.yml @@ -175,37 +175,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -808,18 +777,6 @@ jobs: } } GH_AW_MCP_CONFIG_06a69b26b842771b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/delight.lock.yml b/.github/workflows/delight.lock.yml index 7057bac3f07..9bb6beafee3 100644 --- a/.github/workflows/delight.lock.yml +++ b/.github/workflows/delight.lock.yml @@ -158,35 +158,6 @@ jobs: Tools: create_issue(max:2), create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -663,18 +634,6 @@ jobs: } } GH_AW_MCP_CONFIG_17d1b71e7ef97bf6_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dependabot-burner.lock.yml b/.github/workflows/dependabot-burner.lock.yml index 5b82f84357b..019b8cfdf47 100644 --- a/.github/workflows/dependabot-burner.lock.yml +++ b/.github/workflows/dependabot-burner.lock.yml @@ -161,35 +161,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -611,18 +582,6 @@ jobs: } } GH_AW_MCP_CONFIG_4f351439e1605739_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dependabot-go-checker.lock.yml b/.github/workflows/dependabot-go-checker.lock.yml index 3ec41899510..7f43c265cbb 100644 --- a/.github/workflows/dependabot-go-checker.lock.yml +++ b/.github/workflows/dependabot-go-checker.lock.yml @@ -159,35 +159,6 @@ jobs: Tools: create_issue(max:10), close_issue(max:20), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -629,18 +600,6 @@ jobs: } } GH_AW_MCP_CONFIG_7ea7c063c0476146_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dev-hawk.lock.yml b/.github/workflows/dev-hawk.lock.yml index d2e8a8e60a5..b035fcc443c 100644 --- a/.github/workflows/dev-hawk.lock.yml +++ b/.github/workflows/dev-hawk.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -692,18 +662,6 @@ jobs: } } GH_AW_MCP_CONFIG_ab0350833da7ec40_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dev.lock.yml b/.github/workflows/dev.lock.yml index 2605e6e47ee..9cc72d59b60 100644 --- a/.github/workflows/dev.lock.yml +++ b/.github/workflows/dev.lock.yml @@ -217,36 +217,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -739,18 +709,6 @@ jobs: } } GH_AW_MCP_CONFIG_dbd02877d1f6e4f8_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/developer-docs-consolidator.lock.yml b/.github/workflows/developer-docs-consolidator.lock.yml index cf18896bcad..bbc58d52706 100644 --- a/.github/workflows/developer-docs-consolidator.lock.yml +++ b/.github/workflows/developer-docs-consolidator.lock.yml @@ -175,38 +175,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_b38f5e32f9abeaa2_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -832,18 +800,6 @@ jobs: } } GH_AW_MCP_CONFIG_d1a97433a4daeec5_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/dictation-prompt.lock.yml b/.github/workflows/dictation-prompt.lock.yml index ce1430d7e96..d34768965f4 100644 --- a/.github/workflows/dictation-prompt.lock.yml +++ b/.github/workflows/dictation-prompt.lock.yml @@ -163,36 +163,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_af0c22aa486b1fca_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -689,18 +659,6 @@ jobs: } } GH_AW_MCP_CONFIG_f79e6f0df29f0677_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/discussion-task-miner.lock.yml b/.github/workflows/discussion-task-miner.lock.yml index 1f2b45b7677..3541f1e2b6e 100644 --- a/.github/workflows/discussion-task-miner.lock.yml +++ b/.github/workflows/discussion-task-miner.lock.yml @@ -158,35 +158,6 @@ jobs: Tools: add_comment(max:3), create_issue(max:5), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -653,18 +624,6 @@ jobs: } } GH_AW_MCP_CONFIG_0c41d1cf13dc69ef_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/docs-noob-tester.lock.yml b/.github/workflows/docs-noob-tester.lock.yml index ab6976903d8..dcbbde4ed24 100644 --- a/.github/workflows/docs-noob-tester.lock.yml +++ b/.github/workflows/docs-noob-tester.lock.yml @@ -160,36 +160,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -640,18 +610,6 @@ jobs: } } GH_AW_MCP_CONFIG_fdb2d8f24ab043f5_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/draft-pr-cleanup.lock.yml b/.github/workflows/draft-pr-cleanup.lock.yml index cbb374a4a7e..ebb5cc8d0fb 100644 --- a/.github/workflows/draft-pr-cleanup.lock.yml +++ b/.github/workflows/draft-pr-cleanup.lock.yml @@ -149,35 +149,6 @@ jobs: Tools: add_comment(max:20), close_pull_request(max:10), add_labels(max:20), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -622,18 +593,6 @@ jobs: } } GH_AW_MCP_CONFIG_e6c8f82246cb70f3_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/duplicate-code-detector.lock.yml b/.github/workflows/duplicate-code-detector.lock.yml index f73fa39b5e5..22b363fe8c8 100644 --- a/.github/workflows/duplicate-code-detector.lock.yml +++ b/.github/workflows/duplicate-code-detector.lock.yml @@ -168,36 +168,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -727,18 +697,6 @@ jobs: } } GH_AW_MCP_CONFIG_ba1ec8c1aa410beb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/example-permissions-warning.lock.yml b/.github/workflows/example-permissions-warning.lock.yml index d6cc054be0f..3d798a56e2b 100644 --- a/.github/workflows/example-permissions-warning.lock.yml +++ b/.github/workflows/example-permissions-warning.lock.yml @@ -148,35 +148,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_5c3619dea31e9804_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -408,18 +379,6 @@ jobs: } } GH_AW_MCP_CONFIG_de5f7b75a2c85f8b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/example-workflow-analyzer.lock.yml b/.github/workflows/example-workflow-analyzer.lock.yml index a362e55581f..ea756da9e65 100644 --- a/.github/workflows/example-workflow-analyzer.lock.yml +++ b/.github/workflows/example-workflow-analyzer.lock.yml @@ -166,36 +166,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -682,18 +652,6 @@ jobs: } } GH_AW_MCP_CONFIG_b24fc15d7cd3393e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/firewall-escape.lock.yml b/.github/workflows/firewall-escape.lock.yml index 74c0ec2bac7..b9c429eb36f 100644 --- a/.github/workflows/firewall-escape.lock.yml +++ b/.github/workflows/firewall-escape.lock.yml @@ -176,36 +176,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -664,18 +634,6 @@ jobs: } } GH_AW_MCP_CONFIG_ed0f3038012ec10f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/firewall.lock.yml b/.github/workflows/firewall.lock.yml index 46ddb261df3..6272f77de1b 100644 --- a/.github/workflows/firewall.lock.yml +++ b/.github/workflows/firewall.lock.yml @@ -148,35 +148,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_51f527cfa56efa24_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -410,18 +381,6 @@ jobs: } } GH_AW_MCP_CONFIG_574888acb18b422c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/functional-pragmatist.lock.yml b/.github/workflows/functional-pragmatist.lock.yml index 3c7eb3fce34..5fef408a36a 100644 --- a/.github/workflows/functional-pragmatist.lock.yml +++ b/.github/workflows/functional-pragmatist.lock.yml @@ -163,35 +163,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_c168a14d0fc28a2f_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -616,18 +587,6 @@ jobs: } } GH_AW_MCP_CONFIG_36aa8fb910f8ac6e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-mcp-structural-analysis.lock.yml b/.github/workflows/github-mcp-structural-analysis.lock.yml index f6839282afe..f222869739f 100644 --- a/.github/workflows/github-mcp-structural-analysis.lock.yml +++ b/.github/workflows/github-mcp-structural-analysis.lock.yml @@ -169,36 +169,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -678,18 +648,6 @@ jobs: } } GH_AW_MCP_CONFIG_a1538eadb7702096_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-mcp-tools-report.lock.yml b/.github/workflows/github-mcp-tools-report.lock.yml index 9f98ab4256a..b0367806d54 100644 --- a/.github/workflows/github-mcp-tools-report.lock.yml +++ b/.github/workflows/github-mcp-tools-report.lock.yml @@ -169,36 +169,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_1af95d393f4b398a_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -673,18 +643,6 @@ jobs: } } GH_AW_MCP_CONFIG_07750a9d533cc384_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/github-remote-mcp-auth-test.lock.yml b/.github/workflows/github-remote-mcp-auth-test.lock.yml index c6e6d3f67ba..037959b366d 100644 --- a/.github/workflows/github-remote-mcp-auth-test.lock.yml +++ b/.github/workflows/github-remote-mcp-auth-test.lock.yml @@ -161,35 +161,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -615,18 +586,6 @@ jobs: } } GH_AW_MCP_CONFIG_89196e035e942d59_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/glossary-maintainer.lock.yml b/.github/workflows/glossary-maintainer.lock.yml index 31b8719137f..ae915cedcce 100644 --- a/.github/workflows/glossary-maintainer.lock.yml +++ b/.github/workflows/glossary-maintainer.lock.yml @@ -175,38 +175,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_6e15d7474d90bf3a_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -819,18 +787,6 @@ jobs: } } GH_AW_MCP_CONFIG_adf218d0f4ba2707_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-fan.lock.yml b/.github/workflows/go-fan.lock.yml index e70bd99f3ba..edbf9275817 100644 --- a/.github/workflows/go-fan.lock.yml +++ b/.github/workflows/go-fan.lock.yml @@ -168,37 +168,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -695,18 +664,6 @@ jobs: } } GH_AW_MCP_CONFIG_a10bea8653625418_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-logger.lock.yml b/.github/workflows/go-logger.lock.yml index 519dac4827c..6fa2bb7020c 100644 --- a/.github/workflows/go-logger.lock.yml +++ b/.github/workflows/go-logger.lock.yml @@ -169,36 +169,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_6d6cb0d29893f634_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -799,18 +769,6 @@ jobs: } } GH_AW_MCP_CONFIG_69356c4a7c3d1a8e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/go-pattern-detector.lock.yml b/.github/workflows/go-pattern-detector.lock.yml index e52b706a056..c689e970f54 100644 --- a/.github/workflows/go-pattern-detector.lock.yml +++ b/.github/workflows/go-pattern-detector.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `ast-grep` — run `ast-grep --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -635,18 +605,6 @@ jobs: } } GH_AW_MCP_CONFIG_dfb548a38ce6c86b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/gpclean.lock.yml b/.github/workflows/gpclean.lock.yml index 423e53c75ee..cc3c778c661 100644 --- a/.github/workflows/gpclean.lock.yml +++ b/.github/workflows/gpclean.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -640,18 +610,6 @@ jobs: } } GH_AW_MCP_CONFIG_952d5af838607375_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/grumpy-reviewer.lock.yml b/.github/workflows/grumpy-reviewer.lock.yml index 4fe25ed9993..313da0143f1 100644 --- a/.github/workflows/grumpy-reviewer.lock.yml +++ b/.github/workflows/grumpy-reviewer.lock.yml @@ -215,36 +215,6 @@ jobs: Tools: create_pull_request_review_comment(max:5), submit_pull_request_review, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -749,18 +719,6 @@ jobs: } } GH_AW_MCP_CONFIG_2198edc089fd5a7d_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/hourly-ci-cleaner.lock.yml b/.github/workflows/hourly-ci-cleaner.lock.yml index c2dc8a5e779..aa76a20d1ff 100644 --- a/.github/workflows/hourly-ci-cleaner.lock.yml +++ b/.github/workflows/hourly-ci-cleaner.lock.yml @@ -170,35 +170,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_73077ac1efa7ed06_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -668,18 +639,6 @@ jobs: } } GH_AW_MCP_CONFIG_fc13695802fe239f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/instructions-janitor.lock.yml b/.github/workflows/instructions-janitor.lock.yml index 71eb7d748f4..b84f71a9a09 100644 --- a/.github/workflows/instructions-janitor.lock.yml +++ b/.github/workflows/instructions-janitor.lock.yml @@ -164,36 +164,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_efd5c992561c134e_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -636,18 +606,6 @@ jobs: } } GH_AW_MCP_CONFIG_de038345cb4d5a5f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-arborist.lock.yml b/.github/workflows/issue-arborist.lock.yml index d30c512ddd3..fc1c9090d84 100644 --- a/.github/workflows/issue-arborist.lock.yml +++ b/.github/workflows/issue-arborist.lock.yml @@ -165,35 +165,6 @@ jobs: Tools: create_issue(max:5), create_discussion, link_sub_issue(max:50), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -713,18 +684,6 @@ jobs: } } GH_AW_MCP_CONFIG_1b783250b5f416ed_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-monster.lock.yml b/.github/workflows/issue-monster.lock.yml index 21669aa895c..6d8dfaf2640 100644 --- a/.github/workflows/issue-monster.lock.yml +++ b/.github/workflows/issue-monster.lock.yml @@ -529,35 +529,6 @@ jobs: Tools: add_comment(max:3), assign_to_agent(max:3), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -998,18 +969,6 @@ jobs: } } GH_AW_MCP_CONFIG_bb876e15355ae348_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/issue-triage-agent.lock.yml b/.github/workflows/issue-triage-agent.lock.yml index f8059d98766..4200cc3534f 100644 --- a/.github/workflows/issue-triage-agent.lock.yml +++ b/.github/workflows/issue-triage-agent.lock.yml @@ -160,35 +160,6 @@ jobs: Tools: add_comment, add_labels, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -598,18 +569,6 @@ jobs: } } GH_AW_MCP_CONFIG_2a65d7b11ae90e8e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/jsweep.lock.yml b/.github/workflows/jsweep.lock.yml index 1808daf573e..d0fde52f663 100644 --- a/.github/workflows/jsweep.lock.yml +++ b/.github/workflows/jsweep.lock.yml @@ -168,37 +168,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_eac1fdf49c0156e5_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -714,18 +683,6 @@ jobs: } } GH_AW_MCP_CONFIG_5bef3d8af077c803_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/layout-spec-maintainer.lock.yml b/.github/workflows/layout-spec-maintainer.lock.yml index 924734161f9..183c37d18f3 100644 --- a/.github/workflows/layout-spec-maintainer.lock.yml +++ b/.github/workflows/layout-spec-maintainer.lock.yml @@ -163,35 +163,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_f721fba8c5d6f4ce_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -620,18 +591,6 @@ jobs: } } GH_AW_MCP_CONFIG_86970275459cf827_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/lockfile-stats.lock.yml b/.github/workflows/lockfile-stats.lock.yml index 8012584196a..ee896eb0be4 100644 --- a/.github/workflows/lockfile-stats.lock.yml +++ b/.github/workflows/lockfile-stats.lock.yml @@ -165,36 +165,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -629,18 +599,6 @@ jobs: } } GH_AW_MCP_CONFIG_ad0a2f6a6eba97c1_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/mcp-inspector.lock.yml b/.github/workflows/mcp-inspector.lock.yml index 41078ffe8ba..c1a4e130dbf 100644 --- a/.github/workflows/mcp-inspector.lock.yml +++ b/.github/workflows/mcp-inspector.lock.yml @@ -200,51 +200,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop, notion_add_comment, post_to_slack_channel - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `arxiv` — run `arxiv --help` to see available tools - - `ast-grep` — run `ast-grep --help` to see available tools - - `brave-search` — run `brave-search --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `context7` — run `context7 --help` to see available tools - - `datadog` — run `datadog --help` to see available tools - - `deepwiki` — run `deepwiki --help` to see available tools - - `fabric-rti` — run `fabric-rti --help` to see available tools - - `github` — run `github --help` to see available tools - - `markitdown` — run `markitdown --help` to see available tools - - `memory` — run `memory --help` to see available tools - - `microsoftdocs` — run `microsoftdocs --help` to see available tools - - `notion` — run `notion --help` to see available tools - - `sentry` — run `sentry --help` to see available tools - - `serena` — run `serena --help` to see available tools - - `tavily` — run `tavily --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1158,18 +1113,6 @@ jobs: } } GH_AW_MCP_CONFIG_6b8f5add28aae19f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/mergefest.lock.yml b/.github/workflows/mergefest.lock.yml index 78fce35e3f4..54cb928c794 100644 --- a/.github/workflows/mergefest.lock.yml +++ b/.github/workflows/mergefest.lock.yml @@ -199,35 +199,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_c0b73803c180c67c_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -647,18 +618,6 @@ jobs: } } GH_AW_MCP_CONFIG_47f8b33c70b74959_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/metrics-collector.lock.yml b/.github/workflows/metrics-collector.lock.yml index ea1199bf0b1..b30ac1b66dd 100644 --- a/.github/workflows/metrics-collector.lock.yml +++ b/.github/workflows/metrics-collector.lock.yml @@ -159,36 +159,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/agentic_workflows_guide.md" cat "${RUNNER_TEMP}/gh-aw/prompts/repo_memory_prompt.md" cat << 'GH_AW_PROMPT_d850707bdb59dc40_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -523,18 +493,6 @@ jobs: } } GH_AW_MCP_CONFIG_5c9a9fd6c01a3192_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/notion-issue-summary.lock.yml b/.github/workflows/notion-issue-summary.lock.yml index 11d11d74154..dbc5b9a4af4 100644 --- a/.github/workflows/notion-issue-summary.lock.yml +++ b/.github/workflows/notion-issue-summary.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: missing_tool, missing_data, noop, notion_add_comment - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `notion` — run `notion --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -617,18 +587,6 @@ jobs: } } GH_AW_MCP_CONFIG_e39f260422a5657b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/org-health-report.lock.yml b/.github/workflows/org-health-report.lock.yml index c19dd0d64bd..883a9b6bc92 100644 --- a/.github/workflows/org-health-report.lock.yml +++ b/.github/workflows/org-health-report.lock.yml @@ -169,36 +169,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -678,18 +648,6 @@ jobs: } } GH_AW_MCP_CONFIG_5f628ad6754dfa0e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pdf-summary.lock.yml b/.github/workflows/pdf-summary.lock.yml index 2e7ad9aa129..6ed56e6163a 100644 --- a/.github/workflows/pdf-summary.lock.yml +++ b/.github/workflows/pdf-summary.lock.yml @@ -228,37 +228,6 @@ jobs: Tools: add_comment, create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `markitdown` — run `markitdown --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -747,18 +716,6 @@ jobs: } } GH_AW_MCP_CONFIG_3630b02970b0fa14_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/plan.lock.yml b/.github/workflows/plan.lock.yml index 367a87ad0c7..1dd19cedd85 100644 --- a/.github/workflows/plan.lock.yml +++ b/.github/workflows/plan.lock.yml @@ -200,35 +200,6 @@ jobs: Tools: create_issue(max:5), close_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -687,18 +658,6 @@ jobs: } } GH_AW_MCP_CONFIG_93e9bbbaf1b62840_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/poem-bot.lock.yml b/.github/workflows/poem-bot.lock.yml index c4111066d31..45b0ff645bb 100644 --- a/.github/workflows/poem-bot.lock.yml +++ b/.github/workflows/poem-bot.lock.yml @@ -226,36 +226,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -997,18 +967,6 @@ jobs: } } GH_AW_MCP_CONFIG_66acaa7ee379da27_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/portfolio-analyst.lock.yml b/.github/workflows/portfolio-analyst.lock.yml index 8d19a71b3be..84991ff5be2 100644 --- a/.github/workflows/portfolio-analyst.lock.yml +++ b/.github/workflows/portfolio-analyst.lock.yml @@ -173,37 +173,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -771,18 +740,6 @@ jobs: } } GH_AW_MCP_CONFIG_90c67d3c6678dbe8_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pr-nitpick-reviewer.lock.yml b/.github/workflows/pr-nitpick-reviewer.lock.yml index a9473df46d9..3bf10e7ea19 100644 --- a/.github/workflows/pr-nitpick-reviewer.lock.yml +++ b/.github/workflows/pr-nitpick-reviewer.lock.yml @@ -209,36 +209,6 @@ jobs: Tools: create_discussion, create_pull_request_review_comment(max:10), submit_pull_request_review, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -743,18 +713,6 @@ jobs: } } GH_AW_MCP_CONFIG_0eba254c4d20a470_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/pr-triage-agent.lock.yml b/.github/workflows/pr-triage-agent.lock.yml index be04bb9d4e2..022ac3662da 100644 --- a/.github/workflows/pr-triage-agent.lock.yml +++ b/.github/workflows/pr-triage-agent.lock.yml @@ -162,35 +162,6 @@ jobs: Tools: add_comment(max:50), create_issue, add_labels(max:100), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -672,18 +643,6 @@ jobs: } } GH_AW_MCP_CONFIG_78e23fcc3b0e1c0b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/prompt-clustering-analysis.lock.yml b/.github/workflows/prompt-clustering-analysis.lock.yml index 09e7cfcdea4..f55c308ec5c 100644 --- a/.github/workflows/prompt-clustering-analysis.lock.yml +++ b/.github/workflows/prompt-clustering-analysis.lock.yml @@ -177,37 +177,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -774,18 +743,6 @@ jobs: } } GH_AW_MCP_CONFIG_77d152322b306cbe_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/python-data-charts.lock.yml b/.github/workflows/python-data-charts.lock.yml index 1c538b0421f..3ed5f07e7da 100644 --- a/.github/workflows/python-data-charts.lock.yml +++ b/.github/workflows/python-data-charts.lock.yml @@ -169,37 +169,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -750,18 +719,6 @@ jobs: } } GH_AW_MCP_CONFIG_84c03101db8c2cf9_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/q.lock.yml b/.github/workflows/q.lock.yml index e84f44df5eb..11d933cbc9e 100644 --- a/.github/workflows/q.lock.yml +++ b/.github/workflows/q.lock.yml @@ -240,38 +240,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_a0c3414a8d08f8d7_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -907,18 +875,6 @@ jobs: } } GH_AW_MCP_CONFIG_c649e0fc30544e48_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/refiner.lock.yml b/.github/workflows/refiner.lock.yml index 89cb2d6faa2..6e19c45df69 100644 --- a/.github/workflows/refiner.lock.yml +++ b/.github/workflows/refiner.lock.yml @@ -189,35 +189,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_5537490e8c05e0e7_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -664,18 +635,6 @@ jobs: } } GH_AW_MCP_CONFIG_56bd6f8525212f70_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml index e909b077f1b..7bb716d3cee 100644 --- a/.github/workflows/release.lock.yml +++ b/.github/workflows/release.lock.yml @@ -177,35 +177,6 @@ jobs: Tools: update_release, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -634,18 +605,6 @@ jobs: } } GH_AW_MCP_CONFIG_c313bb4a07e4ca32_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml index 6e266c3e270..086e9dc83ea 100644 --- a/.github/workflows/repo-audit-analyzer.lock.yml +++ b/.github/workflows/repo-audit-analyzer.lock.yml @@ -167,36 +167,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -633,18 +603,6 @@ jobs: } } GH_AW_MCP_CONFIG_19f430b340c0d1a7_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repo-tree-map.lock.yml b/.github/workflows/repo-tree-map.lock.yml index e489884a398..d65e084e0b9 100644 --- a/.github/workflows/repo-tree-map.lock.yml +++ b/.github/workflows/repo-tree-map.lock.yml @@ -160,35 +160,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -601,18 +572,6 @@ jobs: } } GH_AW_MCP_CONFIG_0d763efc0e9c7c1e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/repository-quality-improver.lock.yml b/.github/workflows/repository-quality-improver.lock.yml index e61db6592c4..5d305136cf9 100644 --- a/.github/workflows/repository-quality-improver.lock.yml +++ b/.github/workflows/repository-quality-improver.lock.yml @@ -166,37 +166,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -695,18 +664,6 @@ jobs: } } GH_AW_MCP_CONFIG_6e8eee1df8ed1f5e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/research.lock.yml b/.github/workflows/research.lock.yml index aee35f4b7be..ed4c058b508 100644 --- a/.github/workflows/research.lock.yml +++ b/.github/workflows/research.lock.yml @@ -164,36 +164,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `tavily` — run `tavily --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -631,18 +601,6 @@ jobs: } } GH_AW_MCP_CONFIG_19a6ff64bafecf93_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/safe-output-health.lock.yml b/.github/workflows/safe-output-health.lock.yml index 5b7dbf4a4bf..d418965564c 100644 --- a/.github/workflows/safe-output-health.lock.yml +++ b/.github/workflows/safe-output-health.lock.yml @@ -171,37 +171,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -719,18 +688,6 @@ jobs: } } GH_AW_MCP_CONFIG_fe83dd43c163a91a_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/schema-consistency-checker.lock.yml b/.github/workflows/schema-consistency-checker.lock.yml index b3d301f0bbf..79e42d6c937 100644 --- a/.github/workflows/schema-consistency-checker.lock.yml +++ b/.github/workflows/schema-consistency-checker.lock.yml @@ -165,36 +165,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -629,18 +599,6 @@ jobs: } } GH_AW_MCP_CONFIG_25341b3ac158b212_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/schema-feature-coverage.lock.yml b/.github/workflows/schema-feature-coverage.lock.yml index 3e13728152e..94059d8203d 100644 --- a/.github/workflows/schema-feature-coverage.lock.yml +++ b/.github/workflows/schema-feature-coverage.lock.yml @@ -164,35 +164,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_98b78c552e118305_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -650,18 +621,6 @@ jobs: } } GH_AW_MCP_CONFIG_284f7123e1795d39_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/scout.lock.yml b/.github/workflows/scout.lock.yml index e95e9834ae6..15dd343edad 100644 --- a/.github/workflows/scout.lock.yml +++ b/.github/workflows/scout.lock.yml @@ -259,41 +259,6 @@ jobs: Tools: add_comment, add_labels, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `arxiv` — run `arxiv --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `deepwiki` — run `deepwiki --help` to see available tools - - `github` — run `github --help` to see available tools - - `markitdown` — run `markitdown --help` to see available tools - - `microsoftdocs` — run `microsoftdocs --help` to see available tools - - `tavily` — run `tavily --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -845,18 +810,6 @@ jobs: } } GH_AW_MCP_CONFIG_c538088c873f5c73_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/security-compliance.lock.yml b/.github/workflows/security-compliance.lock.yml index 47a7097576f..bc3adff777c 100644 --- a/.github/workflows/security-compliance.lock.yml +++ b/.github/workflows/security-compliance.lock.yml @@ -169,35 +169,6 @@ jobs: Tools: create_issue(max:100), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -645,18 +616,6 @@ jobs: } } GH_AW_MCP_CONFIG_8ecaeb64faf4c6d2_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/security-review.lock.yml b/.github/workflows/security-review.lock.yml index 66c1f292263..9e3dcb2246d 100644 --- a/.github/workflows/security-review.lock.yml +++ b/.github/workflows/security-review.lock.yml @@ -212,37 +212,6 @@ jobs: Tools: create_pull_request_review_comment(max:10), submit_pull_request_review, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -795,18 +764,6 @@ jobs: } } GH_AW_MCP_CONFIG_bda0e8027f180b5a_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/semantic-function-refactor.lock.yml b/.github/workflows/semantic-function-refactor.lock.yml index a9d1ac08d46..330d1b5906a 100644 --- a/.github/workflows/semantic-function-refactor.lock.yml +++ b/.github/workflows/semantic-function-refactor.lock.yml @@ -164,36 +164,6 @@ jobs: Tools: create_issue, close_issue(max:10), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -693,18 +663,6 @@ jobs: } } GH_AW_MCP_CONFIG_8e9a6c2f4204cba3_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/sergo.lock.yml b/.github/workflows/sergo.lock.yml index 28684290d26..1a57431e3d9 100644 --- a/.github/workflows/sergo.lock.yml +++ b/.github/workflows/sergo.lock.yml @@ -167,37 +167,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -693,18 +662,6 @@ jobs: } } GH_AW_MCP_CONFIG_fc9f4a3e84dd282e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/slide-deck-maintainer.lock.yml b/.github/workflows/slide-deck-maintainer.lock.yml index 24f26440184..1dcb094affc 100644 --- a/.github/workflows/slide-deck-maintainer.lock.yml +++ b/.github/workflows/slide-deck-maintainer.lock.yml @@ -178,37 +178,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_00fdac09910f5004_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -689,18 +658,6 @@ jobs: } } GH_AW_MCP_CONFIG_e80473f9ecc5ff8d_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-all-merged.lock.yml b/.github/workflows/smoke-agent-all-merged.lock.yml index 3b29da15aa2..2bfde7b5488 100644 --- a/.github/workflows/smoke-agent-all-merged.lock.yml +++ b/.github/workflows/smoke-agent-all-merged.lock.yml @@ -195,35 +195,6 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -656,18 +627,6 @@ jobs: } } GH_AW_MCP_CONFIG_73cdc9322ab8c7cb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-all-none.lock.yml b/.github/workflows/smoke-agent-all-none.lock.yml index 62723e057e7..950d9551707 100644 --- a/.github/workflows/smoke-agent-all-none.lock.yml +++ b/.github/workflows/smoke-agent-all-none.lock.yml @@ -195,35 +195,6 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -656,18 +627,6 @@ jobs: } } GH_AW_MCP_CONFIG_be500cd34233bd55_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-public-approved.lock.yml b/.github/workflows/smoke-agent-public-approved.lock.yml index 177f3c8dbed..cbc48a84835 100644 --- a/.github/workflows/smoke-agent-public-approved.lock.yml +++ b/.github/workflows/smoke-agent-public-approved.lock.yml @@ -200,35 +200,6 @@ jobs: Tools: add_comment(max:2), assign_to_agent, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -689,18 +660,6 @@ jobs: } } GH_AW_MCP_CONFIG_aed1dcf0af46bd24_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-public-none.lock.yml b/.github/workflows/smoke-agent-public-none.lock.yml index 57ef283a1fe..72bad1a1d2b 100644 --- a/.github/workflows/smoke-agent-public-none.lock.yml +++ b/.github/workflows/smoke-agent-public-none.lock.yml @@ -195,35 +195,6 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -656,18 +627,6 @@ jobs: } } GH_AW_MCP_CONFIG_2561f0fd9f0b6818_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-agent-scoped-approved.lock.yml b/.github/workflows/smoke-agent-scoped-approved.lock.yml index caf4c46a90e..e333511d628 100644 --- a/.github/workflows/smoke-agent-scoped-approved.lock.yml +++ b/.github/workflows/smoke-agent-scoped-approved.lock.yml @@ -199,35 +199,6 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -666,18 +637,6 @@ jobs: } } GH_AW_MCP_CONFIG_eae6eef7ac15ae9a_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-call-workflow.lock.yml b/.github/workflows/smoke-call-workflow.lock.yml index 6a53d318277..f553a2b2bff 100644 --- a/.github/workflows/smoke-call-workflow.lock.yml +++ b/.github/workflows/smoke-call-workflow.lock.yml @@ -178,35 +178,6 @@ jobs: Tools: call_workflow, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -640,18 +611,6 @@ jobs: } } GH_AW_MCP_CONFIG_da60e4ff2622cb40_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index c7c0518bdf1..d87967f1d84 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -239,40 +239,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_4ec99b0fd270d235_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - `serena` — run `serena --help` to see available tools - - `tavily` — run `tavily --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -2099,18 +2065,6 @@ jobs: } } GH_AW_MCP_CONFIG_82ac77150d4b9330_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-codex.lock.yml b/.github/workflows/smoke-codex.lock.yml index bbad49814b3..cd8ccaa2938 100644 --- a/.github/workflows/smoke-codex.lock.yml +++ b/.github/workflows/smoke-codex.lock.yml @@ -227,39 +227,6 @@ jobs: Tools: add_comment(max:2), create_issue, add_labels, remove_labels, unassign_from_user, hide_comment(max:5), missing_tool, missing_data, noop, add_smoked_label - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1207,18 +1174,6 @@ jobs: } } GH_AW_MCP_CONFIG_c3d48ebeb7d5907a_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-copilot-arm.lock.yml b/.github/workflows/smoke-copilot-arm.lock.yml index 66e1069302d..45b75bd5177 100644 --- a/.github/workflows/smoke-copilot-arm.lock.yml +++ b/.github/workflows/smoke-copilot-arm.lock.yml @@ -222,39 +222,6 @@ jobs: Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, add_labels, remove_labels, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -1560,18 +1527,6 @@ jobs: } } GH_AW_MCP_CONFIG_bbaab723be3e0d4f_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 58692bfd8ae..8d62aa86002 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -1,4 +1,4 @@ -# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"a7b4d7bf4f02611637cd82a7a5f7c06048689e94db970e6f73d90a2673fdecc7","agent_id":"copilot"} +# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"1fece18f9b1af73c6884f94206da8d057f2335bf8327dc656e3a847a008aee46","agent_id":"copilot"} # ___ _ _ # / _ \ | | (_) # | |_| | __ _ ___ _ __ | |_ _ ___ @@ -215,9 +215,9 @@ jobs: run: | bash ${RUNNER_TEMP}/gh-aw/actions/create_prompt_first.sh { - cat << 'GH_AW_PROMPT_9df51225daadb559_EOF' + cat << 'GH_AW_PROMPT_a660cff6b7e1c6bc_EOF' - GH_AW_PROMPT_9df51225daadb559_EOF + GH_AW_PROMPT_a660cff6b7e1c6bc_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/xpia.md" cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" @@ -225,7 +225,7 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/agentic_workflows_guide.md" cat "${RUNNER_TEMP}/gh-aw/prompts/cache_memory_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_prompt.md" - cat << 'GH_AW_PROMPT_9df51225daadb559_EOF' + cat << 'GH_AW_PROMPT_a660cff6b7e1c6bc_EOF' Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, reply_to_pull_request_review_comment(max:5), add_labels, remove_labels, set_issue_type, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message @@ -235,7 +235,6 @@ jobs: The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - `github` — run `github --help` to see available tools - `playwright` — run `playwright --help` to see available tools - `serena` — run `serena --help` to see available tools @@ -290,9 +289,9 @@ jobs: {{/if}} - GH_AW_PROMPT_9df51225daadb559_EOF + GH_AW_PROMPT_a660cff6b7e1c6bc_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/github_mcp_tools_with_safeoutputs_prompt.md" - cat << 'GH_AW_PROMPT_9df51225daadb559_EOF' + cat << 'GH_AW_PROMPT_a660cff6b7e1c6bc_EOF' ## Serena Code Analysis @@ -331,7 +330,7 @@ jobs: {{#runtime-import .github/workflows/shared/github-queries-mcp-script.md}} {{#runtime-import .github/workflows/shared/mcp/serena-go.md}} {{#runtime-import .github/workflows/smoke-copilot.md}} - GH_AW_PROMPT_9df51225daadb559_EOF + GH_AW_PROMPT_a660cff6b7e1c6bc_EOF } > "$GH_AW_PROMPT" - name: Interpolate variables and render templates uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 @@ -587,12 +586,12 @@ jobs: mkdir -p ${RUNNER_TEMP}/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/mcp-logs/safeoutputs - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_3c8a610621dc5cbf_EOF' + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_247fdef21b6c8a4b_EOF' {"add_comment":{"allowed_repos":["github/gh-aw"],"hide_older_comments":true,"max":2},"add_labels":{"allowed":["smoke-copilot"],"allowed_repos":["github/gh-aw"]},"create_discussion":{"category":"announcements","close_older_discussions":true,"close_older_key":"smoke-copilot","expires":2,"fallback_to_issue":true,"labels":["ai-generated"],"max":1},"create_issue":{"close_older_issues":true,"close_older_key":"smoke-copilot","expires":2,"group":true,"labels":["automation","testing"],"max":1},"create_pull_request_review_comment":{"max":5,"side":"RIGHT"},"dispatch_workflow":{"max":1,"workflow_files":{"haiku-printer":".yml"},"workflows":["haiku-printer"]},"missing_data":{},"missing_tool":{},"noop":{"max":1,"report-as-issue":"true"},"remove_labels":{"allowed":["smoke"]},"reply_to_pull_request_review_comment":{"max":5},"send-slack-message":{"description":"Send a message to Slack (stub for testing)","inputs":{"message":{"description":"The message to send","required":false,"type":"string"}},"output":"Slack message stub executed!"},"set_issue_type":{},"submit_pull_request_review":{"max":1}} - GH_AW_SAFE_OUTPUTS_CONFIG_3c8a610621dc5cbf_EOF + GH_AW_SAFE_OUTPUTS_CONFIG_247fdef21b6c8a4b_EOF - name: Write Safe Outputs Tools run: | - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/tools_meta.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_META_d67ffee6fad53472_EOF' + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/tools_meta.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_META_011ff0c80cdbd4b2_EOF' { "description_suffixes": { "add_comment": " CONSTRAINTS: Maximum 2 comment(s) can be added.", @@ -650,8 +649,8 @@ jobs: } ] } - GH_AW_SAFE_OUTPUTS_TOOLS_META_d67ffee6fad53472_EOF - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/validation.json << 'GH_AW_SAFE_OUTPUTS_VALIDATION_d8a24fe9ebf525ab_EOF' + GH_AW_SAFE_OUTPUTS_TOOLS_META_011ff0c80cdbd4b2_EOF + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/validation.json << 'GH_AW_SAFE_OUTPUTS_VALIDATION_f9407d3dd2d2111a_EOF' { "add_comment": { "defaultMax": 1, @@ -921,7 +920,7 @@ jobs: } } } - GH_AW_SAFE_OUTPUTS_VALIDATION_d8a24fe9ebf525ab_EOF + GH_AW_SAFE_OUTPUTS_VALIDATION_f9407d3dd2d2111a_EOF node ${RUNNER_TEMP}/gh-aw/actions/generate_safe_outputs_tools.cjs - name: Generate Safe Outputs MCP Server Config id: safe-outputs-config @@ -966,7 +965,7 @@ jobs: - name: Setup MCP Scripts Config run: | mkdir -p ${RUNNER_TEMP}/gh-aw/mcp-scripts/logs - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/tools.json << 'GH_AW_MCP_SCRIPTS_TOOLS_3e8f78b47058959a_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/tools.json << 'GH_AW_MCP_SCRIPTS_TOOLS_036c8eefc0459001_EOF' { "serverName": "mcpscripts", "version": "1.0.0", @@ -1082,8 +1081,8 @@ jobs: } ] } - GH_AW_MCP_SCRIPTS_TOOLS_3e8f78b47058959a_EOF - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs << 'GH_AW_MCP_SCRIPTS_SERVER_e7b909a1866941c3_EOF' + GH_AW_MCP_SCRIPTS_TOOLS_036c8eefc0459001_EOF + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs << 'GH_AW_MCP_SCRIPTS_SERVER_7bda93e32c4f5de2_EOF' const path = require("path"); const { startHttpServer } = require("./mcp_scripts_mcp_server_http.cjs"); const configPath = path.join(__dirname, "tools.json"); @@ -1097,12 +1096,12 @@ jobs: console.error("Failed to start mcp-scripts HTTP server:", error); process.exit(1); }); - GH_AW_MCP_SCRIPTS_SERVER_e7b909a1866941c3_EOF + GH_AW_MCP_SCRIPTS_SERVER_7bda93e32c4f5de2_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs - name: Setup MCP Scripts Tool Files run: | - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh << 'GH_AW_MCP_SCRIPTS_SH_GH_263ef6d96de89fb3_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh << 'GH_AW_MCP_SCRIPTS_SH_GH_2d467293945e09db_EOF' #!/bin/bash # Auto-generated mcp-script tool: gh # Execute any gh CLI command. This tool is accessible as 'mcpscripts-gh'. Provide the full command after 'gh' (e.g., args: 'pr list --limit 5'). The tool will run: gh . Use single quotes ' for complex args to avoid shell interpretation issues. @@ -1113,9 +1112,9 @@ jobs: echo " token: ${GH_AW_GH_TOKEN:0:6}..." GH_TOKEN="$GH_AW_GH_TOKEN" gh $INPUT_ARGS - GH_AW_MCP_SCRIPTS_SH_GH_263ef6d96de89fb3_EOF + GH_AW_MCP_SCRIPTS_SH_GH_2d467293945e09db_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_05d4ab943fe86ce9_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_3ca6aadecadcf578_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-discussion-query # Query GitHub discussions with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1250,9 +1249,9 @@ jobs: EOF fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_05d4ab943fe86ce9_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_3ca6aadecadcf578_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_8ef0432b17b9641c_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_3cbc391454f8fc2b_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-issue-query # Query GitHub issues with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1331,9 +1330,9 @@ jobs: fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_8ef0432b17b9641c_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_3cbc391454f8fc2b_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_c889f4807956eb81_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_23d9fb82d3487bcb_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-pr-query # Query GitHub pull requests with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1418,7 +1417,7 @@ jobs: fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_c889f4807956eb81_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_23d9fb82d3487bcb_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh - name: Generate MCP Scripts Server Config @@ -1489,47 +1488,9 @@ jobs: export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' mkdir -p /home/runner/.copilot - cat << GH_AW_MCP_CONFIG_7d1672508c35ebcf_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh + cat << GH_AW_MCP_CONFIG_bb0d842290324c48_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh { "mcpServers": { - "agenticworkflows": { - "type": "stdio", - "container": "localhost/gh-aw:dev", - "mounts": ["\${GITHUB_WORKSPACE}:\${GITHUB_WORKSPACE}:rw", "/tmp/gh-aw:/tmp/gh-aw:rw"], - "args": ["--network", "host", "-w", "\${GITHUB_WORKSPACE}"], - "env": { - "DEBUG": "*", - "GITHUB_TOKEN": "\${GITHUB_TOKEN}", - "GITHUB_ACTOR": "\${GITHUB_ACTOR}", - "GITHUB_REPOSITORY": "\${GITHUB_REPOSITORY}" - }, - "guard-policies": { - "write-sink": { - "accept": [ - "*" - ] - } - } - }, - "github": { - "type": "stdio", - "container": "ghcr.io/github/github-mcp-server:v0.32.0", - "env": { - "GITHUB_HOST": "\${GITHUB_SERVER_URL}", - "GITHUB_PERSONAL_ACCESS_TOKEN": "\${GITHUB_MCP_SERVER_TOKEN}", - "GITHUB_READ_ONLY": "1", - "GITHUB_TOOLSETS": "context,repos,issues,pull_requests" - }, - "guard-policies": { - "allow-only": { - "approval-labels": ${{ steps.parse-guard-vars.outputs.approval_labels }}, - "blocked-users": ${{ steps.parse-guard-vars.outputs.blocked_users }}, - "min-integrity": "approved", - "repos": "all", - "trusted-users": ${{ steps.parse-guard-vars.outputs.trusted_users }} - } - } - }, "mcpscripts": { "type": "http", "url": "http://host.docker.internal:$GH_AW_MCP_SCRIPTS_PORT", @@ -1544,20 +1505,6 @@ jobs: } } }, - "playwright": { - "type": "stdio", - "container": "mcr.microsoft.com/playwright/mcp", - "args": ["--init", "--network", "host", "--security-opt", "seccomp=unconfined", "--ipc=host"], - "entrypointArgs": ["--output-dir", "/tmp/gh-aw/mcp-logs/playwright", "--no-sandbox"], - "mounts": ["/tmp/gh-aw/mcp-logs:/tmp/gh-aw/mcp-logs:rw"], - "guard-policies": { - "write-sink": { - "accept": [ - "*" - ] - } - } - }, "safeoutputs": { "type": "http", "url": "http://host.docker.internal:$GH_AW_SAFE_OUTPUTS_PORT", @@ -1571,35 +1518,6 @@ jobs: ] } } - }, - "serena": { - "type": "stdio", - "container": "ghcr.io/github/serena-mcp-server:latest", - "entrypoint": "serena", - "entrypointArgs": [ - "start-mcp-server", - "--context", - "codex", - "--project", - "\${GITHUB_WORKSPACE}" - ], - "mounts": [ - "\${GITHUB_WORKSPACE}:\${GITHUB_WORKSPACE}:rw" - ], - "args": [ - "--network", - "host" - ], - "tools": [ - "*" - ], - "guard-policies": { - "write-sink": { - "accept": [ - "*" - ] - } - } } }, "gateway": { @@ -1609,7 +1527,7 @@ jobs: "payloadDir": "${MCP_GATEWAY_PAYLOAD_DIR}" } } - GH_AW_MCP_CONFIG_7d1672508c35ebcf_EOF + GH_AW_MCP_CONFIG_bb0d842290324c48_EOF - name: Mount MCP servers as CLIs id: mount-mcp-clis continue-on-error: true diff --git a/.github/workflows/smoke-copilot.md b/.github/workflows/smoke-copilot.md index 93649992299..a79604b572c 100644 --- a/.github/workflows/smoke-copilot.md +++ b/.github/workflows/smoke-copilot.md @@ -43,6 +43,7 @@ tools: - pelikhan playwright: web-fetch: + mount-as-clis: true runtimes: go: version: "1.25" diff --git a/.github/workflows/smoke-create-cross-repo-pr.lock.yml b/.github/workflows/smoke-create-cross-repo-pr.lock.yml index 4752359ec66..ee80a92c838 100644 --- a/.github/workflows/smoke-create-cross-repo-pr.lock.yml +++ b/.github/workflows/smoke-create-cross-repo-pr.lock.yml @@ -193,35 +193,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_b5851c5feae065c1_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -711,18 +682,6 @@ jobs: } } GH_AW_MCP_CONFIG_4e0fc3a9881a180e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-gemini.lock.yml b/.github/workflows/smoke-gemini.lock.yml index 10490b0e2a8..cee03969c71 100644 --- a/.github/workflows/smoke-gemini.lock.yml +++ b/.github/workflows/smoke-gemini.lock.yml @@ -217,36 +217,6 @@ jobs: Tools: add_comment(max:2), create_issue, add_labels, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -851,18 +821,6 @@ jobs: } } GH_AW_MCP_CONFIG_dc3832e9686c5ff4_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-multi-pr.lock.yml b/.github/workflows/smoke-multi-pr.lock.yml index 142af52f9f4..a91ce002702 100644 --- a/.github/workflows/smoke-multi-pr.lock.yml +++ b/.github/workflows/smoke-multi-pr.lock.yml @@ -211,35 +211,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_8176b7650e805e07_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -680,18 +651,6 @@ jobs: } } GH_AW_MCP_CONFIG_21037b0628df299c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-project.lock.yml b/.github/workflows/smoke-project.lock.yml index 1f29d5f2e9c..ffd7cbd66b1 100644 --- a/.github/workflows/smoke-project.lock.yml +++ b/.github/workflows/smoke-project.lock.yml @@ -210,35 +210,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_ba7946ed4c54c799_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -838,18 +809,6 @@ jobs: } } GH_AW_MCP_CONFIG_5aaca792fea31195_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-service-ports.lock.yml b/.github/workflows/smoke-service-ports.lock.yml index 77ec6ca8acb..f9bab96d08d 100644 --- a/.github/workflows/smoke-service-ports.lock.yml +++ b/.github/workflows/smoke-service-ports.lock.yml @@ -174,35 +174,6 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -614,18 +585,6 @@ jobs: } } GH_AW_MCP_CONFIG_4d3271670f04abd8_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-temporary-id.lock.yml b/.github/workflows/smoke-temporary-id.lock.yml index de91eae73fd..cd8007e3452 100644 --- a/.github/workflows/smoke-temporary-id.lock.yml +++ b/.github/workflows/smoke-temporary-id.lock.yml @@ -205,35 +205,6 @@ jobs: Tools: add_comment(max:2), create_issue(max:5), link_sub_issue(max:3), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -690,18 +661,6 @@ jobs: } } GH_AW_MCP_CONFIG_e916af4ce11580a1_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-test-tools.lock.yml b/.github/workflows/smoke-test-tools.lock.yml index e8e2401ce86..c45ef51b970 100644 --- a/.github/workflows/smoke-test-tools.lock.yml +++ b/.github/workflows/smoke-test-tools.lock.yml @@ -199,35 +199,6 @@ jobs: Tools: add_comment(max:2), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -656,18 +627,6 @@ jobs: } } GH_AW_MCP_CONFIG_4afe8cef8efb619c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-update-cross-repo-pr.lock.yml b/.github/workflows/smoke-update-cross-repo-pr.lock.yml index 6fd188f48d6..1e79073f1c5 100644 --- a/.github/workflows/smoke-update-cross-repo-pr.lock.yml +++ b/.github/workflows/smoke-update-cross-repo-pr.lock.yml @@ -196,36 +196,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_6b3177d37c27b8e8_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -726,18 +696,6 @@ jobs: } } GH_AW_MCP_CONFIG_814ac3400c1a07dd_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-workflow-call-with-inputs.lock.yml b/.github/workflows/smoke-workflow-call-with-inputs.lock.yml index 57aa24b7a2d..8e9e4bc2180 100644 --- a/.github/workflows/smoke-workflow-call-with-inputs.lock.yml +++ b/.github/workflows/smoke-workflow-call-with-inputs.lock.yml @@ -205,35 +205,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_auto_create_issue.md" cat << 'GH_AW_PROMPT_35a5dccbd8d9d9f9_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -656,18 +627,6 @@ jobs: } } GH_AW_MCP_CONFIG_dfe9f89b71d5cca2_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/smoke-workflow-call.lock.yml b/.github/workflows/smoke-workflow-call.lock.yml index 1f387833183..64401791a90 100644 --- a/.github/workflows/smoke-workflow-call.lock.yml +++ b/.github/workflows/smoke-workflow-call.lock.yml @@ -205,35 +205,6 @@ jobs: Tools: add_comment, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -640,18 +611,6 @@ jobs: } } GH_AW_MCP_CONFIG_93322c1ed722b990_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index 8797fffdf8d..6765f447d00 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -179,36 +179,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -748,18 +718,6 @@ jobs: } } GH_AW_MCP_CONFIG_ebcf5ba4522a9a8c_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/static-analysis-report.lock.yml b/.github/workflows/static-analysis-report.lock.yml index 18d4cbd14e3..9a0c1b24b74 100644 --- a/.github/workflows/static-analysis-report.lock.yml +++ b/.github/workflows/static-analysis-report.lock.yml @@ -168,37 +168,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -724,18 +693,6 @@ jobs: } } GH_AW_MCP_CONFIG_d7f650b7f588b3cb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/step-name-alignment.lock.yml b/.github/workflows/step-name-alignment.lock.yml index 042d2889948..dad3e4965bb 100644 --- a/.github/workflows/step-name-alignment.lock.yml +++ b/.github/workflows/step-name-alignment.lock.yml @@ -160,36 +160,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -629,18 +599,6 @@ jobs: } } GH_AW_MCP_CONFIG_5b790c46c781275b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/sub-issue-closer.lock.yml b/.github/workflows/sub-issue-closer.lock.yml index 5c5667e1adc..570eda34a20 100644 --- a/.github/workflows/sub-issue-closer.lock.yml +++ b/.github/workflows/sub-issue-closer.lock.yml @@ -156,35 +156,6 @@ jobs: Tools: add_comment(max:20), update_issue(max:20), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -643,18 +614,6 @@ jobs: } } GH_AW_MCP_CONFIG_7bbf5f57c18f1049_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/super-linter.lock.yml b/.github/workflows/super-linter.lock.yml index 6c5053efd29..bbd865e8131 100644 --- a/.github/workflows/super-linter.lock.yml +++ b/.github/workflows/super-linter.lock.yml @@ -165,36 +165,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -650,18 +620,6 @@ jobs: } } GH_AW_MCP_CONFIG_9891f0fddf3fb195_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/technical-doc-writer.lock.yml b/.github/workflows/technical-doc-writer.lock.yml index ef7a2faf2ce..caa51af168d 100644 --- a/.github/workflows/technical-doc-writer.lock.yml +++ b/.github/workflows/technical-doc-writer.lock.yml @@ -177,37 +177,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -808,18 +777,6 @@ jobs: } } GH_AW_MCP_CONFIG_b1b9da9c012c0a77_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/terminal-stylist.lock.yml b/.github/workflows/terminal-stylist.lock.yml index 0f6fb8ae993..f23b6ff5d22 100644 --- a/.github/workflows/terminal-stylist.lock.yml +++ b/.github/workflows/terminal-stylist.lock.yml @@ -163,36 +163,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -666,18 +636,6 @@ jobs: } } GH_AW_MCP_CONFIG_494463c69bd7cc06_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-create-pr-error-handling.lock.yml b/.github/workflows/test-create-pr-error-handling.lock.yml index 7e678531cb0..00b594e2c0d 100644 --- a/.github/workflows/test-create-pr-error-handling.lock.yml +++ b/.github/workflows/test-create-pr-error-handling.lock.yml @@ -161,36 +161,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_fd59cc5c2d1fc082_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -631,18 +601,6 @@ jobs: } } GH_AW_MCP_CONFIG_7be545c29dd38aeb_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-dispatcher.lock.yml b/.github/workflows/test-dispatcher.lock.yml index e84d9a5f4d8..35001d73c56 100644 --- a/.github/workflows/test-dispatcher.lock.yml +++ b/.github/workflows/test-dispatcher.lock.yml @@ -152,35 +152,6 @@ jobs: Tools: dispatch_workflow, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -585,18 +556,6 @@ jobs: } } GH_AW_MCP_CONFIG_1c24b4097a736efa_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-project-url-default.lock.yml b/.github/workflows/test-project-url-default.lock.yml index d1e858fb0bd..fe96443646d 100644 --- a/.github/workflows/test-project-url-default.lock.yml +++ b/.github/workflows/test-project-url-default.lock.yml @@ -153,35 +153,6 @@ jobs: Tools: update_project(max:5), create_project_status_update, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -646,18 +617,6 @@ jobs: } } GH_AW_MCP_CONFIG_353cf85114406809_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/test-workflow.lock.yml b/.github/workflows/test-workflow.lock.yml index 7d30c187701..6084c2e1a3d 100644 --- a/.github/workflows/test-workflow.lock.yml +++ b/.github/workflows/test-workflow.lock.yml @@ -151,35 +151,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_d2100dd9504f0ecb_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -409,18 +380,6 @@ jobs: } } GH_AW_MCP_CONFIG_6649ecbe0b98fcdc_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/tidy.lock.yml b/.github/workflows/tidy.lock.yml index 1ebf43d2a43..2bd7a647511 100644 --- a/.github/workflows/tidy.lock.yml +++ b/.github/workflows/tidy.lock.yml @@ -220,35 +220,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_push_to_pr_branch.md" cat << 'GH_AW_PROMPT_d35e31e70bc8be49_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -714,18 +685,6 @@ jobs: } } GH_AW_MCP_CONFIG_c9e3dc06238b8726_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/typist.lock.yml b/.github/workflows/typist.lock.yml index c82888410ff..a2bc8cc6367 100644 --- a/.github/workflows/typist.lock.yml +++ b/.github/workflows/typist.lock.yml @@ -164,36 +164,6 @@ jobs: Tools: create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -666,18 +636,6 @@ jobs: } } GH_AW_MCP_CONFIG_48c9b32d41e4a5f8_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/ubuntu-image-analyzer.lock.yml b/.github/workflows/ubuntu-image-analyzer.lock.yml index 6f5e6658ece..b49954f2809 100644 --- a/.github/workflows/ubuntu-image-analyzer.lock.yml +++ b/.github/workflows/ubuntu-image-analyzer.lock.yml @@ -167,35 +167,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_37168e83c534310c_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -622,18 +593,6 @@ jobs: } } GH_AW_MCP_CONFIG_d099ccc6759c4ef8_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/unbloat-docs.lock.yml b/.github/workflows/unbloat-docs.lock.yml index 6ac96f85fab..9a9cf2f00aa 100644 --- a/.github/workflows/unbloat-docs.lock.yml +++ b/.github/workflows/unbloat-docs.lock.yml @@ -223,38 +223,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -852,18 +820,6 @@ jobs: } } GH_AW_MCP_CONFIG_35b9f7c27ddc03d3_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/update-astro.lock.yml b/.github/workflows/update-astro.lock.yml index 09b6813c714..437974601a5 100644 --- a/.github/workflows/update-astro.lock.yml +++ b/.github/workflows/update-astro.lock.yml @@ -168,35 +168,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_60089bbd806a2741_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -630,18 +601,6 @@ jobs: } } GH_AW_MCP_CONFIG_4fa1cfb31f5631b1_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/video-analyzer.lock.yml b/.github/workflows/video-analyzer.lock.yml index 0ebd25cdfa8..4bcc315d10a 100644 --- a/.github/workflows/video-analyzer.lock.yml +++ b/.github/workflows/video-analyzer.lock.yml @@ -162,35 +162,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -621,18 +592,6 @@ jobs: } } GH_AW_MCP_CONFIG_c4f6aa2564f8ee10_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-blog-post-writer.lock.yml b/.github/workflows/weekly-blog-post-writer.lock.yml index 8616a341465..9df7f5c86fe 100644 --- a/.github/workflows/weekly-blog-post-writer.lock.yml +++ b/.github/workflows/weekly-blog-post-writer.lock.yml @@ -176,37 +176,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_37ff4ed646105a15_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - `qmd` — run `qmd --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -804,18 +773,6 @@ jobs: } } GH_AW_MCP_CONFIG_76f2280dd63b606b_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-editors-health-check.lock.yml b/.github/workflows/weekly-editors-health-check.lock.yml index 1433d536ace..37916047bd0 100644 --- a/.github/workflows/weekly-editors-health-check.lock.yml +++ b/.github/workflows/weekly-editors-health-check.lock.yml @@ -163,36 +163,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -643,18 +613,6 @@ jobs: } } GH_AW_MCP_CONFIG_b498f891f99b13f5_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-issue-summary.lock.yml b/.github/workflows/weekly-issue-summary.lock.yml index 9dd22e51851..0bf2141c2b4 100644 --- a/.github/workflows/weekly-issue-summary.lock.yml +++ b/.github/workflows/weekly-issue-summary.lock.yml @@ -170,36 +170,6 @@ jobs: upload_asset: provide a file path; returns a URL; assets are published after the workflow completes (safeoutputs). - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `cache-memory` — run `cache-memory --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -660,18 +630,6 @@ jobs: } } GH_AW_MCP_CONFIG_45402066e9c8035d_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml index 63fe22a2d90..6e55f4c9dfa 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.lock.yml +++ b/.github/workflows/weekly-safe-outputs-spec-review.lock.yml @@ -164,35 +164,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_create_pull_request.md" cat << 'GH_AW_PROMPT_dd5ce0f0ce7b0ccb_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -613,18 +584,6 @@ jobs: } } GH_AW_MCP_CONFIG_9571fdea0e79c2ac_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-generator.lock.yml b/.github/workflows/workflow-generator.lock.yml index eb03c71a72e..5227266c94b 100644 --- a/.github/workflows/workflow-generator.lock.yml +++ b/.github/workflows/workflow-generator.lock.yml @@ -196,35 +196,6 @@ jobs: Tools: update_issue, assign_to_agent, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -690,18 +661,6 @@ jobs: } } GH_AW_MCP_CONFIG_a89a20c6f3ef975e_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index ca3198a267d..bb5fe7e676b 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -164,35 +164,6 @@ jobs: Tools: add_comment(max:15), create_issue(max:10), update_issue(max:5), missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -711,18 +682,6 @@ jobs: } } GH_AW_MCP_CONFIG_65cf370b1871bead_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-normalizer.lock.yml b/.github/workflows/workflow-normalizer.lock.yml index 85a526a9cda..6d53254db2f 100644 --- a/.github/workflows/workflow-normalizer.lock.yml +++ b/.github/workflows/workflow-normalizer.lock.yml @@ -164,36 +164,6 @@ jobs: Tools: create_issue, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -689,18 +659,6 @@ jobs: } } GH_AW_MCP_CONFIG_b4cdeb8fad7b52fc_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/.github/workflows/workflow-skill-extractor.lock.yml b/.github/workflows/workflow-skill-extractor.lock.yml index a39520a1004..5bc17bbb54d 100644 --- a/.github/workflows/workflow-skill-extractor.lock.yml +++ b/.github/workflows/workflow-skill-extractor.lock.yml @@ -160,35 +160,6 @@ jobs: Tools: create_issue(max:3), create_discussion, missing_tool, missing_data, noop - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -636,18 +607,6 @@ jobs: } } GH_AW_MCP_CONFIG_c96a2c2698a1a0f4_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/pkg/parser/schemas/main_workflow_schema.json b/pkg/parser/schemas/main_workflow_schema.json index 66026536a35..8487ed46ec4 100644 --- a/pkg/parser/schemas/main_workflow_schema.json +++ b/pkg/parser/schemas/main_workflow_schema.json @@ -4286,6 +4286,11 @@ } ] ] + }, + "mount-as-clis": { + "type": "boolean", + "description": "When true, each user-facing MCP server is mounted as a standalone CLI tool on PATH. The agent can then call MCP servers via shell commands (e.g. 'github issue_read --method get ...'). Servers that are CLI-mounted are removed from the MCP gateway config. Default: false.", + "examples": [true] } }, "additionalProperties": { @@ -9161,7 +9166,12 @@ "type": "number", "minimum": 0 }, - "examples": [{ "my-custom-model": 2.5, "gpt-5": 3.0 }] + "examples": [ + { + "my-custom-model": 2.5, + "gpt-5": 3.0 + } + ] }, "token-class-weights": { "type": "object", diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go index 34a39231a7e..014498688f2 100644 --- a/pkg/workflow/mcp_cli_mount.go +++ b/pkg/workflow/mcp_cli_mount.go @@ -28,11 +28,18 @@ var internalMCPServerNames = map[string]bool{ // getMCPCLIServerNames returns the sorted list of MCP server names that will be // mounted as CLI tools. It includes standard MCP tools (github, playwright, etc.) // and custom MCP servers, but excludes internal infrastructure servers. +// Returns nil if tools.mount-as-clis is not set to true. func getMCPCLIServerNames(data *WorkflowData) []string { if data == nil { return nil } + // Only mount if tools.mount-as-clis: true is set. + // Also returns nil when tools configuration is missing entirely. + if data.ParsedTools == nil || !data.ParsedTools.MountAsCLIs { + return nil + } + var servers []string // Collect user-facing standard MCP tools from the raw Tools map @@ -40,9 +47,9 @@ func getMCPCLIServerNames(data *WorkflowData) []string { if toolValue == false { continue } - // Only include tools that have MCP servers (skip bash, web-fetch, web-search, edit, etc.) + // Only include tools that have MCP servers (skip bash, web-fetch, web-search, edit, cache-memory, etc.) switch toolName { - case "github", "playwright", "qmd", "cache-memory", "agentic-workflows": + case "github", "playwright", "qmd", "agentic-workflows": servers = append(servers, toolName) default: // Include custom MCP servers (not in the internal list) diff --git a/pkg/workflow/mcp_rendering.go b/pkg/workflow/mcp_rendering.go index 714c7949899..30e25d61a1d 100644 --- a/pkg/workflow/mcp_rendering.go +++ b/pkg/workflow/mcp_rendering.go @@ -104,14 +104,43 @@ func renderStandardJSONMCPConfig( ) error { mcpRenderingLog.Printf("Rendering standard JSON MCP config: config_path=%s tools=%d mcp_tools=%d", configPath, len(tools), len(mcpTools)) createRenderer := buildMCPRendererFactory(workflowData, "json", includeCopilotFields, inlineArgs) + + // Compose the engine-specific filter with the CLI-mounted servers filter. + // Servers that are mounted as CLIs should not appear in the MCP gateway config. + composedFilter := composeCLIMountFilter(filterTool, workflowData) + return RenderJSONMCPConfig(yaml, tools, mcpTools, workflowData, JSONMCPConfigOptions{ ConfigPath: configPath, GatewayConfig: buildMCPGatewayConfig(workflowData), Renderers: buildStandardJSONMCPRenderers(workflowData, createRenderer, renderCustom), - FilterTool: filterTool, + FilterTool: composedFilter, }) } +// composeCLIMountFilter returns a new filter function that additionally excludes +// any MCP servers that have been mounted as CLI tools (tools.mount-as-clis: true). +// It composes with the existing filter if one is provided. +func composeCLIMountFilter(existing func(string) bool, workflowData *WorkflowData) func(string) bool { + cliServers := getMCPCLIServerNames(workflowData) + if len(cliServers) == 0 { + // Nothing mounted as CLI — return the original filter unchanged + return existing + } + + cliSet := make(map[string]bool, len(cliServers)) + for _, name := range cliServers { + cliSet[name] = true + } + mcpRenderingLog.Printf("Excluding %d CLI-mounted servers from MCP gateway config: %v", len(cliServers), cliServers) + + return func(toolName string) bool { + if cliSet[toolName] { + return false // exclude: mounted as CLI + } + return existing == nil || existing(toolName) + } +} + // buildMCPRendererFactory creates a factory function for MCPConfigRendererUnified instances. // The returned function accepts isLast as a parameter and creates a renderer with engine-specific // options derived from the provided parameters and workflowData at call time. diff --git a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden index 350c1b3e8cf..e777485f867 100644 --- a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden +++ b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden @@ -113,35 +113,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_NORM_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -376,18 +347,6 @@ jobs: } } GH_AW_MCP_CONFIG_NORM_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden index b31f2b1a065..7c426adca49 100644 --- a/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden +++ b/pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden @@ -113,35 +113,6 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" cat << 'GH_AW_PROMPT_NORM_EOF' - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `github` — run `github --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -377,18 +348,6 @@ jobs: } } GH_AW_MCP_CONFIG_NORM_EOF - - name: Mount MCP servers as CLIs - id: mount-mcp-clis - continue-on-error: true - env: - MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 - with: - script: | - const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); - setupGlobals(core, github, context, exec, io); - const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); - await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: diff --git a/pkg/workflow/tools_parser.go b/pkg/workflow/tools_parser.go index 05b0a8bff66..ddeaea44a3b 100644 --- a/pkg/workflow/tools_parser.go +++ b/pkg/workflow/tools_parser.go @@ -147,6 +147,14 @@ func NewTools(toolsMap map[string]any) *Tools { tools.StartupTimeout = parseStartupTimeoutTool(val) } + if val, exists := toolsMap["mount-as-clis"]; exists { + if b, ok := val.(bool); ok { + tools.MountAsCLIs = b + } else { + toolsParserLog.Printf("Warning: mount-as-clis must be a boolean (true/false), ignoring value: %v", val) + } + } + // Extract custom MCP tools (anything not in the known list) knownTools := map[string]bool{ "github": true, @@ -162,6 +170,7 @@ func NewTools(toolsMap map[string]any) *Tools { "safety-prompt": true, "timeout": true, "startup-timeout": true, + "mount-as-clis": true, } customCount := 0 diff --git a/pkg/workflow/tools_types.go b/pkg/workflow/tools_types.go index c6172638015..a2efd4d14c9 100644 --- a/pkg/workflow/tools_types.go +++ b/pkg/workflow/tools_types.go @@ -83,6 +83,13 @@ type ToolsConfig struct { // Custom MCP tools (anything not in the above list) Custom map[string]MCPServerConfig `yaml:",inline"` + // MountAsCLIs enables mounting MCP servers as standalone CLI tools on PATH. + // When true, each user-facing MCP server gets a bash wrapper script placed in + // a read-only directory added to PATH, and those servers are removed from the + // MCP gateway config (so the agent uses the CLI instead of the MCP protocol). + // Default is false. + MountAsCLIs bool `yaml:"mount-as-clis,omitempty"` + // Raw map for backwards compatibility raw map[string]any } From 578ae436f7bde43366d14206cc279a99b6042795 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 15:17:36 +0000 Subject: [PATCH 04/19] fix: implement proper MCP session protocol in CLI wrappers - fetchMCPTools: adds notifications/initialized step between initialize and tools/list - generateCLIWrapperScript: call_tool() now follows the full MCP session protocol: 1. initialize (capture Mcp-Session-Id via -D header file, not -i) 2. notifications/initialized notification (required by MCP spec, 204 No Content) 3. tools/call within the established session - Updated JSDoc comments to reflect correct 3-step protocol sequence Agent-Logs-Url: https://github.com/github/gh-aw/sessions/0251eb93-048a-4005-a523-60e176ca71c0 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- actions/setup/js/mount_mcp_as_cli.cjs | 43 ++++++++++++++++++++++----- 1 file changed, 35 insertions(+), 8 deletions(-) diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs index d4c84da7d2c..1fb25b4521e 100644 --- a/actions/setup/js/mount_mcp_as_cli.cjs +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -90,7 +90,7 @@ function httpPostJSON(urlStr, headers, body, timeoutMs = 15000) { /** * Query the tools list from an MCP server via JSON-RPC. - * Follows the standard MCP handshake: initialize → tools/list. + * Follows the standard MCP handshake: initialize → notifications/initialized → tools/list. * * @param {string} serverUrl - HTTP URL of the MCP server endpoint * @param {string} apiKey - Bearer token for gateway authentication @@ -127,7 +127,15 @@ async function fetchMCPTools(serverUrl, apiKey, core) { return []; } - // Step 2: tools/list – get the available tool definitions + // Step 2: notifications/initialized – required by MCP spec to complete the handshake. + // The server responds with 204 No Content; errors here are non-fatal. + try { + await httpPostJSON(serverUrl, { ...authHeaders, ...sessionHeader }, { jsonrpc: "2.0", method: "notifications/initialized", params: {} }, 10000); + } catch (err) { + core.warning(` notifications/initialized failed for ${serverUrl}: ${err instanceof Error ? err.message : String(err)}`); + } + + // Step 3: tools/list – get the available tool definitions try { const listResp = await httpPostJSON(serverUrl, { ...authHeaders, ...sessionHeader }, { jsonrpc: "2.0", id: 2, method: "tools/list" }, 15000); const respBody = /** @type {Record} */ listResp.body; @@ -147,7 +155,8 @@ async function fetchMCPTools(serverUrl, apiKey, core) { /** * Generate the bash wrapper script content for a given MCP server. * The generated script is a self-contained CLI that delegates all calls - * to the MCP gateway via curl. + * to the MCP gateway via curl, following the proper MCP session protocol: + * initialize → notifications/initialized → tools/call. * * @param {string} serverName - Name of the MCP server * @param {string} serverUrl - HTTP URL of the MCP server endpoint @@ -254,20 +263,38 @@ call_tool() { fi done - local init_resp session_id session_header_args - init_resp=\$(curl -s -i --max-time 30 -X POST "\$SERVER_URL" \\ + # MCP session protocol: initialize → notifications/initialized → tools/call + # A separate headers file is used to capture the Mcp-Session-Id without mixing + # headers and body (curl -i mixes them, making parsing fragile). + local headers_file + headers_file=\$(mktemp) + + # Step 1: initialize – establish the session + curl -s -D "\$headers_file" --max-time 30 -X POST "\$SERVER_URL" \\ -H "Authorization: \$API_KEY" \\ -H "Content-Type: application/json" \\ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"mcp-cli","version":"1.0.0"},"protocolVersion":"2024-11-05"}}' \\ - 2>/dev/null || echo "") + >/dev/null 2>/dev/null || true - session_id=\$(echo "\$init_resp" | grep -i "^mcp-session-id:" | awk "{print \$2}" | tr -d "\\r" 2>/dev/null || echo "") + local session_id + session_id=\$(grep -i "^mcp-session-id:" "\$headers_file" 2>/dev/null | awk "{print \$2}" | tr -d "\\r" || echo "") + rm -f "\$headers_file" - session_header_args=() + local session_header_args=() if [ -n "\$session_id" ]; then session_header_args=(-H "Mcp-Session-Id: \$session_id") fi + # Step 2: notifications/initialized – required by MCP spec to complete the handshake. + # The server responds with 204 No Content; failures here are non-fatal. + curl -s --max-time 10 -X POST "\$SERVER_URL" \\ + -H "Authorization: \$API_KEY" \\ + -H "Content-Type: application/json" \\ + "\${session_header_args[@]}" \\ + -d '{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}' \\ + >/dev/null 2>/dev/null || true + + # Step 3: tools/call – execute the tool within the established session local request request=\$(jq -n --arg name "\$tool_name" --argjson args "\$args" \\ "{\\"jsonrpc\\":\\"2.0\\",\\"id\\":2,\\"method\\":\\"tools/call\\",\\"params\\":{\\"name\\":\$name,\\"arguments\\":\$args}}") From 6183bd69f6cca9dbc5051d72b5ed2186dd44c5e5 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 15:35:46 +0000 Subject: [PATCH 05/19] feat: move MCP CLI tools prompt to actions/setup/md template file - Create actions/setup/md/mcp_cli_tools_prompt.md with wrapper and __GH_AW_MCP_CLI_SERVERS_LIST__ placeholder for runtime substitution - Update buildMCPCLIPromptSection to use IsFile: true with GH_AW_MCP_CLI_SERVERS_LIST env var for the substitute_placeholders step - Remove inline mcpCLIToolsPromptTemplate constant from mcp_cli_mount.go - Remove redundant pkg/workflow/prompts/mcp_cli_tools_prompt.md - Recompile all 179 workflow lock files Agent-Logs-Url: https://github.com/github/gh-aw/sessions/4f7952c9-f3de-498a-a4cc-7fdf59e84b18 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 37 +++------------- .../setup/md}/mcp_cli_tools_prompt.md | 4 +- pkg/workflow/mcp_cli_mount.go | 44 +++---------------- 3 files changed, 15 insertions(+), 70 deletions(-) rename {pkg/workflow/prompts => actions/setup/md}/mcp_cli_tools_prompt.md (93%) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 8d62aa86002..bc81a926e7f 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -229,38 +229,9 @@ jobs: Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, reply_to_pull_request_review_comment(max:5), add_labels, remove_labels, set_issue_type, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message - - ## MCP Tools Available as CLI Commands - - The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - - - `agentic-workflows` — run `agentic-workflows --help` to see available tools - - `github` — run `github --help` to see available tools - - `playwright` — run `playwright --help` to see available tools - - `serena` — run `serena --help` to see available tools - - ### How to Use - - Each server is a standalone command in your PATH. Use them like any other shell command: - - ```bash - # Show all available tools for a server - --help - - # Show help for a specific tool - --help - - # Call a tool with parameters - --param1 value1 --param2 value2 - ``` - - ### Notes - - - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - - Results are printed to stdout; errors are printed to stderr - - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - - + GH_AW_PROMPT_a660cff6b7e1c6bc_EOF + cat "${RUNNER_TEMP}/gh-aw/prompts/mcp_cli_tools_prompt.md" + cat << 'GH_AW_PROMPT_a660cff6b7e1c6bc_EOF' The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -363,6 +334,7 @@ jobs: GH_AW_GITHUB_RUN_ID: ${{ github.run_id }} GH_AW_GITHUB_SERVER_URL: ${{ github.server_url }} GH_AW_GITHUB_WORKSPACE: ${{ github.workspace }} + GH_AW_MCP_CLI_SERVERS_LIST: "- `agentic-workflows` — run `agentic-workflows --help` to see available tools\n- `github` — run `github --help` to see available tools\n- `playwright` — run `playwright --help` to see available tools\n- `serena` — run `serena --help` to see available tools" GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED: ${{ needs.pre_activation.outputs.activated }} with: script: | @@ -387,6 +359,7 @@ jobs: GH_AW_GITHUB_RUN_ID: process.env.GH_AW_GITHUB_RUN_ID, GH_AW_GITHUB_SERVER_URL: process.env.GH_AW_GITHUB_SERVER_URL, GH_AW_GITHUB_WORKSPACE: process.env.GH_AW_GITHUB_WORKSPACE, + GH_AW_MCP_CLI_SERVERS_LIST: process.env.GH_AW_MCP_CLI_SERVERS_LIST, GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED: process.env.GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED } }); diff --git a/pkg/workflow/prompts/mcp_cli_tools_prompt.md b/actions/setup/md/mcp_cli_tools_prompt.md similarity index 93% rename from pkg/workflow/prompts/mcp_cli_tools_prompt.md rename to actions/setup/md/mcp_cli_tools_prompt.md index a2f141dfb0a..5b906a9de86 100644 --- a/pkg/workflow/prompts/mcp_cli_tools_prompt.md +++ b/actions/setup/md/mcp_cli_tools_prompt.md @@ -1,8 +1,9 @@ + ## MCP Tools Available as CLI Commands The following MCP servers have been mounted as local CLI commands and are available directly from the shell: -{MCP_CLI_SERVERS_LIST} +__GH_AW_MCP_CLI_SERVERS_LIST__ ### How to Use @@ -24,3 +25,4 @@ Each server is a standalone command in your PATH. Use them like any other shell - Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) - Results are printed to stdout; errors are printed to stderr - The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly + diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go index 014498688f2..91f35f0154e 100644 --- a/pkg/workflow/mcp_cli_mount.go +++ b/pkg/workflow/mcp_cli_mount.go @@ -101,6 +101,8 @@ func (c *Compiler) generateMCPCLIMountStep(yaml *strings.Builder, data *Workflow // buildMCPCLIPromptSection returns a PromptSection describing the CLI tools available // to the agent, or nil if there are no servers to mount. +// The prompt is loaded from actions/setup/md/mcp_cli_tools_prompt.md at runtime, +// with the __GH_AW_MCP_CLI_SERVERS_LIST__ placeholder substituted by the substitution step. func buildMCPCLIPromptSection(data *WorkflowData) *PromptSection { servers := getMCPCLIServerNames(data) if len(servers) == 0 { @@ -114,43 +116,11 @@ func buildMCPCLIPromptSection(data *WorkflowData) *PromptSection { } serversList := strings.Join(listLines, "\n") - // The prompt file uses a {MCP_CLI_SERVERS_LIST} placeholder; replace it inline - content := strings.ReplaceAll(mcpCLIToolsPromptTemplate, "{MCP_CLI_SERVERS_LIST}", serversList) - return &PromptSection{ - Content: content, - IsFile: false, + Content: mcpCLIToolsPromptFile, + IsFile: true, + EnvVars: map[string]string{ + "GH_AW_MCP_CLI_SERVERS_LIST": serversList, + }, } } - -// mcpCLIToolsPromptTemplate is the inline prompt template for MCP CLI tools. -// It uses the {MCP_CLI_SERVERS_LIST} placeholder which is replaced at compile time. -const mcpCLIToolsPromptTemplate = ` -## MCP Tools Available as CLI Commands - -The following MCP servers have been mounted as local CLI commands and are available directly from the shell: - -{MCP_CLI_SERVERS_LIST} - -### How to Use - -Each server is a standalone command in your PATH. Use them like any other shell command: - -` + "```bash" + ` -# Show all available tools for a server - --help - -# Show help for a specific tool - --help - -# Call a tool with parameters - --param1 value1 --param2 value2 -` + "```" + ` - -### Notes - -- Parameters are passed as ` + "`" + `--name value` + "`" + ` pairs (all values are treated as strings unless the tool accepts booleans, in which case ` + "`" + `--flag` + "`" + ` with no value sets it to ` + "`" + `true` + "`" + `) -- Results are printed to stdout; errors are printed to stderr -- The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly - -` From b15ce1bb09a96b39bd1669fa068a74ca8a7b3b2a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 15:48:24 +0000 Subject: [PATCH 06/19] fix: skip backtick-wrapped placeholder names in prompt validation The validate_prompt_placeholders.sh script was flagging __GH_AW_*__ occurrences wrapped in backtick code spans (e.g. `__GH_AW_MCP_CLI_SERVERS_LIST__` in PR descriptions) as unreplaced placeholders. Strip inline code spans before checking, since backtick-quoted text is documentation/code examples and not actual template placeholders that need substitution. Also add Test 5 to validate_prompt_placeholders_test.sh to cover this case. Agent-Logs-Url: https://github.com/github/gh-aw/sessions/9137131d-773d-4f04-876e-9a38a0118812 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .../setup/sh/validate_prompt_placeholders.sh | 7 ++++-- .../sh/validate_prompt_placeholders_test.sh | 23 +++++++++++++++++++ 2 files changed, 28 insertions(+), 2 deletions(-) diff --git a/actions/setup/sh/validate_prompt_placeholders.sh b/actions/setup/sh/validate_prompt_placeholders.sh index 847e2b07a8b..7e1b9536736 100755 --- a/actions/setup/sh/validate_prompt_placeholders.sh +++ b/actions/setup/sh/validate_prompt_placeholders.sh @@ -14,10 +14,13 @@ fi echo "🔍 Validating prompt placeholders..." # Check for unreplaced environment variable placeholders (format: __GH_AW_*__) -if grep -q "__GH_AW_" "$PROMPT_FILE"; then +# Strip inline code spans (`...`) before checking, since backtick-quoted occurrences +# are documentation/code examples (e.g., in PR descriptions) and not actual placeholders. +STRIPPED_PROMPT=$(sed 's/`[^`]*`//g' "$PROMPT_FILE") +if echo "$STRIPPED_PROMPT" | grep -q "__GH_AW_"; then echo "❌ Error: Found unreplaced placeholders in prompt file:" echo "" - grep -n "__GH_AW_" "$PROMPT_FILE" | head -20 + grep -n "__GH_AW_" "$PROMPT_FILE" | grep -v '`[^`]*__GH_AW_' | head -20 echo "" echo "These placeholders should have been replaced with their actual values." echo "This indicates a problem with the placeholder substitution step." diff --git a/actions/setup/sh/validate_prompt_placeholders_test.sh b/actions/setup/sh/validate_prompt_placeholders_test.sh index 5e74405d97a..b3407475bb8 100755 --- a/actions/setup/sh/validate_prompt_placeholders_test.sh +++ b/actions/setup/sh/validate_prompt_placeholders_test.sh @@ -94,4 +94,27 @@ else fi echo "" +# Test 5: Prompt with placeholder name in backtick code span (should pass - it's documentation) +echo "Test 5: Prompt with placeholder in backtick code span (should pass)" +cat > "$TEST_DIR/prompt_backtick.txt" << 'EOF' + +# System Instructions +You are a helpful assistant. + + +# User Task +This is a PR description that mentions `__GH_AW_MCP_CLI_SERVERS_LIST__` as documentation. +The value has already been substituted but the *name* appears in code formatting. +Also mentions `__GH_AW_GITHUB_ACTOR__` in inline code (safe). +EOF + +export GH_AW_PROMPT="$TEST_DIR/prompt_backtick.txt" +if bash "$SCRIPT_PATH"; then + echo "✅ Test 5 passed: Backtick-quoted placeholder names accepted" +else + echo "❌ Test 5 failed: Backtick-quoted placeholder names incorrectly rejected" + exit 1 +fi +echo "" + echo "🎉 All validation tests passed!" From 73ad5912b81736edc4c69944e9e8f706cc494451 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 17:10:41 +0000 Subject: [PATCH 07/19] feat: mount built-in MCPs (github, playwright, etc.) as CLIs Previously, CLI-mounted servers (github, playwright, agentic-workflows, etc.) were excluded from the MCP gateway config. This prevented the gateway from starting their Docker containers, so the CLI manifest was empty for those servers and mount_mcp_as_cli.cjs could not create wrappers for them. Fix: Stop filtering CLI-mounted servers from the gateway config so the gateway starts all containers and populates the manifest with all servers. Instead, filter CLI-mounted servers from the agent's final MCP config in each engine's conversion script (using the new GH_AW_MCP_CLI_SERVERS env var exported in the gateway step). Changes: - pkg/workflow/mcp_rendering.go: remove composeCLIMountFilter from renderStandardJSONMCPConfig; CLI-mounted servers now stay in gateway config so gateway starts their Docker containers. Remove the now- unused composeCLIMountFilter function. - pkg/workflow/mcp_setup_generator.go: export GH_AW_MCP_CLI_SERVERS (JSON array) in the gateway step script, after GH_AW_ENGINE. - actions/setup/sh/convert_gateway_config_copilot.sh: add --argjson cliServers filtering to jq call. - actions/setup/sh/convert_gateway_config_claude.sh: same. - actions/setup/sh/convert_gateway_config_gemini.sh: same. - actions/setup/sh/convert_gateway_config_codex.sh: same (TOML). - actions/setup/sh/start_mcp_gateway.sh: filter CLI servers from the default fallback agent MCP config. - Recompiled all 179 lock files. Agent-Logs-Url: https://github.com/github/gh-aw/sessions/f2adce8a-7104-4ec1-8c1e-2b24cd87eed5 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 82 +++++++++++++++++++ .../setup/sh/convert_gateway_config_claude.sh | 3 +- .../setup/sh/convert_gateway_config_codex.sh | 4 +- .../sh/convert_gateway_config_copilot.sh | 3 +- .../setup/sh/convert_gateway_config_gemini.sh | 3 +- actions/setup/sh/start_mcp_gateway.sh | 10 ++- pkg/workflow/mcp_rendering.go | 35 ++------ pkg/workflow/mcp_setup_generator.go | 11 +++ 8 files changed, 116 insertions(+), 35 deletions(-) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index bc81a926e7f..8dae6c2774c 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -1458,12 +1458,51 @@ jobs: export DEBUG="*" export GH_AW_ENGINE="copilot" + export GH_AW_MCP_CLI_SERVERS='["agentic-workflows","github","playwright","serena"]' export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' mkdir -p /home/runner/.copilot cat << GH_AW_MCP_CONFIG_bb0d842290324c48_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh { "mcpServers": { + "agenticworkflows": { + "type": "stdio", + "container": "localhost/gh-aw:dev", + "mounts": ["\${GITHUB_WORKSPACE}:\${GITHUB_WORKSPACE}:rw", "/tmp/gh-aw:/tmp/gh-aw:rw"], + "args": ["--network", "host", "-w", "\${GITHUB_WORKSPACE}"], + "env": { + "DEBUG": "*", + "GITHUB_TOKEN": "\${GITHUB_TOKEN}", + "GITHUB_ACTOR": "\${GITHUB_ACTOR}", + "GITHUB_REPOSITORY": "\${GITHUB_REPOSITORY}" + }, + "guard-policies": { + "write-sink": { + "accept": [ + "*" + ] + } + } + }, + "github": { + "type": "stdio", + "container": "ghcr.io/github/github-mcp-server:v0.32.0", + "env": { + "GITHUB_HOST": "\${GITHUB_SERVER_URL}", + "GITHUB_PERSONAL_ACCESS_TOKEN": "\${GITHUB_MCP_SERVER_TOKEN}", + "GITHUB_READ_ONLY": "1", + "GITHUB_TOOLSETS": "context,repos,issues,pull_requests" + }, + "guard-policies": { + "allow-only": { + "approval-labels": ${{ steps.parse-guard-vars.outputs.approval_labels }}, + "blocked-users": ${{ steps.parse-guard-vars.outputs.blocked_users }}, + "min-integrity": "approved", + "repos": "all", + "trusted-users": ${{ steps.parse-guard-vars.outputs.trusted_users }} + } + } + }, "mcpscripts": { "type": "http", "url": "http://host.docker.internal:$GH_AW_MCP_SCRIPTS_PORT", @@ -1478,6 +1517,20 @@ jobs: } } }, + "playwright": { + "type": "stdio", + "container": "mcr.microsoft.com/playwright/mcp", + "args": ["--init", "--network", "host", "--security-opt", "seccomp=unconfined", "--ipc=host"], + "entrypointArgs": ["--output-dir", "/tmp/gh-aw/mcp-logs/playwright", "--no-sandbox"], + "mounts": ["/tmp/gh-aw/mcp-logs:/tmp/gh-aw/mcp-logs:rw"], + "guard-policies": { + "write-sink": { + "accept": [ + "*" + ] + } + } + }, "safeoutputs": { "type": "http", "url": "http://host.docker.internal:$GH_AW_SAFE_OUTPUTS_PORT", @@ -1491,6 +1544,35 @@ jobs: ] } } + }, + "serena": { + "type": "stdio", + "container": "ghcr.io/github/serena-mcp-server:latest", + "entrypoint": "serena", + "entrypointArgs": [ + "start-mcp-server", + "--context", + "codex", + "--project", + "\${GITHUB_WORKSPACE}" + ], + "mounts": [ + "\${GITHUB_WORKSPACE}:\${GITHUB_WORKSPACE}:rw" + ], + "args": [ + "--network", + "host" + ], + "tools": [ + "*" + ], + "guard-policies": { + "write-sink": { + "accept": [ + "*" + ] + } + } } }, "gateway": { diff --git a/actions/setup/sh/convert_gateway_config_claude.sh b/actions/setup/sh/convert_gateway_config_claude.sh index 926d47065ee..43294aa1e38 100755 --- a/actions/setup/sh/convert_gateway_config_claude.sh +++ b/actions/setup/sh/convert_gateway_config_claude.sh @@ -76,8 +76,9 @@ echo "Target domain: $MCP_GATEWAY_DOMAIN:$MCP_GATEWAY_PORT" # Build the correct URL prefix using the configured domain and port URL_PREFIX="http://${MCP_GATEWAY_DOMAIN}:${MCP_GATEWAY_PORT}" -jq --arg urlPrefix "$URL_PREFIX" ' +jq --arg urlPrefix "$URL_PREFIX" --argjson cliServers "${GH_AW_MCP_CLI_SERVERS:-[]}" ' .mcpServers |= with_entries( + select(.key | IN($cliServers[]) | not) | .value |= ( (.type = "http") | # Fix the URL to use the correct domain diff --git a/actions/setup/sh/convert_gateway_config_codex.sh b/actions/setup/sh/convert_gateway_config_codex.sh index f172c0b206f..9cab58b9d9e 100755 --- a/actions/setup/sh/convert_gateway_config_codex.sh +++ b/actions/setup/sh/convert_gateway_config_codex.sh @@ -84,8 +84,8 @@ persistence = "none" TOML_EOF -jq -r --arg urlPrefix "$URL_PREFIX" ' - .mcpServers | to_entries[] | +jq -r --arg urlPrefix "$URL_PREFIX" --argjson cliServers "${GH_AW_MCP_CLI_SERVERS:-[]}" ' + .mcpServers | to_entries[] | select(.key | IN($cliServers[]) | not) | "[mcp_servers.\(.key)]\n" + "url = \"" + ($urlPrefix + "/mcp/" + .key) + "\"\n" + "http_headers = { Authorization = \"\(.value.headers.Authorization)\" }\n" diff --git a/actions/setup/sh/convert_gateway_config_copilot.sh b/actions/setup/sh/convert_gateway_config_copilot.sh index 5544165dae9..c94e6f9a7bf 100755 --- a/actions/setup/sh/convert_gateway_config_copilot.sh +++ b/actions/setup/sh/convert_gateway_config_copilot.sh @@ -76,8 +76,9 @@ echo "Target domain: $MCP_GATEWAY_DOMAIN:$MCP_GATEWAY_PORT" # Build the correct URL prefix using the configured domain and port URL_PREFIX="http://${MCP_GATEWAY_DOMAIN}:${MCP_GATEWAY_PORT}" -jq --arg urlPrefix "$URL_PREFIX" ' +jq --arg urlPrefix "$URL_PREFIX" --argjson cliServers "${GH_AW_MCP_CLI_SERVERS:-[]}" ' .mcpServers |= with_entries( + select(.key | IN($cliServers[]) | not) | .value |= ( # Add tools field if not present (if .tools then . else . + {"tools": ["*"]} end) | diff --git a/actions/setup/sh/convert_gateway_config_gemini.sh b/actions/setup/sh/convert_gateway_config_gemini.sh index 353060b9c24..046ec3d47a3 100644 --- a/actions/setup/sh/convert_gateway_config_gemini.sh +++ b/actions/setup/sh/convert_gateway_config_gemini.sh @@ -93,8 +93,9 @@ GEMINI_SETTINGS_FILE="${GEMINI_SETTINGS_DIR}/settings.json" mkdir -p "$GEMINI_SETTINGS_DIR" -jq --arg urlPrefix "$URL_PREFIX" ' +jq --arg urlPrefix "$URL_PREFIX" --argjson cliServers "${GH_AW_MCP_CLI_SERVERS:-[]}" ' .mcpServers |= with_entries( + select(.key | IN($cliServers[]) | not) | .value |= ( (del(.type)) | # Fix the URL to use the correct domain diff --git a/actions/setup/sh/start_mcp_gateway.sh b/actions/setup/sh/start_mcp_gateway.sh index 67db98ada72..c5ff7ece713 100755 --- a/actions/setup/sh/start_mcp_gateway.sh +++ b/actions/setup/sh/start_mcp_gateway.sh @@ -403,9 +403,15 @@ case "$ENGINE_TYPE" in *) echo "No agent-specific converter found for engine: $ENGINE_TYPE" echo "Using gateway output directly" - # Default fallback - copy to most common location + # Default fallback - copy to most common location, filtering out CLI-mounted servers mkdir -p /home/runner/.copilot - cp /tmp/gh-aw/mcp-config/gateway-output.json /home/runner/.copilot/mcp-config.json + if [ -n "$GH_AW_MCP_CLI_SERVERS" ]; then + jq --argjson cliServers "$GH_AW_MCP_CLI_SERVERS" \ + '.mcpServers |= with_entries(select(.key | IN($cliServers[]) | not))' \ + /tmp/gh-aw/mcp-config/gateway-output.json > /home/runner/.copilot/mcp-config.json + else + cp /tmp/gh-aw/mcp-config/gateway-output.json /home/runner/.copilot/mcp-config.json + fi cat /home/runner/.copilot/mcp-config.json ;; esac diff --git a/pkg/workflow/mcp_rendering.go b/pkg/workflow/mcp_rendering.go index 30e25d61a1d..60ee999d69f 100644 --- a/pkg/workflow/mcp_rendering.go +++ b/pkg/workflow/mcp_rendering.go @@ -105,42 +105,21 @@ func renderStandardJSONMCPConfig( mcpRenderingLog.Printf("Rendering standard JSON MCP config: config_path=%s tools=%d mcp_tools=%d", configPath, len(tools), len(mcpTools)) createRenderer := buildMCPRendererFactory(workflowData, "json", includeCopilotFields, inlineArgs) - // Compose the engine-specific filter with the CLI-mounted servers filter. - // Servers that are mounted as CLIs should not appear in the MCP gateway config. - composedFilter := composeCLIMountFilter(filterTool, workflowData) + // CLI-mounted servers are NOT excluded from the gateway config. + // The gateway must start their Docker containers so that: + // 1. The CLI manifest (saved by start_mcp_gateway.sh) includes them. + // 2. mount_mcp_as_cli.cjs can query their tool lists and create wrappers. + // Exclusion from the agent's final MCP config happens inside each + // convert_gateway_config_*.sh script via GH_AW_MCP_CLI_SERVERS. return RenderJSONMCPConfig(yaml, tools, mcpTools, workflowData, JSONMCPConfigOptions{ ConfigPath: configPath, GatewayConfig: buildMCPGatewayConfig(workflowData), Renderers: buildStandardJSONMCPRenderers(workflowData, createRenderer, renderCustom), - FilterTool: composedFilter, + FilterTool: filterTool, }) } -// composeCLIMountFilter returns a new filter function that additionally excludes -// any MCP servers that have been mounted as CLI tools (tools.mount-as-clis: true). -// It composes with the existing filter if one is provided. -func composeCLIMountFilter(existing func(string) bool, workflowData *WorkflowData) func(string) bool { - cliServers := getMCPCLIServerNames(workflowData) - if len(cliServers) == 0 { - // Nothing mounted as CLI — return the original filter unchanged - return existing - } - - cliSet := make(map[string]bool, len(cliServers)) - for _, name := range cliServers { - cliSet[name] = true - } - mcpRenderingLog.Printf("Excluding %d CLI-mounted servers from MCP gateway config: %v", len(cliServers), cliServers) - - return func(toolName string) bool { - if cliSet[toolName] { - return false // exclude: mounted as CLI - } - return existing == nil || existing(toolName) - } -} - // buildMCPRendererFactory creates a factory function for MCPConfigRendererUnified instances. // The returned function accepts isLast as a parameter and creates a renderer with engine-specific // options derived from the provided parameters and workflowData at call time. diff --git a/pkg/workflow/mcp_setup_generator.go b/pkg/workflow/mcp_setup_generator.go index 6e691d44fd9..c351c80badb 100644 --- a/pkg/workflow/mcp_setup_generator.go +++ b/pkg/workflow/mcp_setup_generator.go @@ -571,6 +571,17 @@ func (c *Compiler) generateMCPSetup(yaml *strings.Builder, tools map[string]any, // Export engine type yaml.WriteString(" export GH_AW_ENGINE=\"" + engine.GetID() + "\"\n") + // Export the list of CLI-mounted server names (JSON array) so that conversion scripts + // can exclude them from the agent's final MCP config while still letting the gateway + // start their Docker containers (needed to populate the CLI manifest). + if cliServers := getMCPCLIServerNames(workflowData); len(cliServers) > 0 { + quoted := make([]string, len(cliServers)) + for i, s := range cliServers { + quoted[i] = `"` + s + `"` + } + yaml.WriteString(" export GH_AW_MCP_CLI_SERVERS='[" + strings.Join(quoted, ",") + "]'\n") + } + // For Copilot engine with GitHub remote MCP, export GITHUB_PERSONAL_ACCESS_TOKEN // This is needed because the MCP gateway validates ${VAR} references in headers at config load time // and the Copilot MCP config uses ${GITHUB_PERSONAL_ACCESS_TOKEN} in the Authorization header From 8e98c460ab032a92513c1e9e3c3431a65d382293 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 17:16:06 +0000 Subject: [PATCH 08/19] fix: use json.Marshal for GH_AW_MCP_CLI_SERVERS and add jq error handling - Use json.Marshal() instead of manual string concatenation when building the GH_AW_MCP_CLI_SERVERS JSON array export, preventing potential injection via specially-crafted server names. - Add explicit error handling for the jq filter in the default fallback case of start_mcp_gateway.sh: log a warning and fall back to the unfiltered config if jq fails, instead of silently creating an empty or incomplete config file. Agent-Logs-Url: https://github.com/github/gh-aw/sessions/f2adce8a-7104-4ec1-8c1e-2b24cd87eed5 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- actions/setup/sh/start_mcp_gateway.sh | 8 ++++++-- pkg/workflow/mcp_setup_generator.go | 7 +++---- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/actions/setup/sh/start_mcp_gateway.sh b/actions/setup/sh/start_mcp_gateway.sh index c5ff7ece713..85ce2dfdb46 100755 --- a/actions/setup/sh/start_mcp_gateway.sh +++ b/actions/setup/sh/start_mcp_gateway.sh @@ -406,9 +406,13 @@ case "$ENGINE_TYPE" in # Default fallback - copy to most common location, filtering out CLI-mounted servers mkdir -p /home/runner/.copilot if [ -n "$GH_AW_MCP_CLI_SERVERS" ]; then - jq --argjson cliServers "$GH_AW_MCP_CLI_SERVERS" \ + if ! jq --argjson cliServers "$GH_AW_MCP_CLI_SERVERS" \ '.mcpServers |= with_entries(select(.key | IN($cliServers[]) | not))' \ - /tmp/gh-aw/mcp-config/gateway-output.json > /home/runner/.copilot/mcp-config.json + /tmp/gh-aw/mcp-config/gateway-output.json > /home/runner/.copilot/mcp-config.json; then + echo "ERROR: Failed to filter CLI-mounted servers from agent MCP config" + echo "Falling back to unfiltered config" + cp /tmp/gh-aw/mcp-config/gateway-output.json /home/runner/.copilot/mcp-config.json + fi else cp /tmp/gh-aw/mcp-config/gateway-output.json /home/runner/.copilot/mcp-config.json fi diff --git a/pkg/workflow/mcp_setup_generator.go b/pkg/workflow/mcp_setup_generator.go index c351c80badb..98d9934afdd 100644 --- a/pkg/workflow/mcp_setup_generator.go +++ b/pkg/workflow/mcp_setup_generator.go @@ -575,11 +575,10 @@ func (c *Compiler) generateMCPSetup(yaml *strings.Builder, tools map[string]any, // can exclude them from the agent's final MCP config while still letting the gateway // start their Docker containers (needed to populate the CLI manifest). if cliServers := getMCPCLIServerNames(workflowData); len(cliServers) > 0 { - quoted := make([]string, len(cliServers)) - for i, s := range cliServers { - quoted[i] = `"` + s + `"` + cliServersJSON, err := json.Marshal(cliServers) + if err == nil { + yaml.WriteString(" export GH_AW_MCP_CLI_SERVERS='" + string(cliServersJSON) + "'\n") } - yaml.WriteString(" export GH_AW_MCP_CLI_SERVERS='[" + strings.Join(quoted, ",") + "]'\n") } // For Copilot engine with GitHub remote MCP, export GITHUB_PERSONAL_ACCESS_TOKEN From 5a24ced920a991d8924a486c0de4e71c931b047e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 17:45:12 +0000 Subject: [PATCH 09/19] docs: update smoke-copilot prompt to use CLI syntax for mounted MCP servers Tests 1, 3, 4, and 12 now reference the github, serena, and playwright CLI commands (e.g. `github pull_request_read --method list ...`, `serena activate_project --path ...`, `playwright browser_navigate --url ...`) instead of the MCP tool names, consistent with the mount-as-clis: true setting that makes these servers available exclusively via CLI wrappers. Agent-Logs-Url: https://github.com/github/gh-aw/sessions/d8c54181-b858-4299-a4b4-7cc223f4f437 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/smoke-copilot.md b/.github/workflows/smoke-copilot.md index a79604b572c..6e16333731b 100644 --- a/.github/workflows/smoke-copilot.md +++ b/.github/workflows/smoke-copilot.md @@ -126,12 +126,12 @@ strict: false ## Test Requirements -1. **GitHub MCP Testing**: Review the last 2 merged pull requests in ${{ github.repository }} +1. **GitHub CLI Testing**: Use the `github` CLI command to list the last 2 merged pull requests in ${{ github.repository }} (e.g., `github pull_request_read --method list --owner --repo --state closed --per_page 2`) 2. **MCP Scripts GH CLI Testing**: Use the `mcpscripts-gh` tool to query 2 pull requests from ${{ github.repository }} (use args: "pr list --repo ${{ github.repository }} --limit 2 --json number,title,author") -3. **Serena MCP Testing**: - - Use the Serena MCP server tool `activate_project` to initialize the workspace at `${{ github.workspace }}` and verify it succeeds (do NOT use bash to run go commands - use Serena's MCP tools) - - After initialization, use the `find_symbol` tool to search for symbols (find which tool to call) and verify that at least 3 symbols are found in the results -4. **Playwright Testing**: Use the playwright tools to navigate to and verify the page title contains "GitHub" (do NOT try to install playwright - use the provided MCP tools) +3. **Serena CLI Testing**: + - Use the `serena` CLI command `serena activate_project --path ${{ github.workspace }}` to initialize the workspace and verify it succeeds (do NOT use bash to run go commands - use the serena CLI) + - After initialization, use `serena find_symbol --name_path ` to search for symbols and verify that at least 3 symbols are found in the results +4. **Playwright CLI Testing**: Use the `playwright` CLI command (`playwright browser_navigate --url https://github.com`) to navigate to and verify the page title contains "GitHub" (do NOT try to install playwright - use the `playwright` CLI command) 5. **Web Fetch Testing**: Use the web-fetch tool to fetch https://github.com and verify the response contains "GitHub" (do NOT use bash or playwright for this test - use the web-fetch tool directly) 6. **File Writing Testing**: Create a test file `/tmp/gh-aw/agent/smoke-test-copilot-${{ github.run_id }}.txt` with content "Smoke test passed for Copilot at $(date)" (create the directory if it doesn't exist) 7. **Bash Tool Testing**: Execute bash commands to verify file creation was successful (use `cat` to read the file back) @@ -142,7 +142,7 @@ strict: false 9. **Build gh-aw**: Run `GOCACHE=/tmp/go-cache GOMODCACHE=/tmp/go-mod make build` to verify the agent can successfully build the gh-aw project (both caches must be set to /tmp because the default cache locations are not writable). If the command fails, mark this test as ❌ and report the failure. 10. **Discussion Creation Testing**: Use the `create_discussion` safe-output tool to create a discussion in the announcements category titled "copilot was here" with the label "ai-generated" 11. **Workflow Dispatch Testing**: Use the `dispatch_workflow` safe output tool to trigger the `haiku-printer` workflow with a haiku as the message input. Create an original, creative haiku about software testing or automation. -12. **PR Review Testing**: Review the diff of the current pull request. Leave 1-2 inline `create_pull_request_review_comment` comments on specific lines, then call `submit_pull_request_review` with a brief body summarizing your review and event `COMMENT`. To test `reply_to_pull_request_review_comment`: use the `pull_request_read` tool (with `method: "get_review_comments"` and `pullNumber: ${{ github.event.pull_request.number }}`) to fetch the PR's existing review comments, then reply to the most recent one using `reply_to_pull_request_review_comment` with its actual numeric `id` as the `comment_id`. Note: `create_pull_request_review_comment` does not return a `comment_id` — you must fetch existing comment IDs from the GitHub API. If the PR has no existing review comments, skip the reply sub-test. +12. **PR Review Testing**: Review the diff of the current pull request. Leave 1-2 inline `create_pull_request_review_comment` comments on specific lines, then call `submit_pull_request_review` with a brief body summarizing your review and event `COMMENT`. To test `reply_to_pull_request_review_comment`: use the `github` CLI command (`github pull_request_read --method get_review_comments --owner --repo --pullNumber ${{ github.event.pull_request.number }}`) to fetch the PR's existing review comments, then reply to the most recent one using `reply_to_pull_request_review_comment` with its actual numeric `id` as the `comment_id`. Note: `create_pull_request_review_comment` does not return a `comment_id` — you must fetch existing comment IDs via the `github` CLI. If the PR has no existing review comments, skip the reply sub-test. ## Output From 5283e4ad0acec2cf9c78be4a9773fdc6594ed5ec Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 18:16:44 +0000 Subject: [PATCH 10/19] fix: generate MCP CLI scripts in RUNNER_TEMP/gh-aw/mcp-cli/ to be inside AWF mount The AWF sandbox mounts ${RUNNER_TEMP}/gh-aw read-only inside the agent container. CLI wrapper scripts and tools JSON were previously generated in /tmp/gh-aw/mcp-cli/ which is not accessible inside AWF. Move CLI_BIN_DIR and TOOLS_DIR to ${RUNNER_TEMP}/gh-aw/mcp-cli/{bin,tools} using process.env.RUNNER_TEMP so the generated scripts are inside the AWF-mounted directory. MANIFEST_FILE stays at /tmp/gh-aw/mcp-cli/manifest.json since it is only read during the "Mount MCP servers as CLIs" setup step, which runs on the host before AWF starts. Agent-Logs-Url: https://github.com/github/gh-aw/sessions/6766dd5e-4f67-4791-9d47-508e39182e4b Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- actions/setup/js/mount_mcp_as_cli.cjs | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs index 1fb25b4521e..5c74237c50c 100644 --- a/actions/setup/js/mount_mcp_as_cli.cjs +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -6,11 +6,14 @@ * * Mounts MCP servers as local CLI tools by reading the manifest written by * start_mcp_gateway.sh, querying each server for its tool list, and generating - * a standalone bash wrapper script per server in /tmp/gh-aw/mcp-cli/bin/. + * a standalone bash wrapper script per server in ${RUNNER_TEMP}/gh-aw/mcp-cli/bin/. * * The bin directory is locked (chmod 555) so the agent cannot modify or inject * scripts. The directory is added to PATH via core.addPath(). * + * Scripts are placed under ${RUNNER_TEMP}/gh-aw/ (not /tmp/gh-aw/) so they are + * accessible inside the AWF sandbox, which mounts ${RUNNER_TEMP}/gh-aw read-only. + * * Generated CLI wrapper usage: * --help Show all available commands * --help Show help for a specific command @@ -22,8 +25,11 @@ const http = require("http"); const path = require("path"); const MANIFEST_FILE = "/tmp/gh-aw/mcp-cli/manifest.json"; -const CLI_BIN_DIR = "/tmp/gh-aw/mcp-cli/bin"; -const TOOLS_DIR = "/tmp/gh-aw/mcp-cli/tools"; +// Use RUNNER_TEMP so the bin and tools directories are inside the AWF sandbox mount +// (AWF mounts ${RUNNER_TEMP}/gh-aw read-only; /tmp/gh-aw is not accessible inside AWF) +const RUNNER_TEMP = process.env.RUNNER_TEMP || "/home/runner/work/_temp"; +const CLI_BIN_DIR = `${RUNNER_TEMP}/gh-aw/mcp-cli/bin`; +const TOOLS_DIR = `${RUNNER_TEMP}/gh-aw/mcp-cli/tools`; /** MCP servers that are internal infrastructure and should not be user-facing CLIs */ const INTERNAL_SERVERS = new Set(["safeoutputs", "mcp-scripts"]); From 2946954a99f6c726d53a2cf83048d4cdafd8b350 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 18:57:17 +0000 Subject: [PATCH 11/19] fix: address code review feedback on mcp_cli_mount comments and mcpscripts exclusion Agent-Logs-Url: https://github.com/github/gh-aw/sessions/4e66887c-a46e-489f-83bd-7d092d487482 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- actions/setup/js/mount_mcp_as_cli.cjs | 2 +- pkg/parser/schemas/main_workflow_schema.json | 2 +- pkg/workflow/mcp_cli_mount.go | 4 +++- pkg/workflow/tools_types.go | 5 +++-- 4 files changed, 8 insertions(+), 5 deletions(-) diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs index 5c74237c50c..756efd01bcb 100644 --- a/actions/setup/js/mount_mcp_as_cli.cjs +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -32,7 +32,7 @@ const CLI_BIN_DIR = `${RUNNER_TEMP}/gh-aw/mcp-cli/bin`; const TOOLS_DIR = `${RUNNER_TEMP}/gh-aw/mcp-cli/tools`; /** MCP servers that are internal infrastructure and should not be user-facing CLIs */ -const INTERNAL_SERVERS = new Set(["safeoutputs", "mcp-scripts"]); +const INTERNAL_SERVERS = new Set(["safeoutputs", "mcp-scripts", "mcpscripts"]); /** * Make an HTTP POST request with a JSON body and return the parsed response. diff --git a/pkg/parser/schemas/main_workflow_schema.json b/pkg/parser/schemas/main_workflow_schema.json index 8022910e82c..28f404916f5 100644 --- a/pkg/parser/schemas/main_workflow_schema.json +++ b/pkg/parser/schemas/main_workflow_schema.json @@ -4289,7 +4289,7 @@ }, "mount-as-clis": { "type": "boolean", - "description": "When true, each user-facing MCP server is mounted as a standalone CLI tool on PATH. The agent can then call MCP servers via shell commands (e.g. 'github issue_read --method get ...'). Servers that are CLI-mounted are removed from the MCP gateway config. Default: false.", + "description": "When true, each user-facing MCP server is mounted as a standalone CLI tool on PATH. The agent can then call MCP servers via shell commands (e.g. 'github issue_read --method get ...'). CLI-mounted servers remain in the MCP gateway config so their containers can start, and are removed only from the agent's final config during convert_gateway_config_*.sh processing. Default: false.", "examples": [true] } }, diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go index 91f35f0154e..fccdc4ede47 100644 --- a/pkg/workflow/mcp_cli_mount.go +++ b/pkg/workflow/mcp_cli_mount.go @@ -14,15 +14,17 @@ import ( // actions/github-script which: // - Reads the CLI manifest saved by start_mcp_gateway.sh // - Queries each server for its tools/list via JSON-RPC -// - Writes a standalone CLI wrapper script for each server to /tmp/gh-aw/mcp-cli/bin/ +// - Writes a standalone CLI wrapper script for each server to ${RUNNER_TEMP}/gh-aw/mcp-cli/bin/ // - Locks the bin directory (chmod 555) so the agent cannot modify the scripts // - Adds the directory to PATH via core.addPath() // internalMCPServerNames lists the MCP servers that are internal infrastructure and // should not be exposed as user-facing CLI tools. +// Include both config-key and rendered server-ID variants where they differ. var internalMCPServerNames = map[string]bool{ "safeoutputs": true, "mcp-scripts": true, + "mcpscripts": true, } // getMCPCLIServerNames returns the sorted list of MCP server names that will be diff --git a/pkg/workflow/tools_types.go b/pkg/workflow/tools_types.go index a2efd4d14c9..7662721e4e9 100644 --- a/pkg/workflow/tools_types.go +++ b/pkg/workflow/tools_types.go @@ -85,8 +85,9 @@ type ToolsConfig struct { // MountAsCLIs enables mounting MCP servers as standalone CLI tools on PATH. // When true, each user-facing MCP server gets a bash wrapper script placed in - // a read-only directory added to PATH, and those servers are removed from the - // MCP gateway config (so the agent uses the CLI instead of the MCP protocol). + // a read-only directory added to PATH. The servers remain in the MCP gateway + // config, but are filtered out of the agent's final MCP config so the agent + // uses the CLI instead of the MCP protocol. // Default is false. MountAsCLIs bool `yaml:"mount-as-clis,omitempty"` From 85f06a0f1e400774da63afaa19a0b19365425a1a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 19:31:48 +0000 Subject: [PATCH 12/19] fix: bake gateway API key into generated CLI wrapper scripts at generation time Agent-Logs-Url: https://github.com/github/gh-aw/sessions/495e9c7e-99e0-4c62-b70b-a6a626ce60bb Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- actions/setup/js/mount_mcp_as_cli.cjs | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs index 756efd01bcb..0711dbb4f5f 100644 --- a/actions/setup/js/mount_mcp_as_cli.cjs +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -164,15 +164,21 @@ async function fetchMCPTools(serverUrl, apiKey, core) { * to the MCP gateway via curl, following the proper MCP session protocol: * initialize → notifications/initialized → tools/call. * + * The gateway API key is baked directly into the generated script at + * generation time because MCP_GATEWAY_API_KEY is excluded from the AWF + * sandbox environment (--exclude-env MCP_GATEWAY_API_KEY) and would not + * be accessible to the agent at runtime. + * * @param {string} serverName - Name of the MCP server * @param {string} serverUrl - HTTP URL of the MCP server endpoint * @param {string} toolsFile - Path to the cached tools JSON file + * @param {string} apiKey - Gateway API key, baked into the script at generation time * @returns {string} Content of the bash wrapper script */ -function generateCLIWrapperScript(serverName, serverUrl, toolsFile) { +function generateCLIWrapperScript(serverName, serverUrl, toolsFile, apiKey) { // We use a template literal but avoid single quotes in the embedded bash - // to keep the heredoc-free approach clean. The API key is read at runtime - // from the MCP_GATEWAY_API_KEY environment variable. + // to keep the heredoc-free approach clean. The API key is embedded directly + // because MCP_GATEWAY_API_KEY is excluded from the AWF sandbox environment. return `#!/usr/bin/env bash # MCP CLI wrapper for: ${serverName} # Auto-generated by gh-aw. Do not modify. @@ -186,11 +192,9 @@ SERVER_NAME="${serverName}" SERVER_URL="${serverUrl}" TOOLS_FILE="${toolsFile}" -API_KEY="\${MCP_GATEWAY_API_KEY:-}" -if [ -z "\$API_KEY" ]; then - echo "Error: MCP_GATEWAY_API_KEY environment variable is not set" >&2 - exit 1 -fi +# API key is baked in at generation time; MCP_GATEWAY_API_KEY is not available +# inside the AWF sandbox (excluded via --exclude-env MCP_GATEWAY_API_KEY). +API_KEY="${apiKey}" load_tools() { if [ -f "\$TOOLS_FILE" ]; then @@ -391,7 +395,7 @@ async function main() { const apiKey = process.env.MCP_GATEWAY_API_KEY || ""; if (!apiKey) { - core.warning("MCP_GATEWAY_API_KEY is not set; generated CLI wrappers will fail at runtime"); + core.warning("MCP_GATEWAY_API_KEY is not set; generated CLI wrappers will not be able to authenticate with the gateway"); } const mountedServers = []; @@ -416,7 +420,7 @@ async function main() { // Write the CLI wrapper script const scriptPath = path.join(CLI_BIN_DIR, name); try { - fs.writeFileSync(scriptPath, generateCLIWrapperScript(name, url, toolsFile), { mode: 0o755 }); + fs.writeFileSync(scriptPath, generateCLIWrapperScript(name, url, toolsFile, apiKey), { mode: 0o755 }); mountedServers.push(name); core.info(` ✓ Mounted as: ${scriptPath}`); } catch (err) { From 7526d824e3ac25f282b75708b524f3ae345361fe Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 21:16:27 +0000 Subject: [PATCH 13/19] fix: bash syntax error in jq expression and agentic-workflows name mismatch - Fix bash 'unexpected EOF' in generated CLI wrapper: switch the multi-line jq -r expression from double-quoted to single-quoted bash string so that double quotes inside the jq filter don't prematurely close the outer string (mount_mcp_as_cli.cjs:335) - Fix agentic-workflows server ID mismatch: getMCPCLIServerNames now emits 'agenticworkflows' (gateway/manifest ID) instead of 'agentic-workflows' (frontmatter key), so GH_AW_MCP_CLI_SERVERS correctly matches manifest entries and the convert_gateway_config_*.sh filter works (mcp_cli_mount.go:54) Agent-Logs-Url: https://github.com/github/gh-aw/sessions/faa03f79-19e9-4c74-b505-9a9b11fdd786 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 4 ++-- actions/setup/js/mount_mcp_as_cli.cjs | 8 ++++---- pkg/workflow/mcp_cli_mount.go | 8 +++++++- 3 files changed, 13 insertions(+), 7 deletions(-) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 8dae6c2774c..bbafe7d98dd 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -334,7 +334,7 @@ jobs: GH_AW_GITHUB_RUN_ID: ${{ github.run_id }} GH_AW_GITHUB_SERVER_URL: ${{ github.server_url }} GH_AW_GITHUB_WORKSPACE: ${{ github.workspace }} - GH_AW_MCP_CLI_SERVERS_LIST: "- `agentic-workflows` — run `agentic-workflows --help` to see available tools\n- `github` — run `github --help` to see available tools\n- `playwright` — run `playwright --help` to see available tools\n- `serena` — run `serena --help` to see available tools" + GH_AW_MCP_CLI_SERVERS_LIST: "- `agenticworkflows` — run `agenticworkflows --help` to see available tools\n- `github` — run `github --help` to see available tools\n- `playwright` — run `playwright --help` to see available tools\n- `serena` — run `serena --help` to see available tools" GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED: ${{ needs.pre_activation.outputs.activated }} with: script: | @@ -1458,7 +1458,7 @@ jobs: export DEBUG="*" export GH_AW_ENGINE="copilot" - export GH_AW_MCP_CLI_SERVERS='["agentic-workflows","github","playwright","serena"]' + export GH_AW_MCP_CLI_SERVERS='["agenticworkflows","github","playwright","serena"]' export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' mkdir -p /home/runner/.copilot diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs index 0711dbb4f5f..a6982fb73dc 100644 --- a/actions/setup/js/mount_mcp_as_cli.cjs +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -330,11 +330,11 @@ call_tool() { fi if echo "\$response" | jq -e ".result.content" >/dev/null 2>&1; then - echo "\$response" | jq -r ".result.content[] | - if .type == \\"text\\" then .text - elif .type == \\"image\\" then \\"[image data - \(.mimeType // \\"unknown\\")]\\"" + echo "\$response" | jq -r '.result.content[] | + if .type == "text" then .text + elif .type == "image" then "[image data - \(.mimeType // "unknown")]" else (. | tostring) - end" + end' elif echo "\$response" | jq -e ".result" >/dev/null 2>&1; then echo "\$response" | jq -r ".result" else diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go index fccdc4ede47..50113ffc05c 100644 --- a/pkg/workflow/mcp_cli_mount.go +++ b/pkg/workflow/mcp_cli_mount.go @@ -5,6 +5,8 @@ import ( "slices" "sort" "strings" + + "github.com/github/gh-aw/pkg/constants" ) // mcp_cli_mount.go generates a workflow step that mounts MCP servers as local CLI tools @@ -51,8 +53,12 @@ func getMCPCLIServerNames(data *WorkflowData) []string { } // Only include tools that have MCP servers (skip bash, web-fetch, web-search, edit, cache-memory, etc.) switch toolName { - case "github", "playwright", "qmd", "agentic-workflows": + case "github", "playwright", "qmd": servers = append(servers, toolName) + case "agentic-workflows": + // The gateway and manifest use "agenticworkflows" (no hyphen) as the server ID. + // Using the gateway ID here ensures GH_AW_MCP_CLI_SERVERS matches the manifest entries. + servers = append(servers, constants.AgenticWorkflowsMCPServerID.String()) default: // Include custom MCP servers (not in the internal list) if !internalMCPServerNames[toolName] { From efc9b052414eeebc54997c909b5c663503c3a046 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 5 Apr 2026 00:28:46 +0000 Subject: [PATCH 14/19] chore: merge main and recompile all 180 workflows Agent-Logs-Url: https://github.com/github/gh-aw/sessions/a98c75cc-c029-45ac-9667-5d50246c2bb1 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 72 +++++++++++++++--------- 1 file changed, 45 insertions(+), 27 deletions(-) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index c30d30a3e68..9672ca4fe66 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -1,4 +1,4 @@ -# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"a905032d976816465ac3dca3ab19ecdf3acddb929861a5ff5984faffcab585e4","agent_id":"copilot"} +# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"f82d217dd025f94174a3901731feec322e745b01335381df8792e86432db6732","agent_id":"copilot"} # ___ _ _ # / _ \ | | (_) # | |_| | __ _ ___ _ __ | |_ _ ___ @@ -226,9 +226,9 @@ jobs: run: | bash ${RUNNER_TEMP}/gh-aw/actions/create_prompt_first.sh { - cat << 'GH_AW_PROMPT_62c8abf1cc0f53ad_EOF' + cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' - GH_AW_PROMPT_62c8abf1cc0f53ad_EOF + GH_AW_PROMPT_7565ae7829013ae2_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/xpia.md" cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" @@ -236,10 +236,13 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/agentic_workflows_guide.md" cat "${RUNNER_TEMP}/gh-aw/prompts/cache_memory_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_prompt.md" - cat << 'GH_AW_PROMPT_62c8abf1cc0f53ad_EOF' + cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, reply_to_pull_request_review_comment(max:5), add_labels, remove_labels, set_issue_type, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message + GH_AW_PROMPT_7565ae7829013ae2_EOF + cat "${RUNNER_TEMP}/gh-aw/prompts/mcp_cli_tools_prompt.md" + cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -268,9 +271,9 @@ jobs: {{/if}} - GH_AW_PROMPT_62c8abf1cc0f53ad_EOF + GH_AW_PROMPT_7565ae7829013ae2_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/github_mcp_tools_with_safeoutputs_prompt.md" - cat << 'GH_AW_PROMPT_62c8abf1cc0f53ad_EOF' + cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' ## Serena Code Analysis @@ -309,7 +312,7 @@ jobs: {{#runtime-import .github/workflows/shared/github-queries-mcp-script.md}} {{#runtime-import .github/workflows/shared/mcp/serena-go.md}} {{#runtime-import .github/workflows/smoke-copilot.md}} - GH_AW_PROMPT_62c8abf1cc0f53ad_EOF + GH_AW_PROMPT_7565ae7829013ae2_EOF } > "$GH_AW_PROMPT" - name: Interpolate variables and render templates uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 @@ -342,6 +345,7 @@ jobs: GH_AW_GITHUB_RUN_ID: ${{ github.run_id }} GH_AW_GITHUB_SERVER_URL: ${{ github.server_url }} GH_AW_GITHUB_WORKSPACE: ${{ github.workspace }} + GH_AW_MCP_CLI_SERVERS_LIST: "- `agenticworkflows` — run `agenticworkflows --help` to see available tools\n- `github` — run `github --help` to see available tools\n- `playwright` — run `playwright --help` to see available tools\n- `serena` — run `serena --help` to see available tools" GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED: ${{ needs.pre_activation.outputs.activated }} with: script: | @@ -366,6 +370,7 @@ jobs: GH_AW_GITHUB_RUN_ID: process.env.GH_AW_GITHUB_RUN_ID, GH_AW_GITHUB_SERVER_URL: process.env.GH_AW_GITHUB_SERVER_URL, GH_AW_GITHUB_WORKSPACE: process.env.GH_AW_GITHUB_WORKSPACE, + GH_AW_MCP_CLI_SERVERS_LIST: process.env.GH_AW_MCP_CLI_SERVERS_LIST, GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED: process.env.GH_AW_NEEDS_PRE_ACTIVATION_OUTPUTS_ACTIVATED } }); @@ -569,12 +574,12 @@ jobs: mkdir -p ${RUNNER_TEMP}/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/mcp-logs/safeoutputs - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_996bb8e28da5dfb7_EOF' + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_6eb7173ed04ae94b_EOF' {"add_comment":{"allowed_repos":["github/gh-aw"],"hide_older_comments":true,"max":2},"add_labels":{"allowed":["smoke-copilot"],"allowed_repos":["github/gh-aw"]},"create_discussion":{"category":"announcements","close_older_discussions":true,"close_older_key":"smoke-copilot","expires":2,"fallback_to_issue":true,"labels":["ai-generated"],"max":1},"create_issue":{"close_older_issues":true,"close_older_key":"smoke-copilot","expires":2,"group":true,"labels":["automation","testing"],"max":1},"create_pull_request_review_comment":{"max":5,"side":"RIGHT"},"dispatch_workflow":{"max":1,"workflow_files":{"haiku-printer":".yml"},"workflows":["haiku-printer"]},"missing_data":{},"missing_tool":{},"noop":{"max":1,"report-as-issue":"true"},"remove_labels":{"allowed":["smoke"]},"reply_to_pull_request_review_comment":{"max":5},"send-slack-message":{"description":"Send a message to Slack (stub for testing)","inputs":{"message":{"description":"The message to send","required":false,"type":"string"}},"output":"Slack message stub executed!"},"set_issue_type":{},"submit_pull_request_review":{"max":1}} - GH_AW_SAFE_OUTPUTS_CONFIG_996bb8e28da5dfb7_EOF + GH_AW_SAFE_OUTPUTS_CONFIG_6eb7173ed04ae94b_EOF - name: Write Safe Outputs Tools run: | - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/tools_meta.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_META_d4e9fcd31c3eddcb_EOF' + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/tools_meta.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_META_e2e85c0900e38f4f_EOF' { "description_suffixes": { "add_comment": " CONSTRAINTS: Maximum 2 comment(s) can be added.", @@ -632,8 +637,8 @@ jobs: } ] } - GH_AW_SAFE_OUTPUTS_TOOLS_META_d4e9fcd31c3eddcb_EOF - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/validation.json << 'GH_AW_SAFE_OUTPUTS_VALIDATION_7d41b605be50b9cb_EOF' + GH_AW_SAFE_OUTPUTS_TOOLS_META_e2e85c0900e38f4f_EOF + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/validation.json << 'GH_AW_SAFE_OUTPUTS_VALIDATION_a062aab4033aaa78_EOF' { "add_comment": { "defaultMax": 1, @@ -903,7 +908,7 @@ jobs: } } } - GH_AW_SAFE_OUTPUTS_VALIDATION_7d41b605be50b9cb_EOF + GH_AW_SAFE_OUTPUTS_VALIDATION_a062aab4033aaa78_EOF node ${RUNNER_TEMP}/gh-aw/actions/generate_safe_outputs_tools.cjs - name: Generate Safe Outputs MCP Server Config id: safe-outputs-config @@ -948,7 +953,7 @@ jobs: - name: Setup MCP Scripts Config run: | mkdir -p ${RUNNER_TEMP}/gh-aw/mcp-scripts/logs - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/tools.json << 'GH_AW_MCP_SCRIPTS_TOOLS_1e7561d526f43bda_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/tools.json << 'GH_AW_MCP_SCRIPTS_TOOLS_afd637f0ee1feb6d_EOF' { "serverName": "mcpscripts", "version": "1.0.0", @@ -1064,8 +1069,8 @@ jobs: } ] } - GH_AW_MCP_SCRIPTS_TOOLS_1e7561d526f43bda_EOF - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs << 'GH_AW_MCP_SCRIPTS_SERVER_a5255a3a8e9f133e_EOF' + GH_AW_MCP_SCRIPTS_TOOLS_afd637f0ee1feb6d_EOF + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs << 'GH_AW_MCP_SCRIPTS_SERVER_f71949f10c5a2ddd_EOF' const path = require("path"); const { startHttpServer } = require("./mcp_scripts_mcp_server_http.cjs"); const configPath = path.join(__dirname, "tools.json"); @@ -1079,12 +1084,12 @@ jobs: console.error("Failed to start mcp-scripts HTTP server:", error); process.exit(1); }); - GH_AW_MCP_SCRIPTS_SERVER_a5255a3a8e9f133e_EOF + GH_AW_MCP_SCRIPTS_SERVER_f71949f10c5a2ddd_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs - name: Setup MCP Scripts Tool Files run: | - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh << 'GH_AW_MCP_SCRIPTS_SH_GH_ba7386878a21d8cb_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh << 'GH_AW_MCP_SCRIPTS_SH_GH_9624d50956e81089_EOF' #!/bin/bash # Auto-generated mcp-script tool: gh # Execute any gh CLI command. This tool is accessible as 'mcpscripts-gh'. Provide the full command after 'gh' (e.g., args: 'pr list --limit 5'). The tool will run: gh . Use single quotes ' for complex args to avoid shell interpretation issues. @@ -1095,9 +1100,9 @@ jobs: echo " token: ${GH_AW_GH_TOKEN:0:6}..." GH_TOKEN="$GH_AW_GH_TOKEN" gh $INPUT_ARGS - GH_AW_MCP_SCRIPTS_SH_GH_ba7386878a21d8cb_EOF + GH_AW_MCP_SCRIPTS_SH_GH_9624d50956e81089_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_4d7640a4c077e31c_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_80a5b97ded04fa04_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-discussion-query # Query GitHub discussions with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1232,9 +1237,9 @@ jobs: EOF fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_4d7640a4c077e31c_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_80a5b97ded04fa04_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_0641c15ff140ff12_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_6dfee3547bf8c448_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-issue-query # Query GitHub issues with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1313,9 +1318,9 @@ jobs: fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_0641c15ff140ff12_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_6dfee3547bf8c448_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_9ddf10ca0deacae4_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_61af5db195e7768f_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-pr-query # Query GitHub pull requests with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1400,7 +1405,7 @@ jobs: fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_9ddf10ca0deacae4_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_61af5db195e7768f_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh - name: Generate MCP Scripts Server Config @@ -1468,10 +1473,11 @@ jobs: export DEBUG="*" export GH_AW_ENGINE="copilot" + export GH_AW_MCP_CLI_SERVERS='["agenticworkflows","github","playwright","serena"]' export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' mkdir -p /home/runner/.copilot - cat << GH_AW_MCP_CONFIG_c260f8029b966df4_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh + cat << GH_AW_MCP_CONFIG_8a1531c3e333b580_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh { "mcpServers": { "agenticworkflows": { @@ -1591,7 +1597,19 @@ jobs: "payloadDir": "${MCP_GATEWAY_PAYLOAD_DIR}" } } - GH_AW_MCP_CONFIG_c260f8029b966df4_EOF + GH_AW_MCP_CONFIG_8a1531c3e333b580_EOF + - name: Mount MCP servers as CLIs + id: mount-mcp-clis + continue-on-error: true + env: + MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 + with: + script: | + const { setupGlobals } = require('${{ runner.temp }}/gh-aw/actions/setup_globals.cjs'); + setupGlobals(core, github, context, exec, io); + const { main } = require('${{ runner.temp }}/gh-aw/actions/mount_mcp_as_cli.cjs'); + await main(); - name: Download activation artifact uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 with: From 969801665e1bca1028ed001e6d4652a4f5e30780 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 5 Apr 2026 01:56:50 +0000 Subject: [PATCH 15/19] feat: improve mcp-clis prompt clarity and smoke-copilot instructions Agent-Logs-Url: https://github.com/github/gh-aw/sessions/a245a2f9-992b-4519-a089-74cf4b957629 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.md | 26 ++++++++++++++---- actions/setup/md/mcp_cli_tools_prompt.md | 35 ++++++++++++++++++------ 2 files changed, 47 insertions(+), 14 deletions(-) diff --git a/.github/workflows/smoke-copilot.md b/.github/workflows/smoke-copilot.md index 8490151e839..6f481947a9c 100644 --- a/.github/workflows/smoke-copilot.md +++ b/.github/workflows/smoke-copilot.md @@ -128,14 +128,30 @@ observability: **IMPORTANT: Keep all outputs extremely short and concise. Use single-line responses where possible. No verbose explanations.** +## Tool Access Overview + +This workflow uses `mount-as-clis: true`. The following MCP servers are **NOT available as MCP tools** — they are mounted exclusively as **shell CLI commands** (see `` section above). You **must** use them via the `bash` tool: + +- **`github`** — use `github [--param value...]` in bash (e.g. `github pull_request_read --method list ...`) +- **`playwright`** — use `playwright [--param value...]` in bash (e.g. `playwright browser_navigate --url ...`) +- **`serena`** — use `serena [--param value...]` in bash (e.g. `serena activate_project --path ...`) +- **`agenticworkflows`** — use `agenticworkflows [--param value...]` in bash + +Run ` --help` to list all available tools for a server, or ` --help` for detailed parameter info. + +These are **not** MCP protocol tools — they are bash executables. Call them with the `bash` tool only. + ## Test Requirements -1. **GitHub CLI Testing**: Use the `github` CLI command to list the last 2 merged pull requests in ${{ github.repository }} (e.g., `github pull_request_read --method list --owner --repo --state closed --per_page 2`) +1. **GitHub CLI Testing**: Use the `github` CLI command (via bash) to list the last 2 merged pull requests in ${{ github.repository }}: + ```bash + github pull_request_read --method list --owner --repo --state closed --per_page 2 + ``` 2. **MCP Scripts GH CLI Testing**: Use the `mcpscripts-gh` tool to query 2 pull requests from ${{ github.repository }} (use args: "pr list --repo ${{ github.repository }} --limit 2 --json number,title,author") 3. **Serena CLI Testing**: - - Use the `serena` CLI command `serena activate_project --path ${{ github.workspace }}` to initialize the workspace and verify it succeeds (do NOT use bash to run go commands - use the serena CLI) - - After initialization, use `serena find_symbol --name_path ` to search for symbols and verify that at least 3 symbols are found in the results -4. **Playwright CLI Testing**: Use the `playwright` CLI command (`playwright browser_navigate --url https://github.com`) to navigate to and verify the page title contains "GitHub" (do NOT try to install playwright - use the `playwright` CLI command) + - Use bash to run `serena activate_project --path ${{ github.workspace }}` to initialize the workspace and verify it succeeds (do NOT use bash to run go commands - use the serena CLI only) + - After initialization, use bash to run `serena find_symbol --name_path ` to search for symbols and verify that at least 3 symbols are found in the results +4. **Playwright CLI Testing**: Use bash to run `playwright browser_navigate --url https://github.com` to navigate to , then `playwright browser_snapshot` to capture the page and verify the title contains "GitHub" (do NOT try to install playwright - use the `playwright` CLI command via bash only) 5. **Web Fetch Testing**: Use the web-fetch tool to fetch https://github.com and verify the response contains "GitHub" (do NOT use bash or playwright for this test - use the web-fetch tool directly) 6. **File Writing Testing**: Create a test file `/tmp/gh-aw/agent/smoke-test-copilot-${{ github.run_id }}.txt` with content "Smoke test passed for Copilot at $(date)" (create the directory if it doesn't exist) 7. **Bash Tool Testing**: Execute bash commands to verify file creation was successful (use `cat` to read the file back) @@ -146,7 +162,7 @@ observability: 9. **Build gh-aw**: Run `GOCACHE=/tmp/go-cache GOMODCACHE=/tmp/go-mod make build` to verify the agent can successfully build the gh-aw project (both caches must be set to /tmp because the default cache locations are not writable). If the command fails, mark this test as ❌ and report the failure. 10. **Discussion Creation Testing**: Use the `create_discussion` safe-output tool to create a discussion in the announcements category titled "copilot was here" with the label "ai-generated" 11. **Workflow Dispatch Testing**: Use the `dispatch_workflow` safe output tool to trigger the `haiku-printer` workflow with a haiku as the message input. Create an original, creative haiku about software testing or automation. -12. **PR Review Testing**: Review the diff of the current pull request. Leave 1-2 inline `create_pull_request_review_comment` comments on specific lines, then call `submit_pull_request_review` with a brief body summarizing your review and event `COMMENT`. To test `reply_to_pull_request_review_comment`: use the `github` CLI command (`github pull_request_read --method get_review_comments --owner --repo --pullNumber ${{ github.event.pull_request.number }}`) to fetch the PR's existing review comments, then reply to the most recent one using `reply_to_pull_request_review_comment` with its actual numeric `id` as the `comment_id`. Note: `create_pull_request_review_comment` does not return a `comment_id` — you must fetch existing comment IDs via the `github` CLI. If the PR has no existing review comments, skip the reply sub-test. +12. **PR Review Testing**: Review the diff of the current pull request. Leave 1-2 inline `create_pull_request_review_comment` comments on specific lines, then call `submit_pull_request_review` with a brief body summarizing your review and event `COMMENT`. To test `reply_to_pull_request_review_comment`: use bash to run the `github` CLI command (`github pull_request_read --method get_review_comments --owner --repo --pullNumber ${{ github.event.pull_request.number }}`) to fetch the PR's existing review comments, then reply to the most recent one using `reply_to_pull_request_review_comment` with its actual numeric `id` as the `comment_id`. Note: `create_pull_request_review_comment` does not return a `comment_id` — you must fetch existing comment IDs via the `github` CLI. If the PR has no existing review comments, skip the reply sub-test. ## Output diff --git a/actions/setup/md/mcp_cli_tools_prompt.md b/actions/setup/md/mcp_cli_tools_prompt.md index 5b906a9de86..8a9b6b6d5bb 100644 --- a/actions/setup/md/mcp_cli_tools_prompt.md +++ b/actions/setup/md/mcp_cli_tools_prompt.md @@ -1,28 +1,45 @@ -## MCP Tools Available as CLI Commands +## MCP Servers Mounted as Shell CLI Commands -The following MCP servers have been mounted as local CLI commands and are available directly from the shell: +> **IMPORTANT**: The following MCP servers are **NOT available as MCP tools** in your agent context. They have been mounted exclusively as shell (bash) CLI commands. You **must** call them via the shell — do **not** attempt to use them as MCP protocol tools. + +The following servers are available as CLI commands on `PATH`: __GH_AW_MCP_CLI_SERVERS_LIST__ ### How to Use -Each server is a standalone command in your PATH. Use them like any other shell command: +Each server is a standalone executable on your `PATH`. Invoke it from bash like any other shell command: ```bash -# Show all available tools for a server +# Discover what tools a server provides --help -# Show help for a specific tool +# Get detailed help for a specific tool (description + parameters) --help -# Call a tool with parameters +# Call a tool — pass arguments as --name value pairs --param1 value1 --param2 value2 ``` +**Example** — using the `github` CLI: +```bash +github --help # list all github tools +github issue_read --help # show parameters for issue_read +github issue_read --method get --owner octocat --repo Hello-World --issue_number 1 +``` + +**Example** — using the `playwright` CLI: +```bash +playwright --help # list all browser tools +playwright browser_navigate --url https://example.com +playwright browser_snapshot # capture page accessibility tree +``` + ### Notes -- Parameters are passed as `--name value` pairs (all values are treated as strings unless the tool accepts booleans, in which case `--flag` with no value sets it to `true`) -- Results are printed to stdout; errors are printed to stderr -- The CLI scripts are read-only — use MCP tools via the CLI wrappers rather than calling the gateway directly +- All parameters are passed as `--name value` pairs; boolean flags can be set with `--flag` (no value) to mean `true` +- Output is printed to stdout; errors are printed to stderr with a non-zero exit code +- Run the CLI commands inside a `bash` tool call — they are shell executables, not MCP tools +- These CLI commands are read-only and cannot be modified by the agent From 35bf4d2991c0315ada8d2e159f8a8f3d98d86623 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 5 Apr 2026 02:13:45 +0000 Subject: [PATCH 16/19] chore: merge main and recompile all workflows Agent-Logs-Url: https://github.com/github/gh-aw/sessions/1a55ef27-ca9f-4720-9f71-523f61fe293f Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 67 +++++++++++------------- 1 file changed, 31 insertions(+), 36 deletions(-) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 9672ca4fe66..d4469a61580 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -1,4 +1,4 @@ -# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"f82d217dd025f94174a3901731feec322e745b01335381df8792e86432db6732","agent_id":"copilot"} +# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"a351500ae6b2fe9704233bd8fa7e9e656214c7854022682cb391c274c87abf65","agent_id":"copilot"} # ___ _ _ # / _ \ | | (_) # | |_| | __ _ ___ _ __ | |_ _ ___ @@ -30,14 +30,13 @@ # - shared/github-queries-mcp-script.md # - shared/mcp/serena-go.md # - shared/mcp/serena.md +# - shared/observability-otlp.md # - shared/reporting.md # # Secrets used: # - COPILOT_GITHUB_TOKEN # - GH_AW_GITHUB_MCP_SERVER_TOKEN # - GH_AW_GITHUB_TOKEN -# - GH_AW_OTEL_ENDPOINT -# - GH_AW_OTEL_HEADERS # - GITHUB_TOKEN # # Custom actions used: @@ -78,11 +77,6 @@ concurrency: run-name: "Smoke Copilot" -env: - OTEL_EXPORTER_OTLP_ENDPOINT: ${{ secrets.GH_AW_OTEL_ENDPOINT }} - OTEL_SERVICE_NAME: gh-aw - OTEL_EXPORTER_OTLP_HEADERS: ${{ secrets.GH_AW_OTEL_HEADERS }} - jobs: activation: needs: pre_activation @@ -226,9 +220,9 @@ jobs: run: | bash ${RUNNER_TEMP}/gh-aw/actions/create_prompt_first.sh { - cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' + cat << 'GH_AW_PROMPT_caa193c5cfb3b282_EOF' - GH_AW_PROMPT_7565ae7829013ae2_EOF + GH_AW_PROMPT_caa193c5cfb3b282_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/xpia.md" cat "${RUNNER_TEMP}/gh-aw/prompts/temp_folder_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/markdown.md" @@ -236,13 +230,13 @@ jobs: cat "${RUNNER_TEMP}/gh-aw/prompts/agentic_workflows_guide.md" cat "${RUNNER_TEMP}/gh-aw/prompts/cache_memory_prompt.md" cat "${RUNNER_TEMP}/gh-aw/prompts/safe_outputs_prompt.md" - cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' + cat << 'GH_AW_PROMPT_caa193c5cfb3b282_EOF' Tools: add_comment(max:2), create_issue, create_discussion, create_pull_request_review_comment(max:5), submit_pull_request_review, reply_to_pull_request_review_comment(max:5), add_labels, remove_labels, set_issue_type, dispatch_workflow, missing_tool, missing_data, noop, send_slack_message - GH_AW_PROMPT_7565ae7829013ae2_EOF + GH_AW_PROMPT_caa193c5cfb3b282_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/mcp_cli_tools_prompt.md" - cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' + cat << 'GH_AW_PROMPT_caa193c5cfb3b282_EOF' The following GitHub context information is available for this workflow: {{#if __GH_AW_GITHUB_ACTOR__ }} @@ -271,9 +265,9 @@ jobs: {{/if}} - GH_AW_PROMPT_7565ae7829013ae2_EOF + GH_AW_PROMPT_caa193c5cfb3b282_EOF cat "${RUNNER_TEMP}/gh-aw/prompts/github_mcp_tools_with_safeoutputs_prompt.md" - cat << 'GH_AW_PROMPT_7565ae7829013ae2_EOF' + cat << 'GH_AW_PROMPT_caa193c5cfb3b282_EOF' ## Serena Code Analysis @@ -311,8 +305,9 @@ jobs: {{#runtime-import .github/workflows/shared/reporting.md}} {{#runtime-import .github/workflows/shared/github-queries-mcp-script.md}} {{#runtime-import .github/workflows/shared/mcp/serena-go.md}} + {{#runtime-import .github/workflows/shared/observability-otlp.md}} {{#runtime-import .github/workflows/smoke-copilot.md}} - GH_AW_PROMPT_7565ae7829013ae2_EOF + GH_AW_PROMPT_caa193c5cfb3b282_EOF } > "$GH_AW_PROMPT" - name: Interpolate variables and render templates uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 @@ -574,12 +569,12 @@ jobs: mkdir -p ${RUNNER_TEMP}/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/safeoutputs mkdir -p /tmp/gh-aw/mcp-logs/safeoutputs - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_6eb7173ed04ae94b_EOF' + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/config.json << 'GH_AW_SAFE_OUTPUTS_CONFIG_6351b36318a2ecfb_EOF' {"add_comment":{"allowed_repos":["github/gh-aw"],"hide_older_comments":true,"max":2},"add_labels":{"allowed":["smoke-copilot"],"allowed_repos":["github/gh-aw"]},"create_discussion":{"category":"announcements","close_older_discussions":true,"close_older_key":"smoke-copilot","expires":2,"fallback_to_issue":true,"labels":["ai-generated"],"max":1},"create_issue":{"close_older_issues":true,"close_older_key":"smoke-copilot","expires":2,"group":true,"labels":["automation","testing"],"max":1},"create_pull_request_review_comment":{"max":5,"side":"RIGHT"},"dispatch_workflow":{"max":1,"workflow_files":{"haiku-printer":".yml"},"workflows":["haiku-printer"]},"missing_data":{},"missing_tool":{},"noop":{"max":1,"report-as-issue":"true"},"remove_labels":{"allowed":["smoke"]},"reply_to_pull_request_review_comment":{"max":5},"send-slack-message":{"description":"Send a message to Slack (stub for testing)","inputs":{"message":{"description":"The message to send","required":false,"type":"string"}},"output":"Slack message stub executed!"},"set_issue_type":{},"submit_pull_request_review":{"max":1}} - GH_AW_SAFE_OUTPUTS_CONFIG_6eb7173ed04ae94b_EOF + GH_AW_SAFE_OUTPUTS_CONFIG_6351b36318a2ecfb_EOF - name: Write Safe Outputs Tools run: | - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/tools_meta.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_META_e2e85c0900e38f4f_EOF' + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/tools_meta.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_META_753e8d4c202f9446_EOF' { "description_suffixes": { "add_comment": " CONSTRAINTS: Maximum 2 comment(s) can be added.", @@ -637,8 +632,8 @@ jobs: } ] } - GH_AW_SAFE_OUTPUTS_TOOLS_META_e2e85c0900e38f4f_EOF - cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/validation.json << 'GH_AW_SAFE_OUTPUTS_VALIDATION_a062aab4033aaa78_EOF' + GH_AW_SAFE_OUTPUTS_TOOLS_META_753e8d4c202f9446_EOF + cat > ${RUNNER_TEMP}/gh-aw/safeoutputs/validation.json << 'GH_AW_SAFE_OUTPUTS_VALIDATION_d2a901799ebcae84_EOF' { "add_comment": { "defaultMax": 1, @@ -908,7 +903,7 @@ jobs: } } } - GH_AW_SAFE_OUTPUTS_VALIDATION_a062aab4033aaa78_EOF + GH_AW_SAFE_OUTPUTS_VALIDATION_d2a901799ebcae84_EOF node ${RUNNER_TEMP}/gh-aw/actions/generate_safe_outputs_tools.cjs - name: Generate Safe Outputs MCP Server Config id: safe-outputs-config @@ -953,7 +948,7 @@ jobs: - name: Setup MCP Scripts Config run: | mkdir -p ${RUNNER_TEMP}/gh-aw/mcp-scripts/logs - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/tools.json << 'GH_AW_MCP_SCRIPTS_TOOLS_afd637f0ee1feb6d_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/tools.json << 'GH_AW_MCP_SCRIPTS_TOOLS_93b95a6fab4cbabc_EOF' { "serverName": "mcpscripts", "version": "1.0.0", @@ -1069,8 +1064,8 @@ jobs: } ] } - GH_AW_MCP_SCRIPTS_TOOLS_afd637f0ee1feb6d_EOF - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs << 'GH_AW_MCP_SCRIPTS_SERVER_f71949f10c5a2ddd_EOF' + GH_AW_MCP_SCRIPTS_TOOLS_93b95a6fab4cbabc_EOF + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs << 'GH_AW_MCP_SCRIPTS_SERVER_e059f8505a05caf9_EOF' const path = require("path"); const { startHttpServer } = require("./mcp_scripts_mcp_server_http.cjs"); const configPath = path.join(__dirname, "tools.json"); @@ -1084,12 +1079,12 @@ jobs: console.error("Failed to start mcp-scripts HTTP server:", error); process.exit(1); }); - GH_AW_MCP_SCRIPTS_SERVER_f71949f10c5a2ddd_EOF + GH_AW_MCP_SCRIPTS_SERVER_e059f8505a05caf9_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/mcp-server.cjs - name: Setup MCP Scripts Tool Files run: | - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh << 'GH_AW_MCP_SCRIPTS_SH_GH_9624d50956e81089_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh << 'GH_AW_MCP_SCRIPTS_SH_GH_14542eaa70e08c01_EOF' #!/bin/bash # Auto-generated mcp-script tool: gh # Execute any gh CLI command. This tool is accessible as 'mcpscripts-gh'. Provide the full command after 'gh' (e.g., args: 'pr list --limit 5'). The tool will run: gh . Use single quotes ' for complex args to avoid shell interpretation issues. @@ -1100,9 +1095,9 @@ jobs: echo " token: ${GH_AW_GH_TOKEN:0:6}..." GH_TOKEN="$GH_AW_GH_TOKEN" gh $INPUT_ARGS - GH_AW_MCP_SCRIPTS_SH_GH_9624d50956e81089_EOF + GH_AW_MCP_SCRIPTS_SH_GH_14542eaa70e08c01_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/gh.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_80a5b97ded04fa04_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_968756eb1dee064f_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-discussion-query # Query GitHub discussions with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1237,9 +1232,9 @@ jobs: EOF fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_80a5b97ded04fa04_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-DISCUSSION-QUERY_968756eb1dee064f_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-discussion-query.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_6dfee3547bf8c448_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_78f5b8f780edb3ad_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-issue-query # Query GitHub issues with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1318,9 +1313,9 @@ jobs: fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_6dfee3547bf8c448_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-ISSUE-QUERY_78f5b8f780edb3ad_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-issue-query.sh - cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_61af5db195e7768f_EOF' + cat > ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh << 'GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_65f8bee389f4452e_EOF' #!/bin/bash # Auto-generated mcp-script tool: github-pr-query # Query GitHub pull requests with jq filtering support. Without --jq, returns schema and data size info. Use --jq '.' to get all data, or specific jq expressions to filter. @@ -1405,7 +1400,7 @@ jobs: fi - GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_61af5db195e7768f_EOF + GH_AW_MCP_SCRIPTS_SH_GITHUB-PR-QUERY_65f8bee389f4452e_EOF chmod +x ${RUNNER_TEMP}/gh-aw/mcp-scripts/github-pr-query.sh - name: Generate MCP Scripts Server Config @@ -1477,7 +1472,7 @@ jobs: export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' mkdir -p /home/runner/.copilot - cat << GH_AW_MCP_CONFIG_8a1531c3e333b580_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh + cat << GH_AW_MCP_CONFIG_16cd234ad530a74b_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh { "mcpServers": { "agenticworkflows": { @@ -1597,7 +1592,7 @@ jobs: "payloadDir": "${MCP_GATEWAY_PAYLOAD_DIR}" } } - GH_AW_MCP_CONFIG_8a1531c3e333b580_EOF + GH_AW_MCP_CONFIG_16cd234ad530a74b_EOF - name: Mount MCP servers as CLIs id: mount-mcp-clis continue-on-error: true From acd44a62ae564202e1d064a0381510473c036ae3 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 5 Apr 2026 03:07:34 +0000 Subject: [PATCH 17/19] fix: pass container-accessible gateway URL to CLI wrapper scripts The manifest saved by start_mcp_gateway.sh stores raw gateway-output URLs (e.g., http://0.0.0.0:80/mcp/server) that work from the host. CLI wrapper scripts generated by mount_mcp_as_cli.cjs baked these URLs in directly, so when the agent inside the AWF sandbox ran e.g. `github pull_request_read ...`, the wrapper's curl call to 0.0.0.0:80 failed because that address is not routable inside the container. Fix: - start_mcp_gateway.sh: output gateway-domain alongside gateway-port - mcp_cli_mount.go: mount step now receives MCP_GATEWAY_DOMAIN and MCP_GATEWAY_PORT from gateway step outputs - mount_mcp_as_cli.cjs: added toContainerUrl() that rewrites raw manifest URLs to use MCP_GATEWAY_DOMAIN:MCP_GATEWAY_PORT; tool fetching still uses the host-accessible URL, but generateCLI WrapperScript receives the container-accessible rewritten URL; warns if env vars are absent so misconfiguration is diagnosable Recompiled all 180 workflows. Agent-Logs-Url: https://github.com/github/gh-aw/sessions/6e5597e6-b5e4-4bc7-914a-9d913b80dba9 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 2 ++ actions/setup/js/mount_mcp_as_cli.cjs | 37 +++++++++++++++++++++--- actions/setup/sh/start_mcp_gateway.sh | 1 + pkg/workflow/mcp_cli_mount.go | 2 ++ 4 files changed, 38 insertions(+), 4 deletions(-) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index d4469a61580..6f4bf6e9d15 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -1598,6 +1598,8 @@ jobs: continue-on-error: true env: MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }} + MCP_GATEWAY_DOMAIN: ${{ steps.start-mcp-gateway.outputs.gateway-domain }} + MCP_GATEWAY_PORT: ${{ steps.start-mcp-gateway.outputs.gateway-port }} uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8 with: script: | diff --git a/actions/setup/js/mount_mcp_as_cli.cjs b/actions/setup/js/mount_mcp_as_cli.cjs index a6982fb73dc..9ea08b9ecf2 100644 --- a/actions/setup/js/mount_mcp_as_cli.cjs +++ b/actions/setup/js/mount_mcp_as_cli.cjs @@ -34,6 +34,25 @@ const TOOLS_DIR = `${RUNNER_TEMP}/gh-aw/mcp-cli/tools`; /** MCP servers that are internal infrastructure and should not be user-facing CLIs */ const INTERNAL_SERVERS = new Set(["safeoutputs", "mcp-scripts", "mcpscripts"]); +/** + * Rewrite a raw gateway manifest URL to use the container-accessible domain. + * + * The manifest stores raw gateway-output URLs (e.g., http://0.0.0.0:80/mcp/server) + * that work from the host. Inside the AWF sandbox the gateway is reachable via + * MCP_GATEWAY_DOMAIN:MCP_GATEWAY_PORT (typically host.docker.internal:80). + * + * @param {string} rawUrl - URL from the manifest (host-accessible) + * @returns {string} URL suitable for use inside AWF containers + */ +function toContainerUrl(rawUrl) { + const domain = process.env.MCP_GATEWAY_DOMAIN; + const port = process.env.MCP_GATEWAY_PORT; + if (domain && port) { + return rawUrl.replace(/^https?:\/\/[^/]+\/mcp\//, `http://${domain}:${port}/mcp/`); + } + return rawUrl; +} + /** * Make an HTTP POST request with a JSON body and return the parsed response. * @@ -398,15 +417,25 @@ async function main() { core.warning("MCP_GATEWAY_API_KEY is not set; generated CLI wrappers will not be able to authenticate with the gateway"); } + const gatewayDomain = process.env.MCP_GATEWAY_DOMAIN || ""; + const gatewayPort = process.env.MCP_GATEWAY_PORT || ""; + if (!gatewayDomain || !gatewayPort) { + core.warning("MCP_GATEWAY_DOMAIN or MCP_GATEWAY_PORT is not set; CLI wrappers will use raw manifest URLs which may not be reachable inside the AWF sandbox"); + } + const mountedServers = []; for (const server of servers) { const { name, url } = server; - core.info(`Mounting MCP server '${name}' (url: ${url})...`); + // The manifest URL is the host-accessible raw gateway address (e.g., http://0.0.0.0:80/mcp/server). + // Rewrite it to the container-accessible URL for the generated CLI wrapper scripts, + // which run inside the AWF sandbox where the gateway is reached via MCP_GATEWAY_DOMAIN. + const containerUrl = toContainerUrl(url); + core.info(`Mounting MCP server '${name}' (host url: ${url}, container url: ${containerUrl})...`); const toolsFile = path.join(TOOLS_DIR, `${name}.json`); - // Query tools from the server + // Query tools from the server using the host-accessible URL (mount step runs on host) const tools = await fetchMCPTools(url, apiKey, core); core.info(` Found ${tools.length} tool(s)`); @@ -417,10 +446,10 @@ async function main() { core.warning(` Failed to write tools cache for ${name}: ${err instanceof Error ? err.message : String(err)}`); } - // Write the CLI wrapper script + // Write the CLI wrapper script using the container-accessible URL const scriptPath = path.join(CLI_BIN_DIR, name); try { - fs.writeFileSync(scriptPath, generateCLIWrapperScript(name, url, toolsFile, apiKey), { mode: 0o755 }); + fs.writeFileSync(scriptPath, generateCLIWrapperScript(name, containerUrl, toolsFile, apiKey), { mode: 0o755 }); mountedServers.push(name); core.info(` ✓ Mounted as: ${scriptPath}`); } catch (err) { diff --git a/actions/setup/sh/start_mcp_gateway.sh b/actions/setup/sh/start_mcp_gateway.sh index 85ce2dfdb46..0132dd891ae 100755 --- a/actions/setup/sh/start_mcp_gateway.sh +++ b/actions/setup/sh/start_mcp_gateway.sh @@ -488,4 +488,5 @@ echo "" echo "gateway-pid=$GATEWAY_PID" echo "gateway-port=${MCP_GATEWAY_PORT}" echo "gateway-api-key=${MCP_GATEWAY_API_KEY}" + echo "gateway-domain=${MCP_GATEWAY_DOMAIN}" } >> "$GITHUB_OUTPUT" diff --git a/pkg/workflow/mcp_cli_mount.go b/pkg/workflow/mcp_cli_mount.go index 50113ffc05c..d5bd367acb4 100644 --- a/pkg/workflow/mcp_cli_mount.go +++ b/pkg/workflow/mcp_cli_mount.go @@ -98,6 +98,8 @@ func (c *Compiler) generateMCPCLIMountStep(yaml *strings.Builder, data *Workflow yaml.WriteString(" continue-on-error: true\n") yaml.WriteString(" env:\n") yaml.WriteString(" MCP_GATEWAY_API_KEY: ${{ steps.start-mcp-gateway.outputs.gateway-api-key }}\n") + yaml.WriteString(" MCP_GATEWAY_DOMAIN: ${{ steps.start-mcp-gateway.outputs.gateway-domain }}\n") + yaml.WriteString(" MCP_GATEWAY_PORT: ${{ steps.start-mcp-gateway.outputs.gateway-port }}\n") fmt.Fprintf(yaml, " uses: %s\n", GetActionPin("actions/github-script")) yaml.WriteString(" with:\n") yaml.WriteString(" script: |\n") From 3214e781e0c082683e6d44d0ebabc8676bcba676 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 5 Apr 2026 09:00:59 +0000 Subject: [PATCH 18/19] fix: persist GH_AW_MCP_CLI_SERVERS to GITHUB_ENV so conversion scripts can filter CLIs Agent-Logs-Url: https://github.com/github/gh-aw/sessions/df695c39-da3e-46c3-af36-1af81c84fa29 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 1 + pkg/workflow/mcp_setup_generator.go | 4 ++++ 2 files changed, 5 insertions(+) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index 6f4bf6e9d15..fe963f4382e 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -1469,6 +1469,7 @@ jobs: export GH_AW_ENGINE="copilot" export GH_AW_MCP_CLI_SERVERS='["agenticworkflows","github","playwright","serena"]' + echo 'GH_AW_MCP_CLI_SERVERS=["agenticworkflows","github","playwright","serena"]' >> "$GITHUB_ENV" export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' mkdir -p /home/runner/.copilot diff --git a/pkg/workflow/mcp_setup_generator.go b/pkg/workflow/mcp_setup_generator.go index 98d9934afdd..59622d1cc87 100644 --- a/pkg/workflow/mcp_setup_generator.go +++ b/pkg/workflow/mcp_setup_generator.go @@ -574,10 +574,14 @@ func (c *Compiler) generateMCPSetup(yaml *strings.Builder, tools map[string]any, // Export the list of CLI-mounted server names (JSON array) so that conversion scripts // can exclude them from the agent's final MCP config while still letting the gateway // start their Docker containers (needed to populate the CLI manifest). + // The variable must be persisted to $GITHUB_ENV (not just exported) because + // convert_gateway_config_*.sh runs in a subsequent step and would otherwise see an + // empty variable, causing no servers to be filtered from the agent's MCP config. if cliServers := getMCPCLIServerNames(workflowData); len(cliServers) > 0 { cliServersJSON, err := json.Marshal(cliServers) if err == nil { yaml.WriteString(" export GH_AW_MCP_CLI_SERVERS='" + string(cliServersJSON) + "'\n") + yaml.WriteString(" echo 'GH_AW_MCP_CLI_SERVERS=" + string(cliServersJSON) + "' >> \"$GITHUB_ENV\"\n") } } From 81db7faf21847b8f5d7e7db15281c8997e8a40b2 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 5 Apr 2026 15:05:40 +0000 Subject: [PATCH 19/19] chore: merge main and recompile 181 workflows Agent-Logs-Url: https://github.com/github/gh-aw/sessions/1d35fa17-1b02-4f55-85f0-9c17d491b2bd Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/smoke-copilot.lock.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/smoke-copilot.lock.yml b/.github/workflows/smoke-copilot.lock.yml index fe963f4382e..c2571f82ea2 100644 --- a/.github/workflows/smoke-copilot.lock.yml +++ b/.github/workflows/smoke-copilot.lock.yml @@ -387,6 +387,8 @@ jobs: path: | /tmp/gh-aw/aw_info.json /tmp/gh-aw/aw-prompts/prompt.txt + /tmp/gh-aw/github_rate_limits.jsonl + if-no-files-found: ignore retention-days: 1 agent: @@ -539,7 +541,7 @@ jobs: GH_AW_APPROVAL_LABELS_VAR: ${{ vars.GH_AW_GITHUB_APPROVAL_LABELS || '' }} run: bash ${RUNNER_TEMP}/gh-aw/actions/parse_guard_list.sh - name: Download container images - run: bash ${RUNNER_TEMP}/gh-aw/actions/download_docker_images.sh ghcr.io/github/gh-aw-firewall/agent:0.25.13 ghcr.io/github/gh-aw-firewall/api-proxy:0.25.13 ghcr.io/github/gh-aw-firewall/squid:0.25.13 ghcr.io/github/gh-aw-mcpg:v0.2.12 ghcr.io/github/github-mcp-server:v0.32.0 ghcr.io/github/serena-mcp-server:latest mcr.microsoft.com/playwright/mcp node:lts-alpine + run: bash ${RUNNER_TEMP}/gh-aw/actions/download_docker_images.sh ghcr.io/github/gh-aw-firewall/agent:0.25.13 ghcr.io/github/gh-aw-firewall/api-proxy:0.25.13 ghcr.io/github/gh-aw-firewall/squid:0.25.13 ghcr.io/github/gh-aw-mcpg:v0.2.14 ghcr.io/github/github-mcp-server:v0.32.0 ghcr.io/github/serena-mcp-server:latest mcr.microsoft.com/playwright/mcp node:lts-alpine - name: Install gh-aw extension env: GH_TOKEN: ${{ secrets.GH_AW_GITHUB_MCP_SERVER_TOKEN || secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }} @@ -1470,7 +1472,7 @@ jobs: export GH_AW_ENGINE="copilot" export GH_AW_MCP_CLI_SERVERS='["agenticworkflows","github","playwright","serena"]' echo 'GH_AW_MCP_CLI_SERVERS=["agenticworkflows","github","playwright","serena"]' >> "$GITHUB_ENV" - export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.12' + export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_MCP_SCRIPTS_PORT -e GH_AW_MCP_SCRIPTS_API_KEY -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -e GH_AW_GH_TOKEN -e GH_DEBUG -e GH_TOKEN -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.14' mkdir -p /home/runner/.copilot cat << GH_AW_MCP_CONFIG_16cd234ad530a74b_EOF | bash ${RUNNER_TEMP}/gh-aw/actions/start_mcp_gateway.sh @@ -1810,6 +1812,7 @@ jobs: /tmp/gh-aw/agent_usage.json /tmp/gh-aw/agent-stdio.log /tmp/gh-aw/agent/ + /tmp/gh-aw/github_rate_limits.jsonl /tmp/gh-aw/safeoutputs.jsonl /tmp/gh-aw/agent_output.json /tmp/gh-aw/aw-*.patch