MCP Server
The gh aw mcp-server command exposes gh aw CLI tools (status, compile, logs, audit, mcp-inspect) to AI agents through the Model Context Protocol, enabling agents to check workflow status, compile workflows, download logs, investigate failures, and inspect MCP servers.
Start the server for local CLI usage:
gh aw mcp-serverOr configure in for any host:
command: ghargs: [aw, mcp-server]Configuration Options
Section titled “Configuration Options”Using a Custom Command Path
Section titled “Using a Custom Command Path”Use the --cmd flag to specify a custom path to the gh-aw binary instead of using the default gh aw command:
gh aw mcp-server --cmd ./gh-awUse this for local development builds, CI/CD workflows with specific versions, or environments without the gh CLI extension.
Example in an agentic workflow:
steps: - name: Build gh-aw run: make build - name: Start MCP server run: | set -e ./gh-aw mcp-server --cmd ./gh-aw --port 8765 & MCP_PID=$! sleep 2 if ! kill -0 $MCP_PID 2>/dev/null; then echo "MCP server failed to start" exit 1 fiHTTP Server Mode
Section titled “HTTP Server Mode”Use the --port flag to run the server with HTTP/SSE transport instead of stdio:
gh aw mcp-server --port 8080Configuring with Copilot CLI
Section titled “Configuring with Copilot CLI”The GitHub Copilot CLI can use the gh-aw MCP server to access workflow management tools.
Use the /mcp command in Copilot CLI to add the MCP server:
/mcp add github-agentic-workflows gh aw mcp-serverThis registers the server with Copilot CLI, making workflow management tools available in your terminal sessions.
Configuring with VS Code
Section titled “Configuring with VS Code”VS Code can use the gh-aw MCP server through the Copilot Chat extension.
Create or update .vscode/mcp.json in your repository:
{ "servers": { "github-agentic-workflows": { "command": "gh", "args": ["aw", "mcp-server"], "cwd": "${workspaceFolder}" } }}After adding the configuration, reload VS Code or restart the Copilot Chat extension.
Available Tools
Section titled “Available Tools”The MCP server provides status (list workflows with pattern filter), compile (generate GitHub Actions YAML), logs (download with timeout handling and continuation), audit (generate report to /tmp/gh-aw/aw-mcp/logs), and mcp-inspect (inspect servers and validate secrets).
Logs Tool Features
Section titled “Logs Tool Features”Timeout and Continuation:
The logs tool uses a 50-second default timeout to prevent MCP server timeouts when downloading large workflow runs. When a timeout occurs, the tool returns partial results with a continuation field containing parameters to resume fetching:
{ "summary": { "total_runs": 5 }, "runs": [ ... ], "continuation": { "message": "Timeout reached. Use these parameters to continue fetching more logs.", "workflow_name": "weekly-research", "count": 100, "before_run_id": 12341, "timeout": 50 }}Agents can detect incomplete data by checking for the continuation field and make follow-up calls with the provided before_run_id to fetch remaining logs.
Large Output Handling:
When tool outputs exceed 16,000 tokens (~64KB), the MCP server automatically writes content to /tmp/gh-aw/safe-outputs/ and returns a JSON response with file location and schema description:
{ "filename": "bb28168fe5604623b804546db0e8c90eaf9e8dcd0f418761787d5159198b4fd8.json", "description": "[{id, name, data}] (2000 items)"}Schema descriptions format: JSON arrays as [{key1, key2}] (N items), objects as {key1, key2, ...} (N keys), and text as text content.
Example Prompt
Section titled “Example Prompt”Check all workflows: use `status` to list workflows, `logs` for recent runs, `audit` for failures, then generate a summary report.Using as Agentic Workflows Tool
Section titled “Using as Agentic Workflows Tool”The MCP server is available as a builtin tool called agentic-workflows in agentic workflows:
---tools: agentic-workflows: # Enables status, compile, logs, audit, and mcp-inspect tools---
Check workflow status, inspect MCP servers, download recent logs, and audit any failures.