Add 'add' tool to mcp-server command

[Copilot]

This PR adds the add tool to the MCP server command, allowing users to add workflows from remote repositories through the MCP protocol.

Changes Made

1. Added add tool to MCP server (pkg/cli/mcp_server.go):

   • Created addArgs struct with minimal parameters: workflows (required), number, and name
   • Implemented tool handler that calls the add CLI command with appropriate arguments
   • Added concise description matching the style of other MCP server tools: "Add workflows from remote repositories to .github/workflows"
   • Updated command documentation to list the new add tool

2. Updated existing tests (pkg/cli/mcp_server_test.go):

   • Updated TestMCPServer_ListTools to include add in the expected tools list

3. Added new integration tests (pkg/cli/mcp_server_add_test.go):

   • TestMCPServer_AddTool: Verifies the add tool is exposed with proper description
   • TestMCPServer_AddToolInvocation: Tests actual tool invocation with workflows parameter
   • Tests error handling when required parameters are missing

Tool Parameters

The add tool supports the following minimal parameters:

• workflows (required): Array of workflow specifications to add (e.g., 'owner/repo/workflow-name' or 'owner/repo/workflow-name@version')
• number: Create multiple numbered copies (corresponds to -c flag)
• name: Specify custom name for the workflow (corresponds to -n flag)

Testing

• ✅ Unit tests: make test-unit
• ✅ Integration tests: TestMCPServer_AddTool
• ✅ Linting: make lint
• ✅ Formatting: make fmt
• ✅ Security: CodeQL scan (no issues found)

The tool is fully functional and follows the same patterns as other tools in the MCP server (status, compile, logs, audit, mcp-inspect).

Original prompt

Add tool to "mcp-server" command that wraps the "add" command.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pelikhan]

@copilot continue working

[Copilot]

@copilot continue working

Completed! Added the add tool to the mcp-server command in commit 17273fb.

The tool wraps the gh aw add command and supports all major parameters:

• workflows (required): Array of workflow specifications to add
• number: Create multiple numbered copies (corresponds to -c flag)
• name: Custom workflow name (corresponds to -n flag)
• engine: Override AI engine (corresponds to -a flag)
• force: Overwrite existing files
• append: Append content to workflow
• verbose: Enable verbose output

All tests pass and no security issues were found. The tool is listed in the help text and available via MCP protocol.

[pelikhan]

@copilot remove text

[Copilot]

Removed verbose description text in commit 591d7b9. The tool description is now concise and matches the style of other MCP server tools: "Add workflows from remote repositories to .github/workflows"

[pelikhan]

@copilot remove force, verbose, append arguments from tool signature

[Copilot]

@copilot remove force, verbose, append arguments from tool signature

Removed force, verbose, and append arguments in commit 96f7970. The add tool now only accepts essential parameters: workflows (required), number, name, and engine.

[pelikhan]

@copilot remove "engine" argument from tool as well

[Copilot]

@copilot remove "engine" argument from tool as well

Removed engine argument in commit e0014d9. The add tool now only accepts: workflows (required), number, and name.

[Copilot]

Pull Request Overview

This PR adds MCP server support for the add command, enabling AI agents to add workflows from remote repositories through the Model Context Protocol.

Key changes:

• Adds new "add" tool to the MCP server that wraps the CLI add command
• Implements basic parameter support for workflows, number of copies, and custom naming
• Includes comprehensive integration tests to verify tool exposure and invocation
• Updates the expected tools list in existing tests

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
pkg/cli/mcp_server.go	Adds the "add" tool to MCP server with argument handling and command execution wrapper
pkg/cli/mcp_server_add_test.go	New integration tests verifying the add tool is properly exposed and functional via MCP
pkg/cli/mcp_server_test.go	Updates expected tools list to include the new "add" tool
.github/workflows/go.mod	Minor formatting cleanup (removes empty require block, reorders go version)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The MCP add tool is missing support for several important CLI flags that are available in the add command:

• --engine/-a - Override AI engine (claude, codex, copilot, custom)
• --pr - Create a pull request with the workflow changes
• --force - Overwrite existing workflow files
• --append - Append extra content to the end of agentic workflow on installation
• --no-gitattributes - Skip updating .gitattributes file

These flags provide important functionality that MCP users may need, particularly --pr and --force which are commonly used. Consider adding these as optional parameters in the addArgs struct to provide feature parity with the CLI command.

[Copilot]

The tool description is too brief and doesn't provide enough context for AI agents using this tool. Following the pattern from other tools in this file (e.g., status, logs, mcp-inspect), the description should include:

• Examples of workflow specifications (e.g., "owner/repo/workflow-name" or "owner/repo/workflow-name@version")
• Explanation of what happens when just a repository is specified (lists available workflows)
• Information about version specifications (tag, branch, or SHA)
• Details about the workflow file destination (.github/workflows)

Example:

Description: `Add workflows from remote repositories to .github/workflows.

Workflow specifications:
- Two parts: "owner/repo[@version]" (lists available workflows in the repository)
- Three parts: "owner/repo/workflow-name[@version]" (implicitly looks in workflows/ directory)
- Four+ parts: "owner/repo/workflows/workflow-name.md[@version]" (requires explicit .md extension)
- GitHub URL: "https://github.com/owner/repo/blob/branch/path/to/workflow.md"
- Wildcard: "owner/repo/*[@version]" (adds all workflows from the repository)
- Version can be tag, branch, or SHA

The number parameter creates multiple numbered copies of the workflow.
The name parameter specifies a custom name for the added workflow file (without .md extension).`,

Suggested change

	Description: "Add workflows from remote repositories to .github/workflows",
	}, func(ctx context.Context, req *mcp.CallToolRequest, args addArgs) (*mcp.CallToolResult, any, error) {
	Description: `Add workflows from remote repositories to .github/workflows.

[Copilot]

The JSON schema descriptions for the arguments should be more detailed to help AI agents understand how to use them properly:

• Workflows - Should explain the format options (owner/repo, owner/repo/workflow-name, with optional @Version, etc.)
• Number - Should clarify that it corresponds to the -c flag and creates multiple numbered copies
• Name - Should clarify that it should not include the .md extension

Example:

Workflows []string `json:"workflows" jsonschema:"Workflow specifications to add (e.g., 'owner/repo', 'owner/repo/workflow-name', 'owner/repo/workflow-name@version', or GitHub URL). Specify just 'owner/repo' to list available workflows."`
Number    int      `json:"number,omitempty" jsonschema:"Create multiple numbered copies of the workflow (corresponds to -c flag, default: 1)"`
Name      string   `json:"name,omitempty" jsonschema:"Custom name for the added workflow file without .md extension (corresponds to -n flag). Only applies to the first workflow when adding multiple."`

Suggested change

	Workflows []string `json:"workflows" jsonschema:"Workflows to add (e.g., 'owner/repo/workflow-name' or 'owner/repo/workflow-name@version')"`
	Number int `json:"number,omitempty" jsonschema:"Create multiple numbered copies (corresponds to -c flag, default: 1)"`
	Name string `json:"name,omitempty" jsonschema:"Specify name for the added workflow - without .md extension (corresponds to -n flag)"`
	Workflows []string `json:"workflows" jsonschema:"Workflow specifications to add (e.g., 'owner/repo', 'owner/repo/workflow-name', 'owner/repo/workflow-name@version', or GitHub URL). Specify just 'owner/repo' to list available workflows."`
	Number int `json:"number,omitempty" jsonschema:"Create multiple numbered copies of the workflow (corresponds to -c flag, default: 1)"`
	Name string `json:"name,omitempty" jsonschema:"Custom name for the added workflow file without .md extension (corresponds to -n flag). Only applies to the first workflow when adding multiple."`